[Bug 219890] New: illuminance sensor is jittering between correct value and 0.03lux

[Bug 219890] New: illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

            Bug ID: 219890
           Summary: illuminance sensor is jittering between correct value
                    and 0.03lux
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: IIO
          Assignee: drivers_iio@kernel-bugs.kernel.org
          Reporter: wysiwyg81@rbox.co
        Regression: No

Hello,

I have a Lenovo thinkbook 13x gen4.
Automatic brightness control is flickering in Gnome, so I checked sensor with
monitor-sensor command (iio-sensor-proxy).

it shows following behavior:
monitor-sensor  --light
    Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has ambient light sensor (value: 316,000000, unit: lux)
    Light changed: 299,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 299,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 299,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 305,000000 (lux)


the 0.03 is unexpected has it has never been that dark.
it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
checking directly content of here :
/sys/bus/iio/devices/iio:device0/in_illuminance_raw


I checked the behavior on windows to make sure it's not an hardware failure
from my sensor.
While I cannot have direct access to raw sensor data on windows, the automatic
brightness is perfectly smooth: no flickering of any kind.

I didn't found sensor name:
❯ cat  /sys/bus/iio/devices/iio:device0/name
als

But if there is other place I could look, let me know.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

wysiwyg81@rbox.co changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|                            |6.13.7-2

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 219890] New: illuminance sensor is jittering between correct value and 0.03lux

[Jonathan Cameron]

On Mon, 17 Mar 2025 09:38:50 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> 
>             Bug ID: 219890
>            Summary: illuminance sensor is jittering between correct value
>                     and 0.03lux
>            Product: Drivers
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: IIO
>           Assignee: drivers_iio@kernel-bugs.kernel.org
>           Reporter: wysiwyg81@rbox.co
>         Regression: No
> 
> Hello,
> 
> I have a Lenovo thinkbook 13x gen4.
> Automatic brightness control is flickering in Gnome, so I checked sensor with
> monitor-sensor command (iio-sensor-proxy).
> 
> it shows following behavior:
> monitor-sensor  --light
>     Waiting for iio-sensor-proxy to appear
> +++ iio-sensor-proxy appeared
> === Has ambient light sensor (value: 316,000000, unit: lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 305,000000 (lux)
> 
> 
> the 0.03 is unexpected has it has never been that dark.
> it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
> checking directly content of here :
> /sys/bus/iio/devices/iio:device0/in_illuminance_raw
> 
> 
> I checked the behavior on windows to make sure it's not an hardware failure
> from my sensor.
> While I cannot have direct access to raw sensor data on windows, the automatic
> brightness is perfectly smooth: no flickering of any kind.
> 
> I didn't found sensor name:
> ❯ cat  /sys/bus/iio/devices/iio:device0/name
> als

Two possibles types. It's either a hid sensor or an ACPI class interface
with a sensor wrapped up in firmware.

My guess is hid-sensor.  Can you do an
ls -lh in /sys/iio/devices/
so we can see what the parent is.
+CC Srinivas based on playing guess the sensor.

Jonathan





> 
> But if there is other place I could look, let me know.
> 

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #1 from Jonathan Cameron (jic23@kernel.org) ---
On Mon, 17 Mar 2025 09:38:50 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> 
>             Bug ID: 219890
>            Summary: illuminance sensor is jittering between correct value
>                     and 0.03lux
>            Product: Drivers
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: IIO
>           Assignee: drivers_iio@kernel-bugs.kernel.org
>           Reporter: wysiwyg81@rbox.co
>         Regression: No
> 
> Hello,
> 
> I have a Lenovo thinkbook 13x gen4.
> Automatic brightness control is flickering in Gnome, so I checked sensor with
> monitor-sensor command (iio-sensor-proxy).
> 
> it shows following behavior:
> monitor-sensor  --light
>     Waiting for iio-sensor-proxy to appear
> +++ iio-sensor-proxy appeared
> === Has ambient light sensor (value: 316,000000, unit: lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 299,000000 (lux)
>     Light changed: 0,030000 (lux)
>     Light changed: 305,000000 (lux)
> 
> 
> the 0.03 is unexpected has it has never been that dark.
> it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
> checking directly content of here :
> /sys/bus/iio/devices/iio:device0/in_illuminance_raw
> 
> 
> I checked the behavior on windows to make sure it's not an hardware failure
> from my sensor.
> While I cannot have direct access to raw sensor data on windows, the
> automatic
> brightness is perfectly smooth: no flickering of any kind.
> 
> I didn't found sensor name:
> ❯ cat  /sys/bus/iio/devices/iio:device0/name
> als

Two possibles types. It's either a hid sensor or an ACPI class interface
with a sensor wrapped up in firmware.

My guess is hid-sensor.  Can you do an
ls -lh in /sys/iio/devices/
so we can see what the parent is.
+CC Srinivas based on playing guess the sensor.

Jonathan





> 
> But if there is other place I could look, let me know.
>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #2 from wysiwyg81@rbox.co ---
Hello, Did you mean in /sys/bus/iio/devices/ instead of 
/sys/iio/devices/ if so: /sys/bus/iio/devices ❯ ls -lh Permissions Size 
User Date Modified Name lrwxrwxrwx - root 17 mars 13:43  iio:device0 -> 
../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/iio:device0 
lrwxrwxrwx - root 17 mars 13:43  iio:device1 -> 
../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/iio:device1 
lrwxrwxrwx - root 17 mars 13:43  trigger0 -> 
../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/trigger0 
lrwxrwxrwx - root 17 mars 13:43  trigger1 -> 
../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/trigger1

(bugzilla seems down currently, so I try direct email answer, hope it 
works, I will check once bugzilla is back).

Best regards,

On 17/03/2025 13:15, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219890
>
> --- Comment #1 from Jonathan Cameron (jic23@kernel.org) ---
> On Mon, 17 Mar 2025 09:38:50 +0000
> bugzilla-daemon@kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=219890
>>
>>              Bug ID: 219890
>>             Summary: illuminance sensor is jittering between correct value
>>                      and 0.03lux
>>             Product: Drivers
>>             Version: 2.5
>>            Hardware: All
>>                  OS: Linux
>>              Status: NEW
>>            Severity: normal
>>            Priority: P3
>>           Component: IIO
>>            Assignee: drivers_iio@kernel-bugs.kernel.org
>>            Reporter: wysiwyg81@rbox.co
>>          Regression: No
>>
>> Hello,
>>
>> I have a Lenovo thinkbook 13x gen4.
>> Automatic brightness control is flickering in Gnome, so I checked sensor
>> with
>> monitor-sensor command (iio-sensor-proxy).
>>
>> it shows following behavior:
>> monitor-sensor  --light
>>      Waiting for iio-sensor-proxy to appear
>> +++ iio-sensor-proxy appeared
>> === Has ambient light sensor (value: 316,000000, unit: lux)
>>      Light changed: 299,000000 (lux)
>>      Light changed: 0,030000 (lux)
>>      Light changed: 299,000000 (lux)
>>      Light changed: 0,030000 (lux)
>>      Light changed: 299,000000 (lux)
>>      Light changed: 0,030000 (lux)
>>      Light changed: 305,000000 (lux)
>>
>>
>> the 0.03 is unexpected has it has never been that dark.
>> it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
>> checking directly content of here :
>> /sys/bus/iio/devices/iio:device0/in_illuminance_raw
>>
>>
>> I checked the behavior on windows to make sure it's not an hardware failure
>> from my sensor.
>> While I cannot have direct access to raw sensor data on windows, the
>> automatic
>> brightness is perfectly smooth: no flickering of any kind.
>>
>> I didn't found sensor name:
>> ❯ cat  /sys/bus/iio/devices/iio:device0/name
>> als
> Two possibles types. It's either a hid sensor or an ACPI class interface
> with a sensor wrapped up in firmware.
>
> My guess is hid-sensor.  Can you do an
> ls -lh in /sys/iio/devices/
> so we can see what the parent is.
> +CC Srinivas based on playing guess the sensor.
>
> Jonathan
>
>
>
>
>
>> But if there is other place I could look, let me know.
>>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[Jonathan Cameron]

On Mon, 17 Mar 2025 13:02:24 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> 
> --- Comment #2 from wysiwyg81@rbox.co ---
> Hello, Did you mean in /sys/bus/iio/devices/ instead of 
> /sys/iio/devices/ if so: /sys/bus/iio/devices ❯ ls -lh Permissions Size 
> User Date Modified Name lrwxrwxrwx - root 17 mars 13:43  iio:device0 -> 
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/iio:device0 
> lrwxrwxrwx - root 17 mars 13:43  iio:device1 -> 
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/iio:device1 
> lrwxrwxrwx - root 17 mars 13:43  trigger0 -> 
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/trigger0 
> lrwxrwxrwx - root 17 mars 13:43  trigger1 -> 
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/trigger1
> 
> (bugzilla seems down currently, so I try direct email answer, hope it 
> works, I will check once bugzilla is back).
Perfect.  So it is definitely a hid sensor.
Srinivas any idea?
> 
> Best regards,
> 
> On 17/03/2025 13:15, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=219890
> >
> > --- Comment #1 from Jonathan Cameron (jic23@kernel.org) ---
> > On Mon, 17 Mar 2025 09:38:50 +0000
> > bugzilla-daemon@kernel.org wrote:
> >  
> >> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> >>
> >>              Bug ID: 219890
> >>             Summary: illuminance sensor is jittering between correct value
> >>                      and 0.03lux
> >>             Product: Drivers
> >>             Version: 2.5
> >>            Hardware: All
> >>                  OS: Linux
> >>              Status: NEW
> >>            Severity: normal
> >>            Priority: P3
> >>           Component: IIO
> >>            Assignee: drivers_iio@kernel-bugs.kernel.org
> >>            Reporter: wysiwyg81@rbox.co
> >>          Regression: No
> >>
> >> Hello,
> >>
> >> I have a Lenovo thinkbook 13x gen4.
> >> Automatic brightness control is flickering in Gnome, so I checked sensor
> >> with
> >> monitor-sensor command (iio-sensor-proxy).
> >>
> >> it shows following behavior:
> >> monitor-sensor  --light
> >>      Waiting for iio-sensor-proxy to appear
> >> +++ iio-sensor-proxy appeared
> >> === Has ambient light sensor (value: 316,000000, unit: lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 305,000000 (lux)
> >>
> >>
> >> the 0.03 is unexpected has it has never been that dark.
> >> it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
> >> checking directly content of here :
> >> /sys/bus/iio/devices/iio:device0/in_illuminance_raw
> >>
> >>
> >> I checked the behavior on windows to make sure it's not an hardware failure
> >> from my sensor.
> >> While I cannot have direct access to raw sensor data on windows, the
> >> automatic
> >> brightness is perfectly smooth: no flickering of any kind.
> >>
> >> I didn't found sensor name:
> >> ❯ cat  /sys/bus/iio/devices/iio:device0/name
> >> als  
> > Two possibles types. It's either a hid sensor or an ACPI class interface
> > with a sensor wrapped up in firmware.
> >
> > My guess is hid-sensor.  Can you do an
> > ls -lh in /sys/iio/devices/
> > so we can see what the parent is.
> > +CC Srinivas based on playing guess the sensor.
> >
> > Jonathan
> >
> >
> >
> >
> >  
> >> But if there is other place I could look, let me know.
> >>  
> 

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #3 from Fred (wysiwyg81@rbox.co) ---
Hello,

Sorry for poor presentation of message above, I tried direct email answer, not
so nice..

Let me know if it's too unreadable, I'll try to post again

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #4 from Jonathan Cameron (jic23@kernel.org) ---
On Mon, 17 Mar 2025 13:02:24 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> 
> --- Comment #2 from wysiwyg81@rbox.co ---
> Hello, Did you mean in /sys/bus/iio/devices/ instead of 
> /sys/iio/devices/ if so: /sys/bus/iio/devices ❯ ls -lh Permissions Size 
> User Date Modified Name lrwxrwxrwx - root 17 mars 13:43  iio:device0 -> 
>
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/iio:device0 
> lrwxrwxrwx - root 17 mars 13:43  iio:device1 -> 
>
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/iio:device1 
> lrwxrwxrwx - root 17 mars 13:43  trigger0 -> 
>
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/trigger0 
> lrwxrwxrwx - root 17 mars 13:43  trigger1 -> 
>
> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.7.auto/trigger1
> 
> (bugzilla seems down currently, so I try direct email answer, hope it 
> works, I will check once bugzilla is back).
Perfect.  So it is definitely a hid sensor.
Srinivas any idea?
> 
> Best regards,
> 
> On 17/03/2025 13:15, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=219890
> >
> > --- Comment #1 from Jonathan Cameron (jic23@kernel.org) ---
> > On Mon, 17 Mar 2025 09:38:50 +0000
> > bugzilla-daemon@kernel.org wrote:
> >  
> >> https://bugzilla.kernel.org/show_bug.cgi?id=219890
> >>
> >>              Bug ID: 219890
> >>             Summary: illuminance sensor is jittering between correct value
> >>                      and 0.03lux
> >>             Product: Drivers
> >>             Version: 2.5
> >>            Hardware: All
> >>                  OS: Linux
> >>              Status: NEW
> >>            Severity: normal
> >>            Priority: P3
> >>           Component: IIO
> >>            Assignee: drivers_iio@kernel-bugs.kernel.org
> >>            Reporter: wysiwyg81@rbox.co
> >>          Regression: No
> >>
> >> Hello,
> >>
> >> I have a Lenovo thinkbook 13x gen4.
> >> Automatic brightness control is flickering in Gnome, so I checked sensor
> >> with
> >> monitor-sensor command (iio-sensor-proxy).
> >>
> >> it shows following behavior:
> >> monitor-sensor  --light
> >>      Waiting for iio-sensor-proxy to appear
> >> +++ iio-sensor-proxy appeared
> >> === Has ambient light sensor (value: 316,000000, unit: lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 299,000000 (lux)
> >>      Light changed: 0,030000 (lux)
> >>      Light changed: 305,000000 (lux)
> >>
> >>
> >> the 0.03 is unexpected has it has never been that dark.
> >> it seems it's not a iio-sensor-proxy bug as I can see similar behavior by
> >> checking directly content of here :
> >> /sys/bus/iio/devices/iio:device0/in_illuminance_raw
> >>
> >>
> >> I checked the behavior on windows to make sure it's not an hardware
> failure
> >> from my sensor.
> >> While I cannot have direct access to raw sensor data on windows, the
> >> automatic
> >> brightness is perfectly smooth: no flickering of any kind.
> >>
> >> I didn't found sensor name:
> >> ❯ cat  /sys/bus/iio/devices/iio:device0/name
> >> als  
> > Two possibles types. It's either a hid sensor or an ACPI class interface
> > with a sensor wrapped up in firmware.
> >
> > My guess is hid-sensor.  Can you do an
> > ls -lh in /sys/iio/devices/
> > so we can see what the parent is.
> > +CC Srinivas based on playing guess the sensor.
> >
> > Jonathan
> >
> >
> >
> >
> >  
> >> But if there is other place I could look, let me know.
> >>  
>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |srinivas.pandruvada@linux.i
                   |                            |ntel.com

--- Comment #5 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
This is HID sensor.
I wonder if you read raw attributes, there may be power ON/OFF, if there is
delay between them then a 0 sample in between.

Can you try
sudo ./iio_generic_buffer -n als -a -c 1000


You have to stop iio sensor proxy service.
I don't think you can disable, just rename /usr/libexec/iio-sensor-proxy to
something else for test.

This tool is under Linux kernel source git under:
https://elixir.bootlin.com/linux/v6.13.6/source/tools/iio

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #6 from Fred (wysiwyg81@rbox.co) ---
Hello!
woo, compiling my own kernel tool? sounds like some stunts, but challenge
accepted :).

Here how I did (just in case) and results so far:

- backup /usr/lib/iio-sensor-proxy to /usr/lib/iio-sensor-proxy-back

- reboot, try "monitor-sensor --light" => stuck on  "Waiting for
iio-sensor-proxy to appear" so iio-sensor-proxy is disabled

- I downloaded kernel source from here:
https://github.com/CachyOS/linux/tree/6.13/cachy
Which seems to be the closest version of my current kernel (6.13 <=>
6.13.7-2-cachyos)

- get in /tools/iio and type make.

here is the result so far:

> sudo ./iio_generic_buffer -n als -a -c 1000
iio device number being used is 1
iio trigger number being used is 1
Enabling all channels
Enabling: in_chromaticity_y_en
Enabling: in_colortemp_en
Enabling: in_intensity_both_en
Enabling: in_illuminance_en
Enabling: in_timestamp_en
Enabling: in_chromaticity_x_en
/sys/bus/iio/devices/iio:device1 als-dev1
107.000000 107.000000 37.149998 39.379997 38.459999 1742281868794404097 
107.000000 107.000000 37.149998 39.379997 38.459999 1742281868795405367 
144.000000 144.000000 37.399998 39.250000 38.389999 1742283688135649249 
116.000000 116.000000 37.149998 39.379997 38.459999 1742284362250389865 
131.000000 131.000000 37.860001 39.020000 38.259998 1742284362493385633 
212.000000 212.000000 37.360001 39.270000 38.399998 1742284386577247020 
416.000000 416.000000 37.250000 39.329998 38.430000 1742284387069388487 
358.000000 358.000000 37.209999 39.349998 38.450001 1742284388291391492 
317.000000 317.000000 37.309998 39.299999 38.419998 1742284388536376237 
282.000000 282.000000 37.450001 39.230000 38.379997 1742284388781420189 
248.000000 248.000000 37.469997 39.219997 38.369999 1742284399552421827 
163.000000 163.000000 37.380001 39.259998 38.399998 1742284402488374365 
124.000000 124.000000 67.629997 30.769999 31.840000 1742284422066296843 
181.000000 181.000000 37.669998 39.119999 38.320000 1742284435348409111 
153.000000 153.000000 37.570000 39.169998 38.340000 1742284435643379865 
165.000000 165.000000 36.849998 39.529999 38.549999 1742284564197069737 
185.000000 185.000000 36.059998 39.950001 38.770000 1742284564442060549 
166.000000 166.000000 36.889999 39.509998 38.540001 1742284566154115050 
184.000000 184.000000 36.160000 39.899998 38.739998 1742284567377313995 
166.000000 166.000000 36.889999 39.509998 38.540001 1742284568357307927 
187.000000 187.000000 36.059998 39.950001 38.770000 1742284573251081541 
210.000000 210.000000 35.410000 40.299999 38.950001 1742284573741120550 


not finished yet, it's seems to take some time (roughly 40min running now).
I will update once finished.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #7 from Fred (wysiwyg81@rbox.co) ---
Hello!
woo, compiling my own kernel tool? sounds like some stunts, but challenge
accepted :).

Here how I did (just in case) and results so far:

- backup /usr/lib/iio-sensor-proxy to /usr/lib/iio-sensor-proxy-back

- reboot, try "monitor-sensor --light" => stuck on  "Waiting for
iio-sensor-proxy to appear" so iio-sensor-proxy is disabled

- I downloaded kernel source from here:
https://github.com/CachyOS/linux/tree/6.13/cachy
Which seems to be the closest version of my current kernel (6.13 <=>
6.13.7-2-cachyos)

- get in /tools/iio and type make.

here is the result so far:

> sudo ./iio_generic_buffer -n als -a -c 1000
iio device number being used is 1
iio trigger number being used is 1
Enabling all channels
Enabling: in_chromaticity_y_en
Enabling: in_colortemp_en
Enabling: in_intensity_both_en
Enabling: in_illuminance_en
Enabling: in_timestamp_en
Enabling: in_chromaticity_x_en
/sys/bus/iio/devices/iio:device1 als-dev1
107.000000 107.000000 37.149998 39.379997 38.459999 1742281868794404097 
107.000000 107.000000 37.149998 39.379997 38.459999 1742281868795405367 
144.000000 144.000000 37.399998 39.250000 38.389999 1742283688135649249 
116.000000 116.000000 37.149998 39.379997 38.459999 1742284362250389865 
131.000000 131.000000 37.860001 39.020000 38.259998 1742284362493385633 
212.000000 212.000000 37.360001 39.270000 38.399998 1742284386577247020 
416.000000 416.000000 37.250000 39.329998 38.430000 1742284387069388487 
358.000000 358.000000 37.209999 39.349998 38.450001 1742284388291391492 
317.000000 317.000000 37.309998 39.299999 38.419998 1742284388536376237 
282.000000 282.000000 37.450001 39.230000 38.379997 1742284388781420189 
248.000000 248.000000 37.469997 39.219997 38.369999 1742284399552421827 
163.000000 163.000000 37.380001 39.259998 38.399998 1742284402488374365 
124.000000 124.000000 67.629997 30.769999 31.840000 1742284422066296843 
181.000000 181.000000 37.669998 39.119999 38.320000 1742284435348409111 
153.000000 153.000000 37.570000 39.169998 38.340000 1742284435643379865 
165.000000 165.000000 36.849998 39.529999 38.549999 1742284564197069737 
185.000000 185.000000 36.059998 39.950001 38.770000 1742284564442060549 
166.000000 166.000000 36.889999 39.509998 38.540001 1742284566154115050 
184.000000 184.000000 36.160000 39.899998 38.739998 1742284567377313995 
166.000000 166.000000 36.889999 39.509998 38.540001 1742284568357307927 
187.000000 187.000000 36.059998 39.950001 38.770000 1742284573251081541 
210.000000 210.000000 35.410000 40.299999 38.950001 1742284573741120550 


not finished yet, it's seems to take some time (roughly 40min running now).
I will update once finished.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #8 from Fred (wysiwyg81@rbox.co) ---
Created attachment 307849
  --> https://bugzilla.kernel.org/attachment.cgi?id=307849&action=edit
logs from iio_generic_buffer

This are the logs from sudo ./iio_generic_buffer -n als -a -c 1000

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #9 from Fred (wysiwyg81@rbox.co) ---
Hi Srinivas,

I have the 1000 samples.
My office is well lit, but I moved around my desktop light and hands to make
some light variation (many times) :).
This speed up the sampling, I hope it is ok?
I made sure to have no complete dark and no masking of the sensor.

See in https://bugzilla.kernel.org/show_bug.cgi?id=219890#c8 
I hope it's useful.

May I ask what are the numbers (column hearders) ?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #10 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
I think you have multiple als sensors on the systems.
You can also give a run with for device 0, which is the sensor you are reading
in your description. This is USB hub.

sudo ./iio_generic_buffer -N 0 -a -c 1000



Those column headers are

Intensity, illumination, color temp, chromocity X, chromocity Y, timestamp

What you are reading from first 2, which are same here.

There is no 0 here, as sensor is ON always.

But when you read a raw value 

/sys/bus/iio/devices/iio:device0/in_illuminance_raw

The sensor is turned ON and kept ON for 3 seconds. I think when sensor is
turned on the first sample is always 0. Using your description of device 0
"../../../devices/pci0000:00/0000:00:14.0/usb3/3-8/3-8:1.0/0003:17EF:F006.000E/HID-SENSOR-200041.6.auto/iio:device0
"


cd /sys/bus/platform/devices/HID-SENSOR-200041.6.auto/power
echo on > control

And try to cat the /sys/bus/iio/devices/iio:device0/in_illuminance_raw
in a loop.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #11 from Fred (wysiwyg81@rbox.co) ---
Created attachment 307852
  --> https://bugzilla.kernel.org/attachment.cgi?id=307852&action=edit
logs from iio_generic_buffer

This are the logs from :

echo on | sudo tee
/sys/bus/platform/devices/HID-SENSOR-200041.6.auto/power/control

sudo ./iio_generic_buffer -N 0 -a -c 1000

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #12 from Fred (wysiwyg81@rbox.co) ---
Hello,

I did:
echo on | sudo tee
/sys/bus/platform/devices/HID-SENSOR-200041.6.auto/power/control

sudo ./iio_generic_buffer -N 0 -a -c 1000

I hope it's what you expected?

It's evening now, ambient light is lower than previous.
Also this time I use a smartphone blinking screen app to add some variation,
otherwise it would take hours to fill the 1000 samples. hope it's fine.

let me know if I shall do something different.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #13 from Fred (wysiwyg81@rbox.co) ---
note :  I also tried this:
watch -n 0.7 cat /sys/bus/iio/devices/iio:device0/in_illuminance_raw

after setting /sys/bus/platform/devices/HID-SENSOR-200041.6.auto/power/control
to on.

it is still "blinking" between "3" and some higher value.
the "3" match the 0.03lux from monitor-sensor.
( /sys/bus/iio/devices/iio:device1/in_illuminance_scale  = 0.01 )

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #14 from Fred (wysiwyg81@rbox.co) ---
Created attachment 307853
  --> https://bugzilla.kernel.org/attachment.cgi?id=307853&action=edit
logs from iio_generic_buffer

added a log with control back to auto (50 samples)

echo auto | sudo tee
/sys/bus/platform/devices/HID-SENSOR-200041.6.auto/power/control

sudo ./iio_generic_buffer -N 0 -a -c 50

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #15 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
Created attachment 307854
  --> https://bugzilla.kernel.org/attachment.cgi?id=307854&action=edit
patch to dump raw data from sensor hub

A patch to dump raw data from notifications.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #16 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
It seems that with raw reads with ON/OFF there may be some bad data from sensor
hub.
Unfortunately, need a kernel built with patch for debug dump.

Remove iio sensor proxy from running and reboot

Before run
echo 'file hid-sensor-trigger.c +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file hid-sensor-hub.c +p' > /sys/kernel/debug/dynamic_debug/control

watch -n 0.7 cat /sys/bus/iio/devices/iio:device0/in_illuminance_raw

Send the output from dmesg command.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #17 from Fred (wysiwyg81@rbox.co) ---
Hello Srinivas,

I have some trouble again to access bugzilla website (error 
502/504)..cannot see the patch right now.

I try again answering by email directly, hope it will keep better 
formatting than previous attempt.

In the mean time, I tried the following command. The unexpected "3" are 
very visible here.

❯ watch -n 0.7 "echo \$(date '+%Y-%m-%d %H:%M:%S') \$(cat 
/sys/bus/iio/devices/iio:device0/in_illuminance_raw) | tee -a 
log_illuminance.txt"

I attach log_illuminance.txtto the email.

iio_sensor_proxy is still disabled for those measurements.

I'll try to setup the patch as soon as I can access to it.

Best regards,

Fred

On 19/03/2025 01:54, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219890
>
> --- Comment #16 from Srinivas Pandruvada
> (srinivas.pandruvada@linux.intel.com) ---
> It seems that with raw reads with ON/OFF there may be some bad data from
> sensor
> hub.
> Unfortunately, need a kernel built with patch for debug dump.
>
> Remove iio sensor proxy from running and reboot
>
> Before run
> echo 'file hid-sensor-trigger.c +p' > /sys/kernel/debug/dynamic_debug/control
> echo 'file hid-sensor-hub.c +p' > /sys/kernel/debug/dynamic_debug/control
>
> watch -n 0.7 cat /sys/bus/iio/devices/iio:device0/in_illuminance_raw
>
> Send the output from dmesg command.
>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #18 from Fred (wysiwyg81@rbox.co) ---
Created attachment 307859
  --> https://bugzilla.kernel.org/attachment.cgi?id=307859&action=edit
dmesg output with patched kernel

Hello,

Here are the dmesg logs after patching kernel and execute commands as
requested.

I just had to reword the echo commands this way:

echo 'file hid-sensor-hub.c +p'  | sudo tee
/sys/kernel/debug/dynamic_debug/control
echo 'file hid-sensor-trigger.c +p' | sudo tee
/sys/kernel/debug/dynamic_debug/control

Let me know if longer logs needed.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #19 from Fred (wysiwyg81@rbox.co) ---
Wrong the data I see in dmesg and watch commands, my understanding is that:

Raw data: 00000000: 08 cf 00 00   => mean cf08 as illuminance measurement =
53000 in decimal (53000 is what I can see on watch command).

if I correctly understood the format, then I can see a few lines with "3"
measurement again:

Raw data: 00000000: 03 00 00 00

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #20 from Fred (wysiwyg81@rbox.co) ---
*sorry 1st sentence in previous message was truncated.

I meant "If I don't understood wrong the data in  dmesg and watch commands, my
understanding is that"

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #21 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
That is correct. Sometimes the data received is 0300. But not as frequent as
you in your description. The first sample after power up, I can understand as I
have seen before. But here it is intermittent. There are no other events also
to see if there is some random mixup.

I want to see if this is lower than the logical min value, then we can return
as failed read.
If you go to /sys/kernel/debug/hid/
There will be folders. I think this sensor is under 0003:17EF:F006.000E.

if you read "rdesc" file, you may see something like this:

Physical(Sensors.LightAmbientLight) 
      Usage(1)
        Sensors.DataFieldIlluminance
      Logical Minimum(0)
      Logical Maximum(10000) 
      Unit Exponent(-3)
      Report Size(32)
      Report Count(1)
      Report Offset(208)
      Flags( Variable Absolute )

Check that.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #22 from Fred (wysiwyg81@rbox.co) ---
it's big file :)
I found this section, by searching "Sensors.DataFieldIlluminance". 
is it what you looking for ?


    Field(2)
      Physical(Sensors.LightAmbientLight)
      Application(Sensors.Sensor)
      Usage(1)
        Sensors.DataFieldIlluminance
      Logical Minimum(0)
      Logical Maximum(-1)
      Unit Exponent(-2)
      Report Size(32)
      Report Count(1)
      Report Offset(16)
      Flags( Variable Absolute

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #23 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
So the logical min and max are not useful here to clamp the result.
I think this needs a quirk in sensor proxy to filter by reading two consecutive
result and discard the bad value.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #24 from Fred (wysiwyg81@rbox.co) ---
If it were me, I would just filter the "3" if that even possible? Anyway just
general though, I cannot say at all that I know what I'm talking about :). 


But what do you mean by a quirk in sensor proxy? Shall it be managed by
iio-sensor-proxy?

I ask because I opened a bug report there before here..

https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/407

And conclusion was that it should be solved in driver before iio-sensor-proxy.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #25 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
Data is sent by the sensor hub. We can't filter out 3 as this still more than
0. The logical min/max is not properly added also to filter out

This data is sent by the sensor hub firmware. We can just add this to banned
list for HID sensor.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #26 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
Also check from iio-sensor-proxy
here on this system weather iio-poll-als or iio-buffer-als is getting used?
Means weather it polling for input of using buffer mode?

It is possible that when you poll, then you have this issue not when using
buffer, where sensor hub will push data.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #27 from Fred (wysiwyg81@rbox.co) ---
Hello Srinivas,
I re-open the bug on iio-sensor-proxy and asked to have a look to last message
here.
to be honest, I don't know what to do right now. 
I will try to search if I can find anything with iio-poll-als or
iio-buffer-als.

suggestions are welcome :)

here is the link on iio-sensor-proxy side:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/407

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #28 from Fred (wysiwyg81@rbox.co) ---
Hello,
After test as suggested here :
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/407#note_2828458

it seems buffer work better than polling !


Disable polling :

❯ cat /usr/lib/udev/rules.d/80-iio-sensor-proxy.rules
# iio-sensor-proxy
# IIO sensor to D-Bus proxy

ACTION=="remove", GOTO="iio_sensor_proxy_end"

# Set the sensor type for all the types we recognise
SUBSYSTEM=="hwmon", TEST=="light", ENV{IIO_SENSOR_PROXY_TYPE}+="hwmon-als"
SUBSYSTEM=="iio", TEST=="in_accel_x_raw", TEST=="in_accel_y_raw",
TEST=="in_accel_z_raw", ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-accel"
SUBSYSTEM=="iio", TEST=="scan_elements/in_accel_x_en",
TEST=="scan_elements/in_accel_y_en", TEST=="scan_elements/in_accel_z_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-accel"
SUBSYSTEM=="iio",
TEST=="scan_elements/in_rot_from_north_magnetic_tilt_comp_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-compass"
#SUBSYSTEM=="iio", TEST=="in_illuminance_input",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
#SUBSYSTEM=="iio", TEST=="in_illuminance0_input",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
#SUBSYSTEM=="iio", TEST=="in_illuminance_clear_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
#SUBSYSTEM=="iio", TEST=="in_illuminance_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
#SUBSYSTEM=="iio", TEST=="in_intensity_clear_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
SUBSYSTEM=="iio", TEST=="scan_elements/in_intensity_both_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-als"
SUBSYSTEM=="iio", TEST=="in_proximity_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-proximity"
SUBSYSTEM=="iio", TEST=="in_proximity0_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-proximity"
SUBSYSTEM=="input", ENV{ID_INPUT_ACCELEROMETER}=="1",
ENV{IIO_SENSOR_PROXY_TYPE}+="input-accel"

ENV{IIO_SENSOR_PROXY_TYPE}=="", GOTO="iio_sensor_proxy_end"

# We got here because we have a sensor type, which means we need the service
TAG+="systemd", ENV{SYSTEMD_WANTS}+="iio-sensor-proxy.service"

LABEL="iio_sensor_proxy_end"

~
❯ monitor-sensor  --light
    Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has ambient light sensor (value: 234,999995, unit: lux)
    Light changed: 163,999996 (lux)
    Light changed: 133,999997 (lux)
    Light changed: 237,999995 (lux)
    Light changed: 207,999995 (lux)
    Light changed: 133,999997 (lux)
    Light changed: 228,999995 (lux)
    Light changed: 231,999995 (lux)
    Light changed: 229,999995 (lux)
    Light changed: 133,999997 (lux)
    Light changed: 225,999995 (lux)
    Light changed: 229,999995 (lux)
    Light changed: 173,999996 (lux)
    Light changed: 237,999995 (lux)
    Light changed: 188,999996 (lux)
    Light changed: 137,999997 (lux)
    Light changed: 227,999995 (lux)





Disabling buffer:



cat /usr/lib/udev/rules.d/80-iio-sensor-proxy.rules
# iio-sensor-proxy
# IIO sensor to D-Bus proxy

ACTION=="remove", GOTO="iio_sensor_proxy_end"

# Set the sensor type for all the types we recognise
SUBSYSTEM=="hwmon", TEST=="light", ENV{IIO_SENSOR_PROXY_TYPE}+="hwmon-als"
SUBSYSTEM=="iio", TEST=="in_accel_x_raw", TEST=="in_accel_y_raw",
TEST=="in_accel_z_raw", ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-accel"
SUBSYSTEM=="iio", TEST=="scan_elements/in_accel_x_en",
TEST=="scan_elements/in_accel_y_en", TEST=="scan_elements/in_accel_z_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-accel"
SUBSYSTEM=="iio",
TEST=="scan_elements/in_rot_from_north_magnetic_tilt_comp_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-compass"
SUBSYSTEM=="iio", TEST=="in_illuminance_input",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
SUBSYSTEM=="iio", TEST=="in_illuminance0_input",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
SUBSYSTEM=="iio", TEST=="in_illuminance_clear_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
SUBSYSTEM=="iio", TEST=="in_illuminance_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
SUBSYSTEM=="iio", TEST=="in_intensity_clear_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-als"
#SUBSYSTEM=="iio", TEST=="scan_elements/in_intensity_both_en",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-buffer-als"
SUBSYSTEM=="iio", TEST=="in_proximity_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-proximity"
SUBSYSTEM=="iio", TEST=="in_proximity0_raw",
ENV{IIO_SENSOR_PROXY_TYPE}+="iio-poll-proximity"
SUBSYSTEM=="input", ENV{ID_INPUT_ACCELEROMETER}=="1",
ENV{IIO_SENSOR_PROXY_TYPE}+="input-accel"

ENV{IIO_SENSOR_PROXY_TYPE}=="", GOTO="iio_sensor_proxy_end"

# We got here because we have a sensor type, which means we need the service
TAG+="systemd", ENV{SYSTEMD_WANTS}+="iio-sensor-proxy.service"

LABEL="iio_sensor_proxy_end"

~
❯ monitor-sensor  --light
    Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has ambient light sensor (value: 263,000000, unit: lux)
    Light changed: 203,000000 (lux)
    Light changed: 148,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 230,000000 (lux)
    Light changed: 237,000000 (lux)
    Light changed: 172,000000 (lux)
    Light changed: 143,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 233,000000 (lux)
    Light changed: 0,030000 (lux)
    Light changed: 237,000000 (lux)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #29 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
That is the observation from test program also. This sensor when polled, it
sends a response which probably is incomplete (may in in flight). But in
buffered mode, no needs to poll.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #30 from Fred (wysiwyg81@rbox.co) ---
Hello Srinivas,

Problem seems gone with iio-sensor-proxy v3.7 that I installed yesterday 

https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/407

Thank you for your kind support in processing this issue !

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219890] illuminance sensor is jittering between correct value and 0.03lux

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219890

--- Comment #31 from Srinivas Pandruvada (srinivas.pandruvada@linux.intel.com) ---
(In reply to Fred from comment #30)
> Hello Srinivas,
> 
> Problem seems gone with iio-sensor-proxy v3.7 that I installed yesterday 
> 
> https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/407
> 
> Thank you for your kind support in processing this issue !

Hi Fred, Thanks for bringing up. I will try to inform Lenovo about this.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.