Re: [PATCH] lis3lv02d: add axes knowledge of HP Pavilion dv5 models

[Giuseppe Bilotta]

On Tue, Feb 10, 2009 at 10:28 PM, Giuseppe Bilotta
<giuseppe.bilotta@xxxxxxxxx> wrote:
> On Tue, Feb 10, 2009 at 1:42 PM, Éric Piel <E.A.B.Piel@xxxxxxxxxx> wrote:
>> Can you try something like this in lis3lv02d_poweron():
>>        adev.read(handle, CTRL_REG2, &val);
>>        val |= CTRL2_BDU | CTRL2_IEN;
>> +       val &= ~CTRL2_BLE;
>>        adev.write(handle, CTRL_REG2, val);
>
> Ok, this is getting crazier and crazier. Apparently, setting the
> CTRL2_BLE bit this way makes no difference, and so does setting it
> with val |= (i.e. enabling it): in both cases, if I debug
> lis3lv02d_read_16 I always get 0 in the lower byte and something in
> the upper byte.

To be precise, these are the result I get with some additional debug
info, with and without setting BLE.

Setting BLE on init:

[ 2891.428798] lis3lv02d: BLE: 0
[ 2891.452567] lis3lv02d: BLE: 32
[ 2891.476800] lis3lv02d: lo: 0 hi: 1
[ 2891.500616] lis3lv02d: lo: 0 hi: 3
[ 2891.524799] lis3lv02d: lo: 0 hi: 57

Resetting BLE on init:

[ 3006.661279] lis3lv02d: BLE: 0
[ 3006.684574] lis3lv02d: BLE: 0
[ 3006.709107] lis3lv02d: lo: 0 hi: 254
[ 3006.733144] lis3lv02d: lo: 0 hi: 2
[ 3006.757286] lis3lv02d: lo: 0 hi: 56

So it looks like (1) the BLE register is ignored (at least in my
sensor) and (2) it actually defaults to LE anyway.

-- 
Giuseppe "Oblomov" Bilotta
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/