| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-id: <000001ce3438$b136e1e0$13a4a5a0$%han@samsung.com>
Date: Mon, 08 Apr 2013 18:08:53 +0900
From: Jingoo Han <jg1.han@...sung.com>
To: 'Jason Gunthorpe' <jgunthorpe@...idianresearch.com>
Cc: 'Kukjin Kim' <kgene.kim@...sung.com>,
'Bjorn Helgaas' <bhelgaas@...gle.com>,
linux-samsung-soc@...r.kernel.org, linux-pci@...r.kernel.org,
devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
'Grant Likely' <grant.likely@...retlab.ca>,
'Andrew Murray' <andrew.murray@....com>,
'Thomas Petazzoni' <thomas.petazzoni@...e-electrons.com>,
'Thierry Reding' <thierry.reding@...onic-design.de>,
'Jason Gunthorpe' <jgunthorpe@...idianresearch.com>,
'Surendranath Gurivireddy Balla' <suren.reddy@...sung.com>,
'Siva Reddy Kallam' <siva.kallam@...sung.com>,
'Thomas Abraham' <thomas.abraham@...aro.org>,
'Jingoo Han' <jg1.han@...sung.com>
Subject: Re: [PATCH 6/6] ARM: dts: Add pcie controller node for Samsung
EXYNOS5440 SoC
On Saturday, March 23, 2013 1:09 PM, Jingoo Han wrote:
>
> Exynos5440 has two PCIe controllers which can be used as root complex
> for PCIe interface.
>
> Signed-off-by: Jingoo Han <jg1.han@...sung.com>
> ---
> arch/arm/boot/dts/exynos5440-ssdk5440.dts | 8 +++++++
> arch/arm/boot/dts/exynos5440.dtsi | 32 +++++++++++++++++++++++++++++
> 2 files changed, 40 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/dts/exynos5440-ssdk5440.dts b/arch/arm/boot/dts/exynos5440-ssdk5440.dts
> index a21eb4c..746f9fc 100644
> --- a/arch/arm/boot/dts/exynos5440-ssdk5440.dts
> +++ b/arch/arm/boot/dts/exynos5440-ssdk5440.dts
> @@ -34,4 +34,12 @@
> clock-frequency = <50000000>;
> };
> };
> +
> + pcie0@...00000 {
> + reset-gpio = <5>;
> + };
> +
> + pcie1@...00000 {
> + reset-gpio = <22>;
> + };
> };
> diff --git a/arch/arm/boot/dts/exynos5440.dtsi b/arch/arm/boot/dts/exynos5440.dtsi
> index c374a31..41b2d2c 100644
> --- a/arch/arm/boot/dts/exynos5440.dtsi
> +++ b/arch/arm/boot/dts/exynos5440.dtsi
> @@ -178,4 +178,36 @@
> clocks = <&clock 21>;
> clock-names = "rtc";
> };
> +
> + pcie0@...00000 {
> + compatible = "samsung,exynos5440-pcie";
> + reg = <0x40000000 0x4000
> + 0x290000 0x1000
> + 0x270000 0x1000
> + 0x271000 0x40>;
> + interrupts = <0 20 0>, <0 21 0>, <0 22 0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + bus-range = <0x0 0xf>;
> + ranges = <0x00000800 0 0x40000000 0x40000000 0 0x00200000 /* configuration space */
> + 0x81000000 0 0 0x40200000 0 0x00004000 /* downstream I/O */
> + 0x82000000 0 0 0x40204000 0 0x10000000>; /* non-prefetchable memory */
> + };
> +
> + pcie1@...00000 {
> + compatible = "samsung,exynos5440-pcie";
> + reg = <0x60000000 0x4000
> + 0x2a0000 0x1000
> + 0x272000 0x1000
> + 0x271040 0x40>;
> + interrupts = <0 23 0>, <0 24 0>, <0 25 0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + bus-range = <0x0 0xf>;
> + ranges = <0x00000800 0 0x60000000 0x60000000 0 0x00200000 /* configuration space */
> + 0x81000000 0 0 0x60200000 0 0x00004000 /* downstream I/O */
> + 0x82000000 0 0 0x60204000 0 0x10000000>; /* non-prefetchable memory */
> + };
Hi Jason,
I have a question.
Now, I am reviewing the Tegra PCIe, Marvell PCIe patchset.
However, in the case of Exynos PCIe,
'downstream I/O' and 'non-prefetchable memory' are different between PCIe0 and PCIe1.
These regions are not shared.
PCIe0:
ranges = <0x00000800 0 0x40000000 0x40000000 0 0x00200000 /* configuration space */
0x81000000 0 0 0x40200000 0 0x00004000 /* downstream I/O */
0x82000000 0 0 0x40204000 0 0x10000000>; /* non-prefetchable memory */
PCIe1:
ranges = <0x00000800 0 0x40000000 0x40000000 0 0x00200000 /* configuration space */
0x81000000 0 0 0x40200000 0 0x00004000 /* downstream I/O */
0x82000000 0 0 0x40204000 0 0x10000000>; /* non-prefetchable memory */
PCIe0 uses 0x40000000~0x5fffffff, PCI1 uses 0x60000000~0x7fffffff.
How can I handle this? :)
The following is right?
+ pcie-controller {
.....
+ ranges = <0x82000000 0 0x40000000 0x40000000 0 0x00200000 /* port 0 registers */
+ 0x82000000 0 0x60000000 0x60000000 0 0x00200000 /* port 1 registers */
+ 0x81000000 0 0 0x40200000 0 0x00004000 /* port 0 downstream I/O */
+ 0x81000000 0 0 0x60200000 0 0x00004000 /* port 1 downstream I/O */
+ 0x82000000 0 0x40204000 0x40204000 0 0x10000000>; /* port 0 non-prefetchable memory */
+ 0x82000000 0 0x40204000 0x60204000 0 0x10000000>; /* port 1 non-prefetchable memory */
+
+ pci@1,0 {
+ device_type = "pci";
+ assigned-addresses = <0x82000800 0 0x40000000 0 0x00200000
+ 0x81000800 0 0x40200000 0 0x00004000
+ 0x81000800 0 0x40204000 0 0x10000000>;
.....
+ pci@2,0 {
+ device_type = "pci";
+ assigned-addresses = <0x82000800 0 0x60000000 0 0x00200000
+ 0x81000800 0 0x60200000 0 0x00004000
+ 0x81000800 0 0x60204000 0 0x10000000>;
Best regards,
Jingoo Han
> };
> --
> 1.7.2.5
--
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