From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Hans de Goede <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Failed IRQ assignment for INT0002 on Braswell
Date: Tue, 21 Nov 2017 23:35:28 +0100 [thread overview]
Message-ID: <1902393.IdeYHqtVB8@natalenko.name> (raw)
Hi, Hans.
v4.13 kernel introduced new fancy warning in the dmesg:
===
kernel: acpi INT0002:00: Device [GPED] is in always present list
kernel: genirq: Flags mismatch irq 9. 00010084 (INT0002) vs. 00002080 (acpi)
kernel: INT0002 Virtual GPIO INT0002:00: Error requesting IRQ 9: -16
kernel: INT0002 Virtual GPIO: probe of INT0002:00 failed with error -16
===
Looking at git log, I've found that this driver was indeed introduced in v4.13
by the following commit:
===
commit 63dada87f7ef7d4a536765c816fbbe7c4b9f3c85
Author: Hans de Goede <hdegoede@redhat.com>
Date: Mon Jun 12 22:55:46 2017 +0200
platform/x86: Add driver for ACPI INT0002 Virtual GPIO device
===
I've checked DSDT disassembly for this device, and here is relevant snippet
[1]. The only thing I currently understand there is that IRQ 9 is hard coded
(line 64), but I'm not sure where those flags come from.
The hardware in J3710 CPU on ASRock J3710-ITX motherboard.
Next, I've found that you also faced this warning and posted some RFC patch
[2], but unfortunately I do not see what that discussion ended up with.
It is not that I really need GPIO on this board, but it would be nice to get
rid of this warning. Could you please point me to a possible fix or a way for
further investigation?
Thanks.
Regards,
Oleksandr
[1] https://gist.github.com/2c69d6e4eb4b5c256601847a9c6aec45
[2] https://patchwork.kernel.org/patch/9671783/
next reply other threads:[~2017-11-21 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 22:35 Oleksandr Natalenko [this message]
2017-11-22 10:48 ` Failed IRQ assignment for INT0002 on Braswell Hans de Goede
2017-11-22 12:48 ` Oleksandr Natalenko
2017-11-22 15:50 ` Hans de Goede
2017-11-22 15:50 ` Hans de Goede
2017-11-22 18:13 ` Oleksandr Natalenko
2017-11-23 21:08 ` Andy Shevchenko
2017-11-23 21:15 ` Oleksandr Natalenko
2017-11-23 21:22 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1902393.IdeYHqtVB8@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.