From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Srinath Mannam <srinath.mannam@broadcom.com>,
Bjorn Helgaas <bhelgaas@google.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] PAXB INTx support with proper model
Date: Wed, 16 Oct 2019 10:16:07 +0100 [thread overview]
Message-ID: <20191016091607.GA22848@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <88449493-4a32-1eda-434d-317b149173eb@gmail.com>
On Tue, Oct 15, 2019 at 10:28:24AM -0700, Florian Fainelli wrote:
> On 9/4/19 10:16 AM, Florian Fainelli wrote:
> > On 8/28/19 1:54 AM, Srinath Mannam wrote:
> >> This patch series adds PCIe legacy interrupt (INTx) support to the iProc
> >> PCIe driver by modeling it with its own IRQ domain. All 4 interrupts INTA,
> >> INTB, INTC, INTD share the same interrupt line connected to the GIC
> >> in the system. This is now modeled by using its own IRQ domain.
> >>
> >> Also update all relevant devicetree files to adapt to the new model.
> >>
> >> This patch set is based on Linux-5.2-rc4.
> >>
> >> Changes from v1:
> >> - Addressed Rob, Lorenzo, Arnd's comments
> >> - Used child node for interrupt controller.
> >> - Addressed Andy Shevchenko's comments
> >> - Replaced while loop with do-while.
> >
> > Lorenzo, Bjorn, if you are good with the binding and PCI host driver
> > changes, you can take patches 1-2 through your tree, and I will queue up
> > the others through the Broadcom ARM SoC pull requests. If not, please
> > feel free to add a:
> >
> > Acked-by: Florian Fainelli <f.fainelli@gmail.com>
>
> I am starting to queue Device Tree patches for 5.5 and I need to know
> whether I should be picking up patches 2 through 6, or if you are going
> to do this, thank you.
I am going to do this but I have comments on the patches they will
have to be updated anyway.
Thanks and apologies for the delay.
Lorenzo
> >> Ray Jui (6):
> >> dt-bindings: pci: Update iProc PCI binding for INTx support
> >> PCI: iproc: Add INTx support with better modeling
> >> arm: dts: Change PCIe INTx mapping for Cygnus
> >> arm: dts: Change PCIe INTx mapping for NSP
> >> arm: dts: Change PCIe INTx mapping for HR2
> >> arm64: dts: Change PCIe INTx mapping for NS2
> >>
> >> .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 48 ++++++++--
> >> arch/arm/boot/dts/bcm-cygnus.dtsi | 30 ++++++-
> >> arch/arm/boot/dts/bcm-hr2.dtsi | 30 ++++++-
> >> arch/arm/boot/dts/bcm-nsp.dtsi | 45 ++++++++--
> >> arch/arm64/boot/dts/broadcom/northstar2/ns2.dtsi | 28 +++++-
> >> drivers/pci/controller/pcie-iproc.c | 100 ++++++++++++++++++++-
> >> drivers/pci/controller/pcie-iproc.h | 6 ++
> >> 7 files changed, 260 insertions(+), 27 deletions(-)
> >>
> >
> >
>
>
> --
> Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-16 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:54 [PATCH v2 0/6] PAXB INTx support with proper model Srinath Mannam
2019-08-28 8:54 ` [PATCH v2 1/6] dt-bindings: pci: Update iProc PCI binding for INTx support Srinath Mannam
2019-09-02 13:38 ` Rob Herring
2019-10-16 10:16 ` Lorenzo Pieralisi
2019-08-28 8:54 ` [PATCH v2 2/6] PCI: iproc: Add INTx support with better modeling Srinath Mannam
2019-08-28 8:54 ` [PATCH v2 3/6] arm: dts: Change PCIe INTx mapping for Cygnus Srinath Mannam
2019-08-28 8:54 ` [PATCH v2 4/6] arm: dts: Change PCIe INTx mapping for NSP Srinath Mannam
2019-08-28 8:54 ` [PATCH v2 5/6] arm: dts: Change PCIe INTx mapping for HR2 Srinath Mannam
2019-08-28 8:54 ` [PATCH v2 6/6] arm64: dts: Change PCIe INTx mapping for NS2 Srinath Mannam
2019-09-04 17:16 ` [PATCH v2 0/6] PAXB INTx support with proper model Florian Fainelli
2019-10-15 17:28 ` Florian Fainelli
2019-10-16 9:16 ` Lorenzo Pieralisi [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=20191016091607.GA22848@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinath.mannam@broadcom.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;
as well as URLs for NNTP newsgroup(s).