All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Antonio Ospite <ao2@ao2.it>
Cc: linux-input@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-acpi@vger.kernel.org, Bastien Nocera <hadess@hadess.net>,
	Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: About Goodix-TS on Bay Trail, and ACPI and interrupts
Date: Mon, 9 Feb 2015 15:25:05 +0200	[thread overview]
Message-ID: <20150209132505.GG1480@lahna.fi.intel.com> (raw)
In-Reply-To: <20150206170013.90a20c05fae6393ea92312df@ao2.it>

On Fri, Feb 06, 2015 at 05:00:13PM +0100, Antonio Ospite wrote:
> Last doubt, now that I am fixing the DSDT I am going to add an
> Interrupt resource, but what is the correct way to specify its value?
> Pin 3 of GPO2 is mapped to IRQ 220 by the mainline kernel, so I added
> this:
> 
>   Interrupt (ResourceConsumer, Edge, ActiveHigh, Exclusive, ,, )
>   {
>     0x000000DC,
>   }
> 
> And it works, but doesn't this rely on the way linux maps interrupt
> numbers? Is this going to be OS agnostic? My doubt arises from the
> fact that on the Android kernel the same pin is mapped to IRQ
> 389.

You should specify GpioInt() instead and turn it to interrupt using
gpiod_to_irq().

      reply	other threads:[~2015-02-09 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  0:03 About Goodix-TS on Bay Trail, and ACPI and interrupts Antonio Ospite
2015-01-19 15:37 ` Benjamin Tissoires
2015-01-20 10:05   ` Mika Westerberg
2015-01-20 16:31     ` Benjamin Tissoires
2015-01-21 10:09       ` Mika Westerberg
2015-01-20 16:56     ` Antonio Ospite
2015-01-21 10:16       ` Mika Westerberg
2015-01-27 14:45         ` Antonio Ospite
2015-02-06 16:00           ` Antonio Ospite
2015-02-09 13:25             ` Mika Westerberg [this message]

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=20150209132505.GG1480@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=ao2@ao2.it \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hadess@hadess.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.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 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.