From: Guillaume Knispel <gknispel@proformatique.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Guillaume Knispel" <gknispel@proformatique.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Len Brown" <lenb@kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
"Xavier Carcelle" <xcarcelle@avencall.com>,
"Noé Rubinstein" <nrubinstein@avencall.com>
Subject: Re: How to "register" a GSI for a non PCI non ISA device
Date: Thu, 26 Jan 2012 18:30:41 +0100 [thread overview]
Message-ID: <20120126183041.15474705@xilun> (raw)
In-Reply-To: <CAErSpo5vCr4Y3Q6U1=yYLcSBH-85koMKDte4rzw4tyuKocYXYA@mail.gmail.com>
On Thu, 26 Jan 2012 10:24:31 -0700
Bjorn Helgaas <bhelgaas@google.com> wrote:
> A driver should never need to use acpi_register_gsi() directly. It
> sounds like you have a non-PCI device that would be described as an
> ACPI device in the DSDT. In the Device definition, you include a _CRS
> method that tells the kernel what GSI it is using. The PNPACPI
> subsystem will parse _CRS and should do the acpi_register_gsi() for
> you. Then your driver would use pnp_register_driver() and pnp_irq()
> to learn the IRQ. drivers/tty/serial/8250_pnp.c is an example.
Thanks a lot, I'll look into it.
--
Guillaume Knispel
Avencall - 10 bis, rue Lucien Voilin - 92800 Puteaux
prev parent reply other threads:[~2012-01-26 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 17:42 How to "register" a GSI for a non PCI non ISA device Guillaume Knispel
2012-01-25 5:56 ` Len Brown
2012-01-25 17:23 ` Guillaume Knispel
2012-01-25 19:02 ` Konrad Rzeszutek Wilk
2012-01-26 15:07 ` Guillaume Knispel
2012-01-26 15:32 ` Konrad Rzeszutek Wilk
2012-01-26 16:22 ` Guillaume Knispel
2012-01-26 17:24 ` Bjorn Helgaas
2012-01-26 17:30 ` Guillaume Knispel [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=20120126183041.15474705@xilun \
--to=gknispel@proformatique.com \
--cc=bhelgaas@google.com \
--cc=konrad.wilk@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nrubinstein@avencall.com \
--cc=xcarcelle@avencall.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.