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-next>] [day] [month] [year] [list]
Date: Tue, 12 Mar 2024 20:28:21 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: "x86@...nel.org" <x86@...nel.org>, "linux-acpi@...r.kernel.org"
	<linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: Adding an interrupt to a PCI device via an ACPI entry

Hi All,

Is there a way to add information about a PCI device via an ACPI entry? 
I'm trying to deal with a device that has an erratum where regular PCI-e 
MSI interrupts don't work. The workaround is to connect a dedicated INT 
output line to an interrupt input on the board. The hardware design has 
done this but I'm trying to figure out how to make that work with ACPI 
describing the hardware.

I know in devicetree land I can do this with something like

&pcic {
                 mydevice@1,0 {
                         compatible = "pci1234,5678";
                         reg = <0x00000000 0 0 0 0>;
                         interrupt-parent = <&intc>;
                         interrupts = <1 IRQ_TYPE_LEVEL_LOW>;
                 };
};

And then when my driver is bound to device the usual irq resource stuff 
will give me the right interrupt line.

Is there a way of expressing this kind of thing in ACPI?

Thanks,
Chris

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ