From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Peter Tyser <ptyser@xes-inc.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Adding interrupt support to gpio-ich driver (possibly via SCI)
Date: Fri, 04 Apr 2014 09:25:50 -0700 [thread overview]
Message-ID: <533EDD0E.8010304@roeck-us.net> (raw)
Hi all,
I have an application where I would need interrupt support for the gpio-ich driver.
More specifically, in my application some of the GPIO pins are used to report
interrupt status from a couple of connected chips. This is with a Panther Point
PCH (QM77).
I see that the gpio pins in question (in the 0..15 range) do support interrupts,
but it looks like the only configuration options are to generate SMI, SCI, or NMI.
Is there a clean way to use any of those to implement interrupt support
for this driver ? I thought about hijacking the SCI interrupt by registering
an interrupt handler with acpi_install_sci_handler(), but that would restrict
the driver to kernel only (or the acpi function would have to be exported),
and I have no idea if it would work or, more importantly, if it would be
the best approach to solve the problem, or if the result would be acceptable.
I can figure out the "working" part, but that would not help much if I would
have to carry the patch locally because it is not acceptable for upstream
integration.
Side note: gpio-ich is not currently enabled for Panther Point; that will be
a one-line separate patch for the mfd/lpc_ich driver.
Thanks,
Guenter
next reply other threads:[~2014-04-04 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 16:25 Guenter Roeck [this message]
2014-04-08 2:48 ` Adding interrupt support to gpio-ich driver (possibly via SCI) Matthew Garrett
2014-04-08 3:21 ` Guenter Roeck
2014-04-08 3:31 ` Matthew Garrett
2014-04-08 4:02 ` Guenter Roeck
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=533EDD0E.8010304@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=ptyser@xes-inc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).