From: Kumar Gala <galak@kernel.crashing.org>
To: Prabhakar Kushwaha <prabhakar@freescale.com>
Cc: meet2prabhu@gmail.com, devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/85xx:DTS: Fix PCIe IDSEL for Px020RDB
Date: Thu, 19 May 2011 01:16:28 -0500 [thread overview]
Message-ID: <12CBD4BB-FC1B-4A44-91A2-B6E00AC251D8@kernel.crashing.org> (raw)
In-Reply-To: <1303272764-15333-1-git-send-email-prabhakar@freescale.com>
On Apr 19, 2011, at 11:12 PM, Prabhakar Kushwaha wrote:
> PCIe device in legacy mode can trigger interrupts using the wires =
#INTA, #INTB
> ,#INTC and #INTD. PCI devices are obligated to use #INTx for =
interrupts under
> legacy mode. Each PCI slot or device is typically wired to different =
inputs on
> the interrupt controller.=20
>=20
> So, Define interrupt-map and interrupt-map-mask properties for device =
tree to
> of map each PCI interrupt signal to the inputs of the interrupt =
controller.
>=20
> Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
> ---
> Based upon =
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git(branc=
h master)
>=20
> This patch has depedency on following 2 patches
> -- powerpc/85xx: P2020 DTS: re-organize dts files
> -- powerpc/85xx: P1020 DTS : re-organize dts files
>=20
> arch/powerpc/boot/dts/p1020rdb.dts | 16 ++++++++++++++++
> arch/powerpc/boot/dts/p2020rdb.dts | 16 ++++++++++++++++
> arch/powerpc/boot/dts/p2020rdb_camp_core0.dts | 8 ++++++++
> arch/powerpc/boot/dts/p2020rdb_camp_core1.dts | 8 ++++++++
> 4 files changed, 48 insertions(+), 0 deletions(-)
applied to next
- k=
prev parent reply other threads:[~2011-05-19 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 4:12 [PATCH] powerpc/85xx:DTS: Fix PCIe IDSEL for Px020RDB Prabhakar Kushwaha
2011-05-19 6:16 ` Kumar Gala [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=12CBD4BB-FC1B-4A44-91A2-B6E00AC251D8@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meet2prabhu@gmail.com \
--cc=prabhakar@freescale.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