[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJsb53VXiUfjGBXK37dBEi1r-PXVohg-c-7_x63R04VMA@mail.gmail.com>
Date: Fri, 9 Oct 2015 08:54:33 -0500
From: Rob Herring <robh@...nel.org>
To: Liviu Dudau <Liviu.Dudau@....com>
Cc: Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Mark Rutland <mark.rutland@....com>,
Linus Walleij <linus.walleij@...aro.org>,
Robin Murphy <robin.murphy@....com>,
Rob Herring <robh+dt@...nel.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Arnd Bergmann <arnd@...db.de>, Jon Medhurst <tixy@...aro.org>,
linux-pci <linux-pci@...r.kernel.org>,
device-tree <devicetree@...r.kernel.org>,
LAKML <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/4] arm64: Juno: Add support for the PCIe host bridge on
Juno R1
On Fri, Oct 9, 2015 at 8:45 AM, Liviu Dudau <Liviu.Dudau@....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@....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@...00000 {
> + 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. Perhaps the firmware did not
setup something correctly.
> + device_type = "pci";
> + reg = <0 0x40000000 0 0x10000000>; /* ECAM config space */
> + bus-range = <0 255>;
> + linux,pci-domain = <0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + dma-coherent;
> + ranges = <0x01000000 0x00 0x5f800000 0x00 0x5f800000 0x0 0x00800000
> + 0x02000000 0x00 0x50000000 0x00 0x50000000 0x0 0x08000000
> + 0x42000000 0x40 0x00000000 0x40 0x00000000 0x1 0x00000000>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0 0 0 1 &gic 0 0 0 136 4
> + 0 0 0 2 &gic 0 0 0 137 4
> + 0 0 0 3 &gic 0 0 0 138 4
> + 0 0 0 4 &gic 0 0 0 139 4>;
> + msi-parent = <&v2m_0>;
> + };
> };
>
> &memtimer {
> --
> 2.6.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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/
Powered by blists - more mailing lists