linux-kernel - Re: How to "register" a GSI for a non PCI non ISA device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120126183041.15474705@xilun>
Date:	Thu, 26 Jan 2012 18:30:41 +0100
From:	Guillaume Knispel <gknispel@...formatique.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Guillaume Knispel <gknispel@...formatique.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org,
	Xavier Carcelle <xcarcelle@...ncall.com>,
	Noé Rubinstein <nrubinstein@...ncall.com>
Subject: Re: How to "register" a GSI for a non PCI non ISA device

On Thu, 26 Jan 2012 10:24:31 -0700
Bjorn Helgaas <bhelgaas@...gle.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/