From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Guillaume Knispel <gknispel@proformatique.com>
Cc: "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: Wed, 25 Jan 2012 14:02:14 -0500 [thread overview]
Message-ID: <20120125190214.GC18606@phenom.dumpdata.com> (raw)
In-Reply-To: <20120125182314.7834c75b@xilun>
On Wed, Jan 25, 2012 at 06:23:14PM +0100, Guillaume Knispel wrote:
> On Wed, 25 Jan 2012 00:56:53 -0500
> Len Brown <lenb@kernel.org> wrote:
>
> > On 01/24/2012 12:42 PM, Guillaume Knispel wrote:
> >
> > > Hi,
> > >
> > > I'm building a PC platform with additional non-PCI and non-ISA devices:
> > > they are basically simple telecom chipsets connected to an SPI and an
> > > old school parallel bus (Intel LEB bus) and GPIO pins that can be used
> > > as interrupts through the IO APIC which exposes 40 GSI. From the point
> > > of view of the software the SPI, LEB, and GPIO are provided by PCI
> > > devices (in reality they are embedded controllers in an Intel SoC
> > > 80579). Anyway I'm not sure the additional GSI are described anywhere
> > > in whatever black magic ACPI / legacy BIOS table they could be
> > > (but I've complete control over the FW, so I can had whatever is
> > > needed when I know it).
> >
> > What is the benefit of implementing ACPI on this custom system?
>
> For our short term project it seems to be more a necessity than a
> benefit. ACPI is supported by the SoC, tables are already largely
> provided by Coreboot, the whole x86 ecosystem including Linux is more
> or less based around ACPI, and my whole interrogation comes from the
> fact that *acpi*_register_gsi() seems to be necessary to configure a
> GSI in the APIC but is not exported anymore, so my guess is that if I
Hm, isn't it __acpi_register_gsi?
> can't call it explicitly from my LKM, there should better be a way to
> make it be called when an ACPI thing is done, or maybe a legacy table
> parsed.
Can you do it the way xen does? Look in arch/x86/xen/pci.c
>
> As we first target an unmodified (if possible) 2.6.32 kernel from
> Debian Squeeze, I can't just re-export acpi_register_gsi() and call it
> a day. (If I've no other choice I'll obviously do it, but this would be
> quite bad for future maintenance).
Oh wow. That is ancient. 3.2?
next prev parent reply other threads:[~2012-01-25 19:04 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 [this message]
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
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=20120125190214.GC18606@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gknispel@proformatique.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 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).