From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 199715] hp_accel: probe of HPQ6007:00 failed with error -22 (HP Envy x360)
Date: Tue, 12 Oct 2021 10:44:49 +0000 [thread overview]
Message-ID: <bug-199715-215701-C7GWTGOA16@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199715-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199715
Marco (rodomar705@protonmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rodomar705@protonmail.com
--- Comment #60 from Marco (rodomar705@protonmail.com) ---
(In reply to kernelbugzilla from comment #59)
> FYI, I unsuccessfully tested both the upstream driver and Richard's version
> on a Renoir device (Ryzen 3 4300U on a Asus Vivobook Flip 14 TM420IA). An
> accelerometer device is detected, but it returns no data.
>
> Apparently, both drivers are missing a report descriptor for the newer
> Renoir hardware.
>
> Reference: https://github.com/conqp/amd-sfh-hid-dkms/issues/1 (thanks
> Richard for the prompt reply there)
On the exact same device, but with a 4500U as of 5.14.11, I do get
accelerometer data.
The issues with sensors however is that I do not have an event for the lid flip
on this device in order to disable automatically keyboard and trackpad in
tablet mode and no way to use an apparently present ALS for automatic
brightness (I'm not sure even if this device has one, but I've seen quite a lot
of reference to a Capella Micro cm32181 in the DSDT under i2c, and the kernel
even load the mentioned driver. No iio data anywhere, though).
If the position of the hinges are derived from two accelerometers (one in the
base, the other in the display) I would like to write an implementation around
that, but the sensor reports only the one in the display panel and nothing
else, so that's really not useful anyway.
However at least I can use display rotation with that.
I really hope that AMD will provide documentation around that or at least will
properly support his sensor hub to Ryzen 4/5 devices themselves.
--
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:[~2021-10-12 10:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199715-215701@https.bugzilla.kernel.org/>
2021-01-16 20:14 ` [Bug 199715] hp_accel: probe of HPQ6007:00 failed with error -22 (HP Envy x360) bugzilla-daemon
2021-01-17 9:02 ` bugzilla-daemon
2021-01-17 10:57 ` bugzilla-daemon
2021-01-17 10:57 ` bugzilla-daemon
2021-01-17 10:58 ` bugzilla-daemon
2021-01-17 11:09 ` bugzilla-daemon
2021-01-17 11:13 ` bugzilla-daemon
2021-01-17 11:34 ` bugzilla-daemon
2021-01-17 11:36 ` bugzilla-daemon
2021-01-17 12:15 ` bugzilla-daemon
2021-01-17 14:23 ` bugzilla-daemon
2021-01-17 14:46 ` bugzilla-daemon
2021-01-17 14:49 ` bugzilla-daemon
2021-01-17 14:51 ` bugzilla-daemon
2021-01-17 16:01 ` bugzilla-daemon
2021-01-19 13:38 ` bugzilla-daemon
2021-01-19 18:56 ` bugzilla-daemon
2021-01-19 20:20 ` bugzilla-daemon
2021-01-19 20:24 ` bugzilla-daemon
2021-01-19 20:36 ` bugzilla-daemon
2021-01-19 20:45 ` bugzilla-daemon
2021-01-19 22:25 ` bugzilla-daemon
2021-01-20 9:24 ` bugzilla-daemon
2021-01-20 11:09 ` bugzilla-daemon
2021-01-20 11:45 ` bugzilla-daemon
2021-01-21 16:58 ` bugzilla-daemon
2021-01-23 14:15 ` bugzilla-daemon
2021-01-23 20:58 ` bugzilla-daemon
2021-01-23 22:08 ` bugzilla-daemon
2021-01-24 12:04 ` bugzilla-daemon
2021-01-24 16:11 ` bugzilla-daemon
2021-01-27 1:57 ` bugzilla-daemon
2021-10-12 10:44 ` bugzilla-daemon [this message]
2021-12-04 11:00 ` bugzilla-daemon
2021-12-04 11:06 ` bugzilla-daemon
2021-12-04 14:48 ` bugzilla-daemon
2021-12-04 16:12 ` bugzilla-daemon
2022-02-02 19:04 ` bugzilla-daemon
2022-02-09 17:52 ` bugzilla-daemon
2022-02-23 20:30 ` bugzilla-daemon
2022-02-24 6:22 ` bugzilla-daemon
2025-04-30 6:37 ` bugzilla-daemon
2026-03-17 14:42 ` 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-199715-215701-C7GWTGOA16@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=platform-driver-x86@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