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: Sun, 17 Jan 2021 12:15:14 +0000 [thread overview]
Message-ID: <bug-199715-215701-W0O8FL9zKr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199715-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199715
--- Comment #33 from Richard Neumann (mail@richard-neumann.de) ---
@Hans "work" is a relative term here. They are all recognized and started.
Going into details would go beyond the scope of this thread, I think.
dmesg excerpt:
[ 10.855774] amd-sfh-pci 0000:04:00.7: Sensor mask: 0x80007
[ 10.856054] hid-generic 0018:03FE:0001.0002: hidraw1: I2C HID v0.01 Device
[accelerometer] on AMD Sensor Fusion Hub (PCIe)
[ 10.856325] hid-generic 0018:03FE:0001.0003: hidraw2: I2C HID v0.01 Device
[gyroscope] on AMD Sensor Fusion Hub (PCIe)
[ 10.856614] hid-generic 0018:03FE:0001.0004: hidraw3: I2C HID v0.01 Device
[magnetometer] on AMD Sensor Fusion Hub (PCIe)
[ 10.856893] hid-generic 0018:03FE:0001.0005: hidraw4: I2C HID v0.01 Device
[ambient light sensor] on AMD Sensor Fusion Hub (PCIe)
I am only *using* the accelerometer, so a mask of "1" or "0x1" respectively
would suffice.
Testing the other sensors is non-trivial. I branched my refactored version of
the driver to extend it with an API to allow for reverse-engineering the PCI
device to detect other sensors. But again, this maybe something to discuss in
another place (or write a paper about :p).
--
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-01-17 12:15 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 [this message]
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
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-W0O8FL9zKr@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 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.