Linux IIO development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 219890] illuminance sensor is jittering between correct value and 0.03lux
Date: Mon, 17 Mar 2025 18:57:25 +0000	[thread overview]
Message-ID: <bug-219890-217253-rJnq3XbWLK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219890-217253@https.bugzilla.kernel.org/>

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.

  parent reply	other threads:[~2025-03-17 18:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  9:38 [Bug 219890] New: illuminance sensor is jittering between correct value and 0.03lux bugzilla-daemon
2025-03-17 10:25 ` [Bug 219890] " bugzilla-daemon
2025-03-17 12:14 ` [Bug 219890] New: " Jonathan Cameron
2025-03-17 12:15 ` [Bug 219890] " bugzilla-daemon
2025-03-17 13:02 ` bugzilla-daemon
2025-03-17 18:57   ` Jonathan Cameron
2025-03-17 13:37 ` bugzilla-daemon
2025-03-17 18:57 ` bugzilla-daemon [this message]
2025-03-17 22:13 ` bugzilla-daemon
2025-03-18  8:05 ` bugzilla-daemon
2025-03-18  8:06 ` bugzilla-daemon
2025-03-18 11:56 ` bugzilla-daemon
2025-03-18 11:57 ` bugzilla-daemon
2025-03-18 17:47 ` bugzilla-daemon
2025-03-18 18:25 ` bugzilla-daemon
2025-03-18 18:27 ` bugzilla-daemon
2025-03-18 18:31 ` bugzilla-daemon
2025-03-18 18:36 ` bugzilla-daemon
2025-03-19  0:51 ` bugzilla-daemon
2025-03-19  0:54 ` bugzilla-daemon
2025-03-19  8:14 ` bugzilla-daemon
2025-03-19 13:11 ` bugzilla-daemon
2025-03-19 13:17 ` bugzilla-daemon
2025-03-19 13:19 ` bugzilla-daemon
2025-03-19 19:25 ` bugzilla-daemon
2025-03-19 19:48 ` bugzilla-daemon
2025-03-19 20:59 ` bugzilla-daemon
2025-03-19 23:19 ` bugzilla-daemon
2025-03-20 17:27 ` bugzilla-daemon
2025-03-20 17:46 ` bugzilla-daemon
2025-03-20 18:08 ` bugzilla-daemon
2025-03-21  6:04 ` bugzilla-daemon
2025-03-21 16:36 ` bugzilla-daemon
2025-03-22  9:38 ` bugzilla-daemon
2025-03-22 15:11 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-219890-217253-rJnq3XbWLK@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox