[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD



Le lun. 11 déc. 2023 à 10:18, Sébastien Chaumat <euidzero@xxxxxxxxx> a écrit :
>
> > On 05.12.2023 21:31, Sébastien Chaumat wrote:
> > >> [    2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
> > >
> > > Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> > > ioapic-edge and IRQ9 to ioapic-level ?
> > >
> > > IR-IO-APIC    7-fasteoi   pinctrl_amd
> > > IR-IO-APIC    9-fasteoi   acpi
> > >
> > > to (xen 4.18.0)
> > >
> > > xen-pirq     -ioapic-edge  pinctrl_amd
> > > xen-pirq     -ioapic-level  acpi
> > >
> > > ?

This look similar to
https://yhbt.net/lore/all/20201006044941.fdjsp346kc5thyzy@Rk/t/

This issue seems that IRQ 7 (the GPIO controller) is natively fasteoi
(so level type) while in xen it  is mapped to oapic-edge  instead of
oapic-level
as the SSDT indicates :

 Device (GPIO)

     {
         Name (_HID, "AMDI0030")  // _HID: Hardware ID
         Name (_CID, "AMDI0030")  // _CID: Compatible ID
         Name (_UID, Zero)  // _UID: Unique ID
         Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
         {
             Name (RBUF, ResourceTemplate ()
             {
                 Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
                 {
                     0x00000007,
           }
Any idea why ?

Sébastien



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.