https://bugzilla.kernel.org/show_bug.cgi?id=201817
Hans de Goede (jwrdego...@fedoraproject.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwrdego...@fedoraproject.or
| |g
Component|Other |x86-64
Assignee|acpi_ot...@kernel-bugs.osdl |platform_x86_64@kernel-bugs
|.org |.osdl.org
Product|ACPI |Platform Specific/Hardware
--- Comment #4 from Hans de Goede (jwrdego...@fedoraproject.org) ---
I discussed this a bit on the mailinglist. Here are the relevant parts of the
discussion:
Me:
The amd_gpio chip/driver appears to be the only driver
connected to IRQ 7, so I think there is an issue with the
amd_gpio driver where it does not properly clear the interrupt
source. E.g. it might be that the BIOS requested interrupts
on a GPIO which Linux does not monitor and that the driver
does not disable this GPIO-IRQ on probe and since it is not
handling that pin in IRQ mode also does not clear it.
Anyways that is just a theory. It would greatly help if
someone who knows the amd_gpio driver better could take
a look.
Reply by Daniel Drake:
Sorry that I can't be much help here - I don't have access to any
useful info beyond the source code already present in Linux.
Maybe you could explore your theory by dumping the GPIO/GPIO-INT
enable regs, see if any of them are marked as enabled by something
other than Linux.
###
I'm afraid I don't have time to look into this myself atm. Maybe someone can
add some printk calls to drivers/pinctrl/pinctrl-amd.c to dump relevant
register values as Daniel suggested and see if that yields any useful info?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
