From: Tj <linux@iam.tj>
To: linux-input <linux-input@vger.kernel.org>, linux-iio@vger.kernel.org
Subject: bug: i2c-INVN6500:00: unexpected HID descriptor bcdVersion (0xca9b)
Date: Wed, 6 Feb 2019 10:35:09 +0000 [thread overview]
Message-ID: <27a0a01c-7e4b-136c-7cfe-9ef93d5bfd05@iam.tj> (raw)
Looking back through boot logs this message is seen on all kernels used
on this Asus T300CHI, from v4.15 onwards:
hidraw: raw HID events driver (C) Jiri Kosina
i2c_hid i2c-INVN6500:00: i2c-INVN6500:00 supply vdd not found, using
dummy regulator
i2c_hid i2c-INVN6500:00: Linked as a consumer to regulator.0
i2c_hid i2c-INVN6500:00: i2c-INVN6500:00 supply vddl not found, using
dummy regulator
i2c_hid i2c-INVN6500:00: unexpected HID descriptor bcdVersion (0xca9b)
inv-mpu6050-i2c i2c-INVN6500:00: mounting matrix not found: using
identity...
inv-mpu6050-i2c i2c-INVN6500:00: i2c-INVN6500:00 supply vddio not found,
using dummy regulator
It's not clear if this is a warning that can be disregarded or an
indication the protocol isn't being completely decoded.
The accelerometer is working correctly but the ambient light sensor
isn't. I tested that by shining an LED camera light around the edges of
the device where the sensors are located and monitoring for changes.
I'm reasonably sure the light-sensor has worked previously but it isn't
something I would generally notice since the device is used in fairly
constant low-light conditions.
This may or may not be related to the error message.
$ monitor-sensor
Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has accelerometer (orientation: normal)
=== Has ambient light sensor (value: 0.000000, unit: lux)
next reply other threads:[~2019-02-06 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 10:35 Tj [this message]
2019-02-09 18:02 ` bug: i2c-INVN6500:00: unexpected HID descriptor bcdVersion (0xca9b) Jonathan Cameron
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=27a0a01c-7e4b-136c-7cfe-9ef93d5bfd05@iam.tj \
--to=linux@iam.tj \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).