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: Wed, 19 Mar 2025 19:25:33 +0000 [thread overview]
Message-ID: <bug-219890-217253-G0WGUruKe4@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 #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.
next prev parent reply other threads:[~2025-03-19 19:25 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
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 [this message]
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-G0WGUruKe4@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.