linux-kernel - Re: [PATCH] Add MSI interrupts to DTS of MPC8315E-RDB

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]

Date:	Sat, 6 Jun 2009 10:44:10 +1000
From:	David Gibson <david@...son.dropbear.id.au>
To:	leon.woestenberg@...il.com
Cc:	linuxppc-dev@...abs.org, galak@...nel.crashing.org,
	linux-kernel@...r.kernel.org,
	Leon Woestenberg <leon@...ebranch.com>
Subject: Re: [PATCH] Add MSI interrupts to DTS of MPC8315E-RDB

On Fri, Jun 05, 2009 at 07:45:41AM -0700, leon.woestenberg@...il.com wrote:
> The PCIe MSI interrupts are missing from the device tree source, and
> thus were not enabled. This patch adds them.
> 
> Tested to work on MPC8315E-RDB with custom FPGA PCIe device.
> 
> Signed-off-by: Leon Woestenberg <leon@...ebranch.com>
> Tested-by: Leon Woestenberg <leon@...ebranch.com>
> 
> diff --git a/arch/powerpc/boot/dts/mpc8315erdb.dts b/arch/powerpc/boot/dts/mpc8315erdb.dts
> index 3f4c5fb..4f04667 100644
> --- a/arch/powerpc/boot/dts/mpc8315erdb.dts
> +++ b/arch/powerpc/boot/dts/mpc8315erdb.dts
> @@ -322,6 +322,21 @@
>  			reg = <0x700 0x100>;
>  			device_type = "ipic";
>  		};
> +
> +		ipic-msi@7c0 {
> +			compatible = "fsl,ipic-msi";
> +                        reg = <0x7c0 0x40>;
> +                        msi-available-ranges = <0 0x100>;

This patch appears not to use consistent whitespace formatting.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson
--
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/