From: Mark Rutland <mark.rutland@arm.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Rob Herring <robh@kernel.org>, Jon Medhurst <tixy@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-pci <linux-pci@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
device-tree <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Robin Murphy <robin.murphy@arm.com>,
LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/4] arm64: Juno: Add support for the PCIe host bridge on Juno R1
Date: Fri, 9 Oct 2015 16:44:08 +0100 [thread overview]
Message-ID: <20151009154408.GD21629@leverpostej> (raw)
In-Reply-To: <20151009141107.GD3394@e106497-lin.cambridge.arm.com>
On Fri, Oct 09, 2015 at 03:11:07PM +0100, Liviu Dudau wrote:
> On Fri, Oct 09, 2015 at 08:54:33AM -0500, Rob Herring wrote:
> > On Fri, Oct 9, 2015 at 8:45 AM, Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> > > Juno R1 board sports a functional PCIe host bridge that is
> > > compliant with the SBSA standard found here[1]. With the right
> > > firmware that initialises the XpressRICH3 controller one can
> > > use the generic Host Bridge driver to use the PCIe hardware.
> > >
> > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> > >
> > > [1] http://infocenter.arm.com/help/topic/com.arm.doc.den0029a/
> > > ---
> > > arch/arm64/boot/dts/arm/juno-r1.dts | 20 ++++++++++++++++++++
> > > 1 file changed, 20 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/arm/juno-r1.dts b/arch/arm64/boot/dts/arm/juno-r1.dts
> > > index c627511..a702a6b 100644
> > > --- a/arch/arm64/boot/dts/arm/juno-r1.dts
> > > +++ b/arch/arm64/boot/dts/arm/juno-r1.dts
> > > @@ -109,6 +109,26 @@
> > >
> > > #include "juno-base.dtsi"
> > >
> > > + pcie-controller@40000000 {
> > > + compatible = "pci-host-ecam-generic";
> >
> > I think this is the first case of real h/w using this. We should have
> > a specific compatible here additionally.
>
> Or maybe I can claim the use of the string on account on being the first on arm64 ;)
>
> I can add a vendor prefix if you want, but pci-host-generic is going to ignore it
> *because* it is trying to be a generic driver.
The point here is to have the string ready if we need it later, so it's
fine that it's not used currently.
Rob's suggestion is that the compatible list should look something like:
compatible = "arm,juno-r1-pcie", "plda,xpressrich3", "pci-host-ecam-generic";
We can match on "pci-host-ecam-generic" for now (and hopefully forever),
but if for some reason we need to special-case this host controller (or
Juno's integration thereof), we can do that based on the compatible
string.
Thanks,
Mark.
next prev parent reply other threads:[~2015-10-09 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 13:45 [PATCH 0/4] arm64: Juno: Add support for PCIe on R1 board Liviu Dudau
2015-10-09 13:45 ` [PATCH 1/4] pci: Add PLDA's XpressRICH3 PCIe host bridge PCI ID Liviu Dudau
2015-10-09 13:45 ` [PATCH 2/4] PCI: Add quirk for PLDA's XpressRICH3 host bridge class Liviu Dudau
2015-10-09 13:45 ` [PATCH 3/4] arm64: Juno: Add support for the PCIe host bridge on Juno R1 Liviu Dudau
2015-10-09 13:54 ` Rob Herring
2015-10-09 14:11 ` Liviu Dudau
[not found] ` <20151009141107.GD3394-2JSQmVVBSi7ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2015-10-09 14:18 ` Will Deacon
2015-10-09 15:44 ` Mark Rutland [this message]
2015-10-09 15:49 ` Arnd Bergmann
2015-10-09 16:09 ` Liviu Dudau
2015-10-09 16:32 ` Mark Rutland
2015-10-09 16:41 ` Liviu Dudau
2015-10-09 13:45 ` [PATCH 4/4] arm64: defconfig: Enable PCI generic host bridge by default Liviu Dudau
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=20151009154408.GD21629@leverpostej \
--to=mark.rutland@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tixy@linaro.org \
--cc=will.deacon@arm.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).