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: Tue, 18 Mar 2025 17:47:01 +0000 [thread overview]
Message-ID: <bug-219890-217253-Nxbd18fG2C@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 #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.
next prev parent reply other threads:[~2025-03-18 17:47 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
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 [this message]
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-Nxbd18fG2C@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.