* ACPI defined devices not showing up under /sys/bus/platform/devices @ 2014-09-18 12:04 Hans de Goede 2014-09-18 14:01 ` Mika Westerberg 0 siblings, 1 reply; 12+ messages in thread From: Hans de Goede @ 2014-09-18 12:04 UTC (permalink / raw) To: linux-acpi; +Cc: Marcos Paulo de souza, Hans de Goede Hi, I'm trying to help various users with Asus X450 and Asus X550 laptops to get their touchpad to work: https://bugzilla.redhat.com/show_bug.cgi?id=1110011 We believe that this touchpad is connected over i2c, using the i2c-designware-platform driver. If you look at the DSDT attached there you can clearly see nodes defines which should lead to e.g. : /sys/bus/platform/devices/INT33C2:00 Showing up (which should then be bound by i2c-designware-platform). But nothing is showing up, not a single ACPI defined device shows up actually: [root@asusx550 devices]# ll insgesamt 0 lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 Which is weird, since any recent machine usually has at least one or 2 show up. Therefor I would like to ask your help with figuring out how to get the device nodes defined in the DSDT to actual show up. Thanks & Regards, Hans ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-18 12:04 ACPI defined devices not showing up under /sys/bus/platform/devices Hans de Goede @ 2014-09-18 14:01 ` Mika Westerberg 2014-09-18 20:49 ` Hans de Goede 0 siblings, 1 reply; 12+ messages in thread From: Mika Westerberg @ 2014-09-18 14:01 UTC (permalink / raw) To: Hans de Goede; +Cc: linux-acpi, Marcos Paulo de souza On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: > Hi, > > I'm trying to help various users with Asus X450 and Asus X550 laptops > to get their touchpad to work: > > https://bugzilla.redhat.com/show_bug.cgi?id=1110011 > > We believe that this touchpad is connected over i2c, using the > i2c-designware-platform driver. > > If you look at the DSDT attached there you can clearly see > nodes defines which should lead to e.g. : > > /sys/bus/platform/devices/INT33C2:00 > > Showing up (which should then be bound by i2c-designware-platform). > > But nothing is showing up, not a single ACPI defined device shows > up actually: > > > > > > [root@asusx550 devices]# ll > insgesamt 0 > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 > lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 > lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 > > > Which is weird, since any recent machine usually has at least one or 2 > show up. It depends whether the BIOS has enabled those or not. If # cat /sys/bus/acpi/devices/INT33C2:00/status # cat /sys/bus/acpi/devices/INT33C3:00/status returns 0xf, then the device should be there, otherwise it is not. The "status" refers directly shat _STA() ACPI method returns. Note that the device could also be in PCI mode, in case lspci should show it. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-18 14:01 ` Mika Westerberg @ 2014-09-18 20:49 ` Hans de Goede 2014-09-18 21:02 ` Marcos Paulo de souza 0 siblings, 1 reply; 12+ messages in thread From: Hans de Goede @ 2014-09-18 20:49 UTC (permalink / raw) To: Mika Westerberg; +Cc: linux-acpi, Marcos Paulo de souza Hi, On 09/18/2014 04:01 PM, Mika Westerberg wrote: > On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >> Hi, >> >> I'm trying to help various users with Asus X450 and Asus X550 laptops >> to get their touchpad to work: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >> >> We believe that this touchpad is connected over i2c, using the >> i2c-designware-platform driver. >> >> If you look at the DSDT attached there you can clearly see >> nodes defines which should lead to e.g. : >> >> /sys/bus/platform/devices/INT33C2:00 >> >> Showing up (which should then be bound by i2c-designware-platform). >> >> But nothing is showing up, not a single ACPI defined device shows >> up actually: >> >> >> >> >> >> [root@asusx550 devices]# ll >> insgesamt 0 >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >> >> >> Which is weird, since any recent machine usually has at least one or 2 >> show up. > > It depends whether the BIOS has enabled those or not. > > If > > # cat /sys/bus/acpi/devices/INT33C2:00/status > # cat /sys/bus/acpi/devices/INT33C3:00/status > > returns 0xf, then the device should be there, otherwise it is not. Interesting. Marcos, can you give this a try please ? > The "status" refers directly shat _STA() ACPI method returns. Ok, so assuming that Marcos' testing shows it is not enabled, is there anything we can, could there be some ACPI call to enable these devs ? > Note that the device could also be in PCI mode, in case lspci should > show it. Right, it does not show in lspci. Regards, Hans ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-18 20:49 ` Hans de Goede @ 2014-09-18 21:02 ` Marcos Paulo de souza 2014-09-19 8:47 ` Mika Westerberg 0 siblings, 1 reply; 12+ messages in thread From: Marcos Paulo de souza @ 2014-09-18 21:02 UTC (permalink / raw) To: Hans de Goede, Mika Westerberg; +Cc: linux-acpi Hi, On 09/18/2014 05:49 PM, Hans de Goede wrote: > Hi, > > On 09/18/2014 04:01 PM, Mika Westerberg wrote: >> On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >>> Hi, >>> >>> I'm trying to help various users with Asus X450 and Asus X550 laptops >>> to get their touchpad to work: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >>> >>> We believe that this touchpad is connected over i2c, using the >>> i2c-designware-platform driver. >>> >>> If you look at the DSDT attached there you can clearly see >>> nodes defines which should lead to e.g. : >>> >>> /sys/bus/platform/devices/INT33C2:00 >>> >>> Showing up (which should then be bound by i2c-designware-platform). >>> >>> But nothing is showing up, not a single ACPI defined device shows >>> up actually: >>> >>> >>> >>> >>> >>> [root@asusx550 devices]# ll >>> insgesamt 0 >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >>> >>> >>> Which is weird, since any recent machine usually has at least one or 2 >>> show up. >> It depends whether the BIOS has enabled those or not. >> >> If >> >> # cat /sys/bus/acpi/devices/INT33C2:00/status >> # cat /sys/bus/acpi/devices/INT33C3:00/status >> >> returns 0xf, then the device should be there, otherwise it is not. > Interesting. Marcos, can you give this a try please ? Hans, both here returned 0. As I said to you, I'm using Fedora in insecure mode (I don't know if this changes anything). > >> The "status" refers directly shat _STA() ACPI method returns. > Ok, so assuming that Marcos' testing shows it is not enabled, > is there anything we can, could there be some ACPI call to > enable these devs ? > >> Note that the device could also be in PCI mode, in case lspci should >> show it. > Right, it does not show in lspci. > > Regards, > > Hans ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-18 21:02 ` Marcos Paulo de souza @ 2014-09-19 8:47 ` Mika Westerberg 2014-09-19 11:48 ` Marcos Paulo de souza 2014-09-19 11:51 ` Marcos Paulo de souza 0 siblings, 2 replies; 12+ messages in thread From: Mika Westerberg @ 2014-09-19 8:47 UTC (permalink / raw) To: Marcos Paulo de souza; +Cc: Hans de Goede, linux-acpi On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: > Hi, > > On 09/18/2014 05:49 PM, Hans de Goede wrote: > >Hi, > > > >On 09/18/2014 04:01 PM, Mika Westerberg wrote: > >>On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: > >>>Hi, > >>> > >>>I'm trying to help various users with Asus X450 and Asus X550 laptops > >>>to get their touchpad to work: > >>> > >>>https://bugzilla.redhat.com/show_bug.cgi?id=1110011 > >>> > >>>We believe that this touchpad is connected over i2c, using the > >>>i2c-designware-platform driver. > >>> > >>>If you look at the DSDT attached there you can clearly see > >>>nodes defines which should lead to e.g. : > >>> > >>>/sys/bus/platform/devices/INT33C2:00 > >>> > >>>Showing up (which should then be bound by i2c-designware-platform). > >>> > >>>But nothing is showing up, not a single ACPI defined device shows > >>>up actually: > >>> > >>> > >>> > >>> > >>> > >>>[root@asusx550 devices]# ll > >>>insgesamt 0 > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 > >>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 > >>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 > >>> > >>> > >>>Which is weird, since any recent machine usually has at least one or 2 > >>>show up. > >>It depends whether the BIOS has enabled those or not. > >> > >>If > >> > >> # cat /sys/bus/acpi/devices/INT33C2:00/status > >> # cat /sys/bus/acpi/devices/INT33C3:00/status > >> > >>returns 0xf, then the device should be there, otherwise it is not. > >Interesting. Marcos, can you give this a try please ? > Hans, both here returned 0. As I said to you, I'm using Fedora in insecure > mode (I don't know if this changes anything). That just means that your BIOS has disabled these devices. Unless there is a menu somewhere in BIOS setup to enable these, there is nothing we can do in the kernel to make them appear. > >>The "status" refers directly shat _STA() ACPI method returns. > >Ok, so assuming that Marcos' testing shows it is not enabled, > >is there anything we can, could there be some ACPI call to > >enable these devs ? > > > >>Note that the device could also be in PCI mode, in case lspci should > >>show it. > >Right, it does not show in lspci. OK. So I think that this particular machine, either does not have Intel LPSS (it is not Haswell-LP) or the devices have been deliberately disabled for some reason. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 8:47 ` Mika Westerberg @ 2014-09-19 11:48 ` Marcos Paulo de souza 2014-09-19 12:01 ` Mika Westerberg 2014-09-19 11:51 ` Marcos Paulo de souza 1 sibling, 1 reply; 12+ messages in thread From: Marcos Paulo de souza @ 2014-09-19 11:48 UTC (permalink / raw) To: Mika Westerberg; +Cc: Hans de Goede, linux-acpi Hi, On 09/19/2014 05:47 AM, Mika Westerberg wrote: > On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: >> Hi, >> >> On 09/18/2014 05:49 PM, Hans de Goede wrote: >>> Hi, >>> >>> On 09/18/2014 04:01 PM, Mika Westerberg wrote: >>>> On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >>>>> Hi, >>>>> >>>>> I'm trying to help various users with Asus X450 and Asus X550 laptops >>>>> to get their touchpad to work: >>>>> >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >>>>> >>>>> We believe that this touchpad is connected over i2c, using the >>>>> i2c-designware-platform driver. >>>>> >>>>> If you look at the DSDT attached there you can clearly see >>>>> nodes defines which should lead to e.g. : >>>>> >>>>> /sys/bus/platform/devices/INT33C2:00 >>>>> >>>>> Showing up (which should then be bound by i2c-designware-platform). >>>>> >>>>> But nothing is showing up, not a single ACPI defined device shows >>>>> up actually: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> [root@asusx550 devices]# ll >>>>> insgesamt 0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >>>>> >>>>> >>>>> Which is weird, since any recent machine usually has at least one or 2 >>>>> show up. >>>> It depends whether the BIOS has enabled those or not. >>>> >>>> If >>>> >>>> # cat /sys/bus/acpi/devices/INT33C2:00/status >>>> # cat /sys/bus/acpi/devices/INT33C3:00/status >>>> >>>> returns 0xf, then the device should be there, otherwise it is not. >>> Interesting. Marcos, can you give this a try please ? >> Hans, both here returned 0. As I said to you, I'm using Fedora in insecure >> mode (I don't know if this changes anything). > That just means that your BIOS has disabled these devices. Unless there > is a menu somewhere in BIOS setup to enable these, there is nothing we > can do in the kernel to make them appear. Interesting. This machine came with Windows 8, and removed. The touchpad was working on Windows. Mika, I verified my BIOS configurations and there isn't any configuration to enable PCI devices. Do you beleive there is something about secure boot? As it worked with Windows, hwo can it be detected on Linux? > >>>> The "status" refers directly shat _STA() ACPI method returns. >>> Ok, so assuming that Marcos' testing shows it is not enabled, >>> is there anything we can, could there be some ACPI call to >>> enable these devs ? >>> >>>> Note that the device could also be in PCI mode, in case lspci should >>>> show it. >>> Right, it does not show in lspci. > OK. So I think that this particular machine, either does not have Intel > LPSS (it is not Haswell-LP) or the devices have been deliberately > disabled for some reason. How can I verify this? ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 11:48 ` Marcos Paulo de souza @ 2014-09-19 12:01 ` Mika Westerberg 2014-09-19 12:19 ` Marcos Paulo de souza 2014-09-20 8:48 ` Hans de Goede 0 siblings, 2 replies; 12+ messages in thread From: Mika Westerberg @ 2014-09-19 12:01 UTC (permalink / raw) To: Marcos Paulo de souza; +Cc: Hans de Goede, linux-acpi On Fri, Sep 19, 2014 at 08:48:49AM -0300, Marcos Paulo de souza wrote: > Hi, > > On 09/19/2014 05:47 AM, Mika Westerberg wrote: > >On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: > >>Hi, > >> > >>On 09/18/2014 05:49 PM, Hans de Goede wrote: > >>>Hi, > >>> > >>>On 09/18/2014 04:01 PM, Mika Westerberg wrote: > >>>>On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: > >>>>>Hi, > >>>>> > >>>>>I'm trying to help various users with Asus X450 and Asus X550 laptops > >>>>>to get their touchpad to work: > >>>>> > >>>>>https://bugzilla.redhat.com/show_bug.cgi?id=1110011 > >>>>> > >>>>>We believe that this touchpad is connected over i2c, using the > >>>>>i2c-designware-platform driver. > >>>>> > >>>>>If you look at the DSDT attached there you can clearly see > >>>>>nodes defines which should lead to e.g. : > >>>>> > >>>>>/sys/bus/platform/devices/INT33C2:00 > >>>>> > >>>>>Showing up (which should then be bound by i2c-designware-platform). > >>>>> > >>>>>But nothing is showing up, not a single ACPI defined device shows > >>>>>up actually: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>[root@asusx550 devices]# ll > >>>>>insgesamt 0 > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 > >>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 > >>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 > >>>>> > >>>>> > >>>>>Which is weird, since any recent machine usually has at least one or 2 > >>>>>show up. > >>>>It depends whether the BIOS has enabled those or not. > >>>> > >>>>If > >>>> > >>>> # cat /sys/bus/acpi/devices/INT33C2:00/status > >>>> # cat /sys/bus/acpi/devices/INT33C3:00/status > >>>> > >>>>returns 0xf, then the device should be there, otherwise it is not. > >>>Interesting. Marcos, can you give this a try please ? > >>Hans, both here returned 0. As I said to you, I'm using Fedora in insecure > >>mode (I don't know if this changes anything). > >That just means that your BIOS has disabled these devices. Unless there > >is a menu somewhere in BIOS setup to enable these, there is nothing we > >can do in the kernel to make them appear. > Interesting. This machine came with Windows 8, and removed. The touchpad was > working on Windows. Mika, I verified my BIOS configurations and there isn't > any configuration to enable PCI devices. Do you beleive there is something > about secure boot? As it worked with Windows, hwo can it be detected on > Linux? Are you sure that your touch pad is connected to I2C bus in the first place? In your ACPI DSDT, there is also a device called PS2M that happens to to look like touch pad to me. For example it reports one of these _HIDs: Method (_HID, 0, NotSerialized) // _HID: Hardware ID { If (SYNA) { Return (0x190A2E4F) } If (ALPS) { Return (0x0713A906) } If (ELAN) { Return (0x08018416) } If (STLC) { Return (0x41C18C4E) } If (FOLT) { Return (0x01019419) } Return (0x060A2E4F) } Have you checked if any of these are present in /sys/bus/acpi/devices/*? > > > >>>>The "status" refers directly shat _STA() ACPI method returns. > >>>Ok, so assuming that Marcos' testing shows it is not enabled, > >>>is there anything we can, could there be some ACPI call to > >>>enable these devs ? > >>> > >>>>Note that the device could also be in PCI mode, in case lspci should > >>>>show it. > >>>Right, it does not show in lspci. > >OK. So I think that this particular machine, either does not have Intel > >LPSS (it is not Haswell-LP) or the devices have been deliberately > >disabled for some reason. > How can I verify this? Can you send me output of lspci -vv? ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 12:01 ` Mika Westerberg @ 2014-09-19 12:19 ` Marcos Paulo de souza 2014-09-19 12:26 ` Mika Westerberg 2014-09-20 8:48 ` Hans de Goede 1 sibling, 1 reply; 12+ messages in thread From: Marcos Paulo de souza @ 2014-09-19 12:19 UTC (permalink / raw) To: Mika Westerberg; +Cc: Hans de Goede, linux-acpi Hi Mika, On 09/19/2014 09:01 AM, Mika Westerberg wrote: > On Fri, Sep 19, 2014 at 08:48:49AM -0300, Marcos Paulo de souza wrote: >> Hi, >> >> On 09/19/2014 05:47 AM, Mika Westerberg wrote: >>> On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: >>>> Hi, >>>> >>>> On 09/18/2014 05:49 PM, Hans de Goede wrote: >>>>> Hi, >>>>> >>>>> On 09/18/2014 04:01 PM, Mika Westerberg wrote: >>>>>> On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I'm trying to help various users with Asus X450 and Asus X550 laptops >>>>>>> to get their touchpad to work: >>>>>>> >>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >>>>>>> >>>>>>> We believe that this touchpad is connected over i2c, using the >>>>>>> i2c-designware-platform driver. >>>>>>> >>>>>>> If you look at the DSDT attached there you can clearly see >>>>>>> nodes defines which should lead to e.g. : >>>>>>> >>>>>>> /sys/bus/platform/devices/INT33C2:00 >>>>>>> >>>>>>> Showing up (which should then be bound by i2c-designware-platform). >>>>>>> >>>>>>> But nothing is showing up, not a single ACPI defined device shows >>>>>>> up actually: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [root@asusx550 devices]# ll >>>>>>> insgesamt 0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >>>>>>> >>>>>>> >>>>>>> Which is weird, since any recent machine usually has at least one or 2 >>>>>>> show up. >>>>>> It depends whether the BIOS has enabled those or not. >>>>>> >>>>>> If >>>>>> >>>>>> # cat /sys/bus/acpi/devices/INT33C2:00/status >>>>>> # cat /sys/bus/acpi/devices/INT33C3:00/status >>>>>> >>>>>> returns 0xf, then the device should be there, otherwise it is not. >>>>> Interesting. Marcos, can you give this a try please ? >>>> Hans, both here returned 0. As I said to you, I'm using Fedora in insecure >>>> mode (I don't know if this changes anything). >>> That just means that your BIOS has disabled these devices. Unless there >>> is a menu somewhere in BIOS setup to enable these, there is nothing we >>> can do in the kernel to make them appear. >> Interesting. This machine came with Windows 8, and removed. The touchpad was >> working on Windows. Mika, I verified my BIOS configurations and there isn't >> any configuration to enable PCI devices. Do you beleive there is something >> about secure boot? As it worked with Windows, hwo can it be detected on >> Linux? > Are you sure that your touch pad is connected to I2C bus in the first > place? > > In your ACPI DSDT, there is also a device called PS2M that happens to to > look like touch pad to me. For example it reports one of these _HIDs: > > Method (_HID, 0, NotSerialized) // _HID: Hardware ID > { > If (SYNA) > { > Return (0x190A2E4F) > } > > If (ALPS) > { > Return (0x0713A906) > } > > If (ELAN) > { > Return (0x08018416) > } > > If (STLC) > { > Return (0x41C18C4E) > } > > If (FOLT) > { > Return (0x01019419) > } > > Return (0x060A2E4F) > } > > Have you checked if any of these are present in /sys/bus/acpi/devices/*? Yes. This is exactly the same: Method (_HID, 0, NotSerialized) // _HID: Hardware ID { If (SYNA) { Return (0x190A2E4F) } If (ALPS) { Return (0x0713A906) } If (ELAN) { Return (0x08018416) } If (STLC) { Return (0x41C18C4E) } If (FOLT) { Return (0x02019419) } Return (0x060A2E4F) } > >>>>>> The "status" refers directly shat _STA() ACPI method returns. >>>>> Ok, so assuming that Marcos' testing shows it is not enabled, >>>>> is there anything we can, could there be some ACPI call to >>>>> enable these devs ? >>>>> >>>>>> Note that the device could also be in PCI mode, in case lspci should >>>>>> show it. >>>>> Right, it does not show in lspci. >>> OK. So I think that this particular machine, either does not have Intel >>> LPSS (it is not Haswell-LP) or the devices have been deliberately >>> disabled for some reason. >> How can I verify this? > Can you send me output of lspci -vv? It I have a Haswell-ULT: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 42 Region 0: Memory at f7400000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0200c Data: 41c1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) Subsystem: Intel Corporation Device 2010 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at f7a14000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4152 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 41 Region 0: Memory at f7a00000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Address: 00000000fee0f00c Data: 41b1 Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at f7a1d000 (64-bit, non-prefetchable) [size=32] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0f00c Data: 41e1 Kernel driver in use: mei_me Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Device 11bf Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 45 Region 0: Memory at f7a10000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0f00c Data: 4142 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable- ID=2 ArbSelect=Fixed TC/VC=04 Status: NegoPending- InProgress- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 13fd Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: f7900000-f79fffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #3, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #2, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 13fd Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v0] #00 Capabilities: [200 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=40us PortTPowerOnTime=10us Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f7800000-f78fffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #4, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #3, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 13fd Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v0] #00 Capabilities: [200 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=40us PortTPowerOnTime=10us Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: f6000000-f70fffff Prefetchable memory behind bridge: 00000000e0000000-00000000f1ffffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #5, Speed 5GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <512ns, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #4, PowerLimit 25.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 13fd Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v0] #00 Capabilities: [200 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=40us PortTPowerOnTime=10us Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 23 Region 0: Memory at f7a1b000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 40 Region 0: I/O ports at f0b0 [size=8] Region 1: I/O ports at f0a0 [size=4] Region 2: I/O ports at f090 [size=8] Region 3: I/O ports at f080 [size=4] Region 4: I/O ports at f060 [size=32] Region 5: Memory at f7a1a000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0100c Data: 4191 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004 Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) Subsystem: ASUSTeK Computer Inc. Device 13fd Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at f7a19000 (64-bit, non-prefetchable) [size=256] Region 4: I/O ports at f040 [size=32] Kernel modules: i2c_i801 02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10) Subsystem: ASUSTeK Computer Inc. Device 200f Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 47 Region 0: Memory at f7900000 (64-bit, non-prefetchable) [size=256K] Region 2: I/O ports at e000 [size=128] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- AttnBtn+ AttnInd+ PwrInd+ RBE+ FLReset- DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 unlimited ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [c0] MSI: Enable+ Count=1/16 Maskable+ 64bit+ Address: 00000000fee0f00c Data: 4162 Masking: 0000fffe Pending: 00000000 Capabilities: [d8] MSI-X: Enable- Count=16 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00003000 Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP- SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [180 v1] Device Serial Number ff-c1-f9-b8-10-c3-7b-ff Kernel driver in use: alx Kernel modules: alx 03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe Subsystem: Foxconn International, Inc. Device e055 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f7810000 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Device Serial Number 00-00-75-68-45-30-35-54 Kernel driver in use: rt2800pci Kernel modules: rt2800pci 03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth Subsystem: Foxconn International, Inc. Device e056 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at f7800000 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Device Serial Number 00-00-76-68-45-30-35-54 04:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] (rev a1) Subsystem: ASUSTeK Computer Inc. GeForce GT 720M Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at d000 [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0100c Data: 41d1 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting <?> Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau Kernel modules: nouveau If you need more info please tell me. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 12:19 ` Marcos Paulo de souza @ 2014-09-19 12:26 ` Mika Westerberg 0 siblings, 0 replies; 12+ messages in thread From: Mika Westerberg @ 2014-09-19 12:26 UTC (permalink / raw) To: Marcos Paulo de souza; +Cc: Hans de Goede, linux-acpi On Fri, Sep 19, 2014 at 09:19:14AM -0300, Marcos Paulo de souza wrote: > Hi Mika, > > On 09/19/2014 09:01 AM, Mika Westerberg wrote: > >On Fri, Sep 19, 2014 at 08:48:49AM -0300, Marcos Paulo de souza wrote: > >>Hi, > >> > >>On 09/19/2014 05:47 AM, Mika Westerberg wrote: > >>>On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: > >>>>Hi, > >>>> > >>>>On 09/18/2014 05:49 PM, Hans de Goede wrote: > >>>>>Hi, > >>>>> > >>>>>On 09/18/2014 04:01 PM, Mika Westerberg wrote: > >>>>>>On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: > >>>>>>>Hi, > >>>>>>> > >>>>>>>I'm trying to help various users with Asus X450 and Asus X550 laptops > >>>>>>>to get their touchpad to work: > >>>>>>> > >>>>>>>https://bugzilla.redhat.com/show_bug.cgi?id=1110011 > >>>>>>> > >>>>>>>We believe that this touchpad is connected over i2c, using the > >>>>>>>i2c-designware-platform driver. > >>>>>>> > >>>>>>>If you look at the DSDT attached there you can clearly see > >>>>>>>nodes defines which should lead to e.g. : > >>>>>>> > >>>>>>>/sys/bus/platform/devices/INT33C2:00 > >>>>>>> > >>>>>>>Showing up (which should then be bound by i2c-designware-platform). > >>>>>>> > >>>>>>>But nothing is showing up, not a single ACPI defined device shows > >>>>>>>up actually: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>[root@asusx550 devices]# ll > >>>>>>>insgesamt 0 > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 > >>>>>>>lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 > >>>>>>> > >>>>>>> > >>>>>>>Which is weird, since any recent machine usually has at least one or 2 > >>>>>>>show up. > >>>>>>It depends whether the BIOS has enabled those or not. > >>>>>> > >>>>>>If > >>>>>> > >>>>>> # cat /sys/bus/acpi/devices/INT33C2:00/status > >>>>>> # cat /sys/bus/acpi/devices/INT33C3:00/status > >>>>>> > >>>>>>returns 0xf, then the device should be there, otherwise it is not. > >>>>>Interesting. Marcos, can you give this a try please ? > >>>>Hans, both here returned 0. As I said to you, I'm using Fedora in insecure > >>>>mode (I don't know if this changes anything). > >>>That just means that your BIOS has disabled these devices. Unless there > >>>is a menu somewhere in BIOS setup to enable these, there is nothing we > >>>can do in the kernel to make them appear. > >>Interesting. This machine came with Windows 8, and removed. The touchpad was > >>working on Windows. Mika, I verified my BIOS configurations and there isn't > >>any configuration to enable PCI devices. Do you beleive there is something > >>about secure boot? As it worked with Windows, hwo can it be detected on > >>Linux? > >Are you sure that your touch pad is connected to I2C bus in the first > >place? > > > >In your ACPI DSDT, there is also a device called PS2M that happens to to > >look like touch pad to me. For example it reports one of these _HIDs: > > > > Method (_HID, 0, NotSerialized) // _HID: Hardware ID > > { > > If (SYNA) > > { > > Return (0x190A2E4F) > > } > > > > If (ALPS) > > { > > Return (0x0713A906) > > } > > > > If (ELAN) > > { > > Return (0x08018416) > > } > > > > If (STLC) > > { > > Return (0x41C18C4E) > > } > > > > If (FOLT) > > { > > Return (0x01019419) > > } > > > > Return (0x060A2E4F) > > } > > > >Have you checked if any of these are present in /sys/bus/acpi/devices/*? > > Yes. This is exactly the same: > > Method (_HID, 0, NotSerialized) // _HID: Hardware ID > { > If (SYNA) > { > Return (0x190A2E4F) > } > > If (ALPS) > { > Return (0x0713A906) > } > > If (ELAN) > { > Return (0x08018416) > } > > If (STLC) > { > Return (0x41C18C4E) > } > > If (FOLT) > { > Return (0x02019419) > } > > Return (0x060A2E4F) > } Which one of them is present in /sys/bus/acpi/devices/? > > > >>>>>>The "status" refers directly shat _STA() ACPI method returns. > >>>>>Ok, so assuming that Marcos' testing shows it is not enabled, > >>>>>is there anything we can, could there be some ACPI call to > >>>>>enable these devs ? > >>>>> > >>>>>>Note that the device could also be in PCI mode, in case lspci should > >>>>>>show it. > >>>>>Right, it does not show in lspci. > >>>OK. So I think that this particular machine, either does not have Intel > >>>LPSS (it is not Haswell-LP) or the devices have been deliberately > >>>disabled for some reason. > >>How can I verify this? > >Can you send me output of lspci -vv? > It I have a Haswell-ULT: Based on your lspci output you have LPSS disabled. For comparison here is a snippet from one development machine which is HSW-ULT: ... 00:15.1 Serial bus controller [0c80]: Intel Corporation Lynx Point-LP I2C Controller #0 (rev 03) 00:15.2 Serial bus controller [0c80]: Intel Corporation Lynx Point-LP I2C Controller #1 (rev 03) ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 12:01 ` Mika Westerberg 2014-09-19 12:19 ` Marcos Paulo de souza @ 2014-09-20 8:48 ` Hans de Goede 2014-09-22 9:14 ` Mika Westerberg 1 sibling, 1 reply; 12+ messages in thread From: Hans de Goede @ 2014-09-20 8:48 UTC (permalink / raw) To: Mika Westerberg, Marcos Paulo de souza; +Cc: linux-acpi Hi Mika, First of all many thanks for your input on this. On 09/19/2014 02:01 PM, Mika Westerberg wrote: > On Fri, Sep 19, 2014 at 08:48:49AM -0300, Marcos Paulo de souza wrote: >> Hi, >> >> On 09/19/2014 05:47 AM, Mika Westerberg wrote: >>> On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: >>>> Hi, >>>> >>>> On 09/18/2014 05:49 PM, Hans de Goede wrote: >>>>> Hi, >>>>> >>>>> On 09/18/2014 04:01 PM, Mika Westerberg wrote: >>>>>> On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I'm trying to help various users with Asus X450 and Asus X550 laptops >>>>>>> to get their touchpad to work: >>>>>>> >>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >>>>>>> >>>>>>> We believe that this touchpad is connected over i2c, using the >>>>>>> i2c-designware-platform driver. >>>>>>> >>>>>>> If you look at the DSDT attached there you can clearly see >>>>>>> nodes defines which should lead to e.g. : >>>>>>> >>>>>>> /sys/bus/platform/devices/INT33C2:00 >>>>>>> >>>>>>> Showing up (which should then be bound by i2c-designware-platform). >>>>>>> >>>>>>> But nothing is showing up, not a single ACPI defined device shows >>>>>>> up actually: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [root@asusx550 devices]# ll >>>>>>> insgesamt 0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >>>>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >>>>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >>>>>>> >>>>>>> >>>>>>> Which is weird, since any recent machine usually has at least one or 2 >>>>>>> show up. >>>>>> It depends whether the BIOS has enabled those or not. >>>>>> >>>>>> If >>>>>> >>>>>> # cat /sys/bus/acpi/devices/INT33C2:00/status >>>>>> # cat /sys/bus/acpi/devices/INT33C3:00/status >>>>>> >>>>>> returns 0xf, then the device should be there, otherwise it is not. >>>>> Interesting. Marcos, can you give this a try please ? >>>> Hans, both here returned 0. As I said to you, I'm using Fedora in insecure >>>> mode (I don't know if this changes anything). >>> That just means that your BIOS has disabled these devices. Unless there >>> is a menu somewhere in BIOS setup to enable these, there is nothing we >>> can do in the kernel to make them appear. >> Interesting. This machine came with Windows 8, and removed. The touchpad was >> working on Windows. Mika, I verified my BIOS configurations and there isn't >> any configuration to enable PCI devices. Do you beleive there is something >> about secure boot? As it worked with Windows, hwo can it be detected on >> Linux? > > Are you sure that your touch pad is connected to I2C bus in the first > place? No, that is a guess because the windows drivers for this touchpad can do both ps/2 and i2c-hid, and we're sort of hoping that i2c-hid is attached, so that we don't need to reverse-engineer a new ps/2 protocol. But it looks like we are out of luck there, and we really need to figure out the ps/2 protocol. > In your ACPI DSDT, there is also a device called PS2M that happens to to > look like touch pad to me. For example it reports one of these _HIDs: > > Method (_HID, 0, NotSerialized) // _HID: Hardware ID > { > If (SYNA) > { > Return (0x190A2E4F) > } > > If (ALPS) > { > Return (0x0713A906) > } > > If (ELAN) > { > Return (0x08018416) > } > > If (STLC) > { > Return (0x41C18C4E) > } > > If (FOLT) > { > Return (0x01019419) > } FOLT probably stands for Focaltech, and I bet this is the one which will show up in /sys/bus/acpi/devices/ If it does show up, is there any way to see how it is supposed to be connected ? Regards, Hans ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-20 8:48 ` Hans de Goede @ 2014-09-22 9:14 ` Mika Westerberg 0 siblings, 0 replies; 12+ messages in thread From: Mika Westerberg @ 2014-09-22 9:14 UTC (permalink / raw) To: Hans de Goede; +Cc: Marcos Paulo de souza, linux-acpi On Sat, Sep 20, 2014 at 10:48:11AM +0200, Hans de Goede wrote: > FOLT probably stands for Focaltech, and I bet this is the one which will show up in > /sys/bus/acpi/devices/ > > If it does show up, is there any way to see how it is supposed to be connected ? Well, given that the device name is PS2M I would expect it to be connected via serio using PS/2 protocol. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ACPI defined devices not showing up under /sys/bus/platform/devices 2014-09-19 8:47 ` Mika Westerberg 2014-09-19 11:48 ` Marcos Paulo de souza @ 2014-09-19 11:51 ` Marcos Paulo de souza 1 sibling, 0 replies; 12+ messages in thread From: Marcos Paulo de souza @ 2014-09-19 11:51 UTC (permalink / raw) To: Mika Westerberg; +Cc: Hans de Goede, linux-acpi Another info, On 09/19/2014 05:47 AM, Mika Westerberg wrote: > On Thu, Sep 18, 2014 at 06:02:40PM -0300, Marcos Paulo de souza wrote: >> Hi, >> >> On 09/18/2014 05:49 PM, Hans de Goede wrote: >>> Hi, >>> >>> On 09/18/2014 04:01 PM, Mika Westerberg wrote: >>>> On Thu, Sep 18, 2014 at 02:04:11PM +0200, Hans de Goede wrote: >>>>> Hi, >>>>> >>>>> I'm trying to help various users with Asus X450 and Asus X550 laptops >>>>> to get their touchpad to work: >>>>> >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1110011 >>>>> >>>>> We believe that this touchpad is connected over i2c, using the >>>>> i2c-designware-platform driver. >>>>> >>>>> If you look at the DSDT attached there you can clearly see >>>>> nodes defines which should lead to e.g. : >>>>> >>>>> /sys/bus/platform/devices/INT33C2:00 >>>>> >>>>> Showing up (which should then be bound by i2c-designware-platform). >>>>> >>>>> But nothing is showing up, not a single ACPI defined device shows >>>>> up actually: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> [root@asusx550 devices]# ll >>>>> insgesamt 0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 alarmtimer -> ../../../devices/platform/alarmtimer >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 asus-nb-wmi -> ../../../devices/platform/asus-nb-wmi >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 coretemp.0 -> ../../../devices/platform/coretemp.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 efi-framebuffer.0 -> ../../../devices/platform/efi-framebuffer.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 Fixed MDIO bus.0 -> ../../../devices/platform/Fixed MDIO bus.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 i8042 -> ../../../devices/platform/i8042 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 iTCO_wdt -> ../../../devices/pci0000:00/0000:00:1f.0/iTCO_wdt >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 microcode -> ../../../devices/platform/microcode >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 pcspkr -> ../../../devices/platform/pcspkr >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 regulatory.0 -> ../../../devices/platform/regulatory.0 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_ms.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_ms.0 >>>>> lrwxrwxrwx. 1 root root 0 25. Jul 23:54 rtsx_pci_sdmmc.0 -> ../../../devices/pci0000:00/0000:00:1c.2/0000:02:00.0/rtsx_pci_sdmmc.0 >>>>> lrwxrwxrwx. 1 root root 0 22. Jul 14:56 serial8250 -> ../../../devices/platform/serial8250 >>>>> >>>>> >>>>> Which is weird, since any recent machine usually has at least one or 2 >>>>> show up. >>>> It depends whether the BIOS has enabled those or not. >>>> >>>> If >>>> >>>> # cat /sys/bus/acpi/devices/INT33C2:00/status >>>> # cat /sys/bus/acpi/devices/INT33C3:00/status >>>> >>>> returns 0xf, then the device should be there, otherwise it is not. >>> Interesting. Marcos, can you give this a try please ? >> Hans, both here returned 0. As I said to you, I'm using Fedora in insecure >> mode (I don't know if this changes anything). > That just means that your BIOS has disabled these devices. Unless there > is a menu somewhere in BIOS setup to enable these, there is nothing we > can do in the kernel to make them appear. When I removed Windows, I did a mistake removing the EFI partition. I didn't boot my Fedora. After that, I created a new EFI partition with Anaconda. Maybe this can related to the problem? > >>>> The "status" refers directly shat _STA() ACPI method returns. >>> Ok, so assuming that Marcos' testing shows it is not enabled, >>> is there anything we can, could there be some ACPI call to >>> enable these devs ? >>> >>>> Note that the device could also be in PCI mode, in case lspci should >>>> show it. >>> Right, it does not show in lspci. > OK. So I think that this particular machine, either does not have Intel > LPSS (it is not Haswell-LP) or the devices have been deliberately > disabled for some reason. ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2014-09-22 9:15 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-09-18 12:04 ACPI defined devices not showing up under /sys/bus/platform/devices Hans de Goede 2014-09-18 14:01 ` Mika Westerberg 2014-09-18 20:49 ` Hans de Goede 2014-09-18 21:02 ` Marcos Paulo de souza 2014-09-19 8:47 ` Mika Westerberg 2014-09-19 11:48 ` Marcos Paulo de souza 2014-09-19 12:01 ` Mika Westerberg 2014-09-19 12:19 ` Marcos Paulo de souza 2014-09-19 12:26 ` Mika Westerberg 2014-09-20 8:48 ` Hans de Goede 2014-09-22 9:14 ` Mika Westerberg 2014-09-19 11:51 ` Marcos Paulo de souza
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox