From: bharatku@xilinx.com (bharat kumar gogada)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64 PCIe legacy interrupts
Date: Tue, 6 Oct 2015 10:17:11 +0000 (UTC) [thread overview]
Message-ID: <loom.20151006T121259-647@post.gmane.org> (raw)
In-Reply-To: CAHM4w1kzt0wCCxfvofXqzgK=Te50_1ZsYnApbEojMQq8x+wcdA@mail.gmail.com
Pratyush Anand <pratyush.anand <at> gmail.com> writes:
>
> On Thu, Oct 1, 2015 at 5:59 PM, bharat kumar gogada <bharatku <at>
xilinx.com> wrote:
> > Hi, in ARM32 bit pci_fixup_irqs is being used to support legacy interrupts,
> > in ARM64 how legacy interrupts are being handled
>
> See, arch/arm64/kernel/pci.c:pcibios_add_devices()
>
Thanks.
I have a confusion in handling legacy interrupts in driver, I'm seeing that
for legacy handling there is separate node being created. Ex: for
pcie-xilinx.c the following node is being used
pcie_intc: interrupt-controller {
interrupt-controller;
#address-cells = <0>;
#interrupt-cells = <1>;
};
Why do we need a separate child node for legacy handling and why is the
address cells parameter assigned zero value
next prev parent reply other threads:[~2015-10-06 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:29 ARM64 PCIe legacy interrupts bharat kumar gogada
2015-10-05 5:45 ` Pratyush Anand
2015-10-06 10:17 ` bharat kumar gogada [this message]
2015-10-06 10:30 ` Arnd Bergmann
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=loom.20151006T121259-647@post.gmane.org \
--to=bharatku@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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