On 04/07/2014 08:31 PM, Matthew Garrett wrote:
On Mon, Apr 07, 2014 at 08:21:00PM -0700, Guenter Roeck wrote:
On 04/07/2014 07:48 PM, Matthew Garrett wrote:
You shouldn't need to install an SCI handler - the way the hardware will
generate an SCI is to raise a GPE. If you know which GPE the devi
On Mon, Apr 07, 2014 at 08:21:00PM -0700, Guenter Roeck wrote:
> On 04/07/2014 07:48 PM, Matthew Garrett wrote:
> >You shouldn't need to install an SCI handler - the way the hardware will
> >generate an SCI is to raise a GPE. If you know which GPE the device
> >raises (my recollection is that for m
On 04/07/2014 07:48 PM, Matthew Garrett wrote:
On Fri, Apr 04, 2014 at 09:25:50AM -0700, Guenter Roeck wrote:
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_insta
On Fri, Apr 04, 2014 at 09:25:50AM -0700, Guenter Roeck wrote:
> 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
>
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 quest
5 matches
Mail list logo
