Bug 1651886 - Missing AMD Sensor Fusion Hub driver for Linux kernel
Summary: Missing AMD Sensor Fusion Hub driver for Linux kernel
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-21 06:28 UTC by Luya Tshimbalanga
Modified: 2019-05-21 05:51 UTC (History)
21 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)
Journal report after bios update (870.34 KB, text/plain)
2018-11-21 06:28 UTC, Luya Tshimbalanga
no flags Details
acpidump data after bios update (870.34 KB, text/plain)
2018-11-21 06:31 UTC, Luya Tshimbalanga
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Linux Kernel 199715 None None None 2019-05-04 18:30 UTC

Description Luya Tshimbalanga 2018-11-21 06:28:52 UTC
Created attachment 1507558 [details]
Journal report after bios update

Description of problem:

The HP Envy x360(Ryzen) uses an integrated accelerometer which get detected but probe fails with:

    lis3lv02d: unknown sensor type 0x0
    hp_accel: probe of HPQ6007:00 failed with error -22

Possibly all HP touchscreen laptops with AMD processors are affected considering their Intel counterpart run out of box (https://h30434.www3.hp.com/t5/Notebook-Video-Display-and-Touch/HP-Zbook-15-external-monitor-connected-to-docking-station/td-p/4985667)

Version-Release number of selected component (if applicable):
4.19.2

How reproducible:
Always

Steps to Reproduce:
1. Boot a AMD power HP Touchscreen Laptop
2.
3.

Actual results:
lis3lv02d: unknown sensor type 0x0
hp_accel: probe of HPQ6007:00 failed with error -22

Expected results:
Accelerometer is probed and configured accordingly.

Additional info:
Tested with HP Envy x360 Ryzen 2500U

Comment 1 Luya Tshimbalanga 2018-11-21 06:31 UTC
Created attachment 1507559 [details]
acpidump data after bios update

acpidump tested with scratch build kernel provided by Hans

Comment 2 Hans de Goede 2018-11-21 09:40:40 UTC
(In reply to Luya Tshimbalanga from comment #0)
> lis3lv02d: unknown sensor type 0x0
> hp_accel: probe of HPQ6007:00 failed with error -22

I do not think that those messages are the problem, they are about a driver for harddisk fall protection, which given that your device uses a SSD is probably not there. I guess the ACPI tables still advertise support for it even though the hardware is not there, causing these log messages.

In order to figure out how to get accelerometer support working on your laptop I need some more info.

First of all try running "monitor-sensor":

If this just hangs at "Waiting for iio-sensor-proxy to appear" then press ctrl+c, if it prints some more things, please let me know what it prints and if it claims you've an accelerometer, try rotating the screen and see if it outputs anything.

If monitor-sensors finds an accelerometer and prints orientation changes when rotating, then everything is working as it should.

If not please provide the output of:

lspci -nn
lsusb
ls /sys/bus/i2c/devices
ls /sys/bus/iio/devices

And then we will see form there.

Note, some AMD devices use a "AMD Sensor Fusion Hub" pci-id: 1022:15e4 for which there does not seem to be a linux driver yet. So if your lspci output includes a device with those ids then chances are that is the problem. But please do provide the output of all requested commands in the case that monitor-sensor does not see an accelerometer.

Comment 3 Luya Tshimbalanga 2018-11-21 15:54:36 UTC
(In reply to Hans de Goede from comment #2)
> (In reply to Luya Tshimbalanga from comment #0)
> > lis3lv02d: unknown sensor type 0x0
> > hp_accel: probe of HPQ6007:00 failed with error -22
> 
> I do not think that those messages are the problem, they are about a driver
> for harddisk fall protection, which given that your device uses a SSD is
> probably not there. I guess the ACPI tables still advertise support for it
> even though the hardware is not there, causing these log messages.

The laptop originally has HDD before swapping with the SSD. It seems like a bug such driver does not automatically disable when SSD is present.

 
> First of all try running "monitor-sensor":
> 
> If this just hangs at "Waiting for iio-sensor-proxy to appear" then press
> ctrl+c, if it prints some more things, please let me know what it prints and
> if it claims you've an accelerometer, try rotating the screen and see if it
> outputs anything.

Sadly it hangs.
> 
> If monitor-sensors finds an accelerometer and prints orientation changes
> when rotating, then everything is working as it should.
> 
> If not please provide the output of:
> 
> lspci -nn

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15d0]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Device [1022:15d1]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:15d3]
00:01.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:15d3]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:15db]
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:15dc]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ea]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15eb]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ec]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ed]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ee]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:15ef]
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4)
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15de]
03:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Device [1022:15df]
03:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e0]
03:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e1]
03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e3]
03:00.7 Non-VGA unclassified device [0000]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e4]
04:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 61)


> lsusb

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
Bus 003 Device 002: ID 04f2:b634 Chicony Electronics Co., Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

> ls /sys/bus/i2c/devices

i2c-0  i2c-2  i2c-4  i2c-6  i2c-8  i2c-ELAN0732:00
i2c-1  i2c-3  i2c-5  i2c-7  i2c-9

> ls /sys/bus/iio/devices

Not listed. However, booting Windows 10 shows the screen rotating when positioning the laptop in portrait. Not sure if it is an emulation.

> And then we will see form there.
> 
> Note, some AMD devices use a "AMD Sensor Fusion Hub" pci-id: 1022:15e4 for
> which there does not seem to be a linux driver yet. So if your lspci output 
> includes a device with those ids then chances are that is the problem. 

It looks like we found the issue from the lspci -nn extract:

03:00.7 Non-VGA unclassified device [0000]: Advanced Micro Devices, Inc. [AMD] Device [1022:15e4]

Comment 4 Hans de Goede 2018-11-21 16:54:43 UTC
Ok, so I indeed believe that this is caused by missing support for the AMD fusion sensor hub.

I've send a message to AMD's Bridgman who is a point of contact for FOSS GPU drivers if he can put me in contact with someone inside AMD who knows more about the AMD fusion sensor hub.

Comment 5 Luya Tshimbalanga 2018-11-21 22:50:57 UTC
Thanks Hans!

Comment 6 Luya Tshimbalanga 2018-11-29 04:54:50 UTC
Rename the bug to match comment #4.

Comment 7 Luya Tshimbalanga 2018-12-16 11:31:33 UTC
(In reply to Hans de Goede from comment #4)
> Ok, so I indeed believe that this is caused by missing support for the AMD
> fusion sensor hub.
> 
> I've send a message to AMD's Bridgman who is a point of contact for FOSS GPU
> drivers if he can put me in contact with someone inside AMD who knows more
> about the AMD fusion sensor hub.

With some researches, I found these informations: https://www.kionix.com/sensor-fusion and https://github.com/RohmSemiconductor/Linux-Kernel-Input-Drivers

Comment 8 Hans de Goede 2018-12-16 13:18:03 UTC
Hi,

(In reply to Luya Tshimbalanga from comment #7)
> (In reply to Hans de Goede from comment #4)
> > Ok, so I indeed believe that this is caused by missing support for the AMD
> > fusion sensor hub.
> > 
> > I've send a message to AMD's Bridgman who is a point of contact for FOSS GPU
> > drivers if he can put me in contact with someone inside AMD who knows more
> > about the AMD fusion sensor hub.
> 
> With some researches, I found these informations:
> https://www.kionix.com/sensor-fusion and
> https://github.com/RohmSemiconductor/Linux-Kernel-Input-Drivers

I do not believe that those are related to the AMD sensor-hub, they just happen to both use "sensor fusion" as some sort of marketing term. Unfortunately I've not heard anything back from AMD yet wrt this.

Regards,

Hans

Comment 9 Luya Tshimbalanga 2018-12-17 02:22:14 UTC
Oh well. Hopefully AMD will reply sooner.

Comment 10 Luya Tshimbalanga 2019-01-20 18:52:08 UTC
Any update from the AMD side?

Comment 11 Hans de Goede 2019-01-21 08:41:39 UTC
(In reply to Luya Tshimbalanga from comment #10)
> Any update from the AMD side?

Unfortunately not, and without any documentation it is going to be quite hard to support this.

Comment 12 Luya Tshimbalanga 2019-01-25 16:11:41 UTC
I found an Arch linux page (https://wiki.archlinux.org/index.php/HP_Envy_X360_15-bq102ng) mentioning STM Sensor hub. Maybe investigating there?

Comment 13 Hans de Goede 2019-01-26 14:25:16 UTC
(In reply to Luya Tshimbalanga from comment #12)
> I found an Arch linux page
> (https://wiki.archlinux.org/index.php/HP_Envy_X360_15-bq102ng) mentioning
> STM Sensor hub. Maybe investigating there?

That is for s slightly different model Envy X360, which has sensors connected to the i2c bus, as the "ls /sys/bus/i2c/devices" you have done shows, your model's sensors are not connected to the i2c bus.

Comment 14 Luya Tshimbalanga 2019-01-27 02:09:27 UTC
Interesting, I wonder why that little change on the newer Envy X360.

Comment 15 Stasiek Michalski 2019-01-28 09:24:41 UTC
Same issue on 13 inch Envy, to the PCI-E ID, hope you hear something from AMD soon :D

Comment 16 hpryzen5 2019-02-20 16:32:40 UTC
Hello all, I am also experiencing this issue on the HP Envy x360(Ryzen). Is there still any hope of AMD responding?

Comment 17 Luya Tshimbalanga 2019-03-16 21:02:27 UTC
The Sensor Fusion Hub is correctly identified on  kernel 4.20.14 displayed a more detailed information:

03:00.7 Non-VGA unclassified device [0000]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Sensor Fusion Hub [1022:15e4]

It looks like the info is from the linux-firmware. Still no driver.

Comment 18 Laura Abbott 2019-04-09 20:44:42 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora XX has now been rebased to 5.0.6  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30.
 
If you experience different issues, please open a new bug report for those.

Comment 19 Luya Tshimbalanga 2019-04-09 23:11:25 UTC
Done. The issue still affects all Fedora release and other distributions.

Comment 20 Luya Tshimbalanga 2019-05-04 18:39:33 UTC
Hi Hans,

Just noticed this link https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/commit/?h=i2c/for-next&id=529766e0a0114438887382a68d97341fbf8349fb via Phoronix post (https://www.phoronix.com/scan.php?page=news_item&px=AMD-MP2-I2C-Linux-5.2).
Not sure if this is the missing driver as I would like to test it.

Comment 21 Hans de Goede 2019-05-06 08:24:39 UTC
(In reply to Luya Tshimbalanga from comment #20)
> Hi Hans,
> 
> Just noticed this link
> https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/commit/?h=i2c/
> for-next&id=529766e0a0114438887382a68d97341fbf8349fb via Phoronix post
> (https://www.phoronix.com/scan.php?page=news_item&px=AMD-MP2-I2C-Linux-5.2).
> Not sure if this is the missing driver as I would like to test it.

I'm afraid that that is not the driver you need, that is an i2c controller driver, not a driver for sensors attached to the fusion-hub.

Comment 22 Luya Tshimbalanga 2019-05-07 23:18:52 UTC
You are right. Still waiting for the driver in question.

Comment 24 hpryzen5 2019-05-21 05:51:11 UTC
(In reply to hpryzen5 from comment #23)
> Could this be it?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/commit/?h=i2c/
> for-next&id=529766e0a0114438887382a68d97341fbf8349fb

Oh, should read first... sorry. I see it's not. Got over-excited I guess. Really hoping the driver'll show up.


Note You need to log in before you can comment on or make changes to this bug.