From: Mark Rutland <mark.rutland@arm.com>, marc.zyngier@arm.com
To: Zhiqiang Hou <B48286@freescale.com>, marc.zyngier@arm.com
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"Shaohui.Xie@freescale.com" <Shaohui.Xie@freescale.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"bhupesh.sharma@freescale.com" <bhupesh.sharma@freescale.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"wim@iguana.be" <wim@iguana.be>,
"Wenbin.Song@freescale.com" <Wenbin.Song@freescale.com>,
"scottwood@freescale.com" <scottwood@freescale.com>,
"Mingkai.Hu@freescale.com" <Mingkai.Hu@freescale.com>,
"leoli@freescale.com" <leoli@freescale.com>
Subject: Re: [PATCH 4/6] arm64/ls1043a: add DTS for Freescale LS1043A SoC
Date: Tue, 22 Sep 2015 02:24:03 +0100 [thread overview]
Message-ID: <20150922012403.GA1535@svinekod> (raw)
In-Reply-To: <1442838158-2964-5-git-send-email-B48286@freescale.com>
Hi,
> +/memreserve/ 0x80000000 0x00010000;
Why is this necessary?
If this is necessary, please add a comment stating what this is for.
> + cpu@3 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a53";
> + reg = <0x0 0x3>;
> + clocks = <&clockgen 1 0>;
> + };
Missing enable-method properties on all the secondary CPUs.
[...]
> + gic: interrupt-controller@1400000 {
> + compatible = "arm,gic-400";
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + reg = <0x0 0x1401000 0 0x1000>, /* GICD */
> + <0x0 0x1402000 0 0x1000>, /* GICC */
> + <0x0 0x1404000 0 0x2000>, /* GICH */
> + <0x0 0x1406000 0 0x2000>; /* GICV */
> + interrupts = <1 9 0xf08>;
> + };
These sizes don't look right.
To the best of my knowledge, GICC (and GICV) should be 0x2000 in size, while
GICD and GICH should be 0x1000.
[...]
> + ifc: ifc@1530000 {
> + compatible = "fsl,ifc", "simple-bus";
> + reg = <0x0 0x1530000 0x0 0x10000>;
> + interrupts = <0 43 0x4>;
> + };
Why simple-bus?
> + clockgen: clocking@1ee1000 {
> + compatible = "fsl,ls1043a-clockgen";
> + reg = <0x0 0x1ee1000 0x0 0x1000>;
> + #clock-cells = <2>;
> + clocks = <&sysclk>;
> + sysclk: sysclk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <100000000>;
> + clock-output-names = "sysclk";
> + };
> + };
Why does this fixed clock live under the clockgen? It should live directly
under the root node.
[...]
> + pcie@3400000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03400000 0x0 0x00100000 /* controller registers */
> + 0x40 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 118 0x4>, /* controller interrupt */
> + <0 117 0x4>; /* PME interrupt */
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <4>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x40 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x40 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi1>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 110 0x4>,
> + <0000 0 0 2 &gic 0 111 0x4>,
> + <0000 0 0 3 &gic 0 112 0x4>,
> + <0000 0 0 4 &gic 0 113 0x4>;
> + };
> +
> + pcie@3500000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03500000 0x0 0x00100000 /* controller registers */
> + 0x48 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 128 0x4>,
> + <0 127 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x48 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x48 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi2>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 120 0x4>,
> + <0000 0 0 2 &gic 0 121 0x4>,
> + <0000 0 0 3 &gic 0 122 0x4>,
> + <0000 0 0 4 &gic 0 123 0x4>;
> + };
> +
> + pcie@3600000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03600000 0x0 0x00100000 /* controller registers */
> + 0x50 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 162 0x4>,
> + <0 161 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x50 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x50 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi3>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 154 0x4>,
> + <0000 0 0 2 &gic 0 155 0x4>,
> + <0000 0 0 3 &gic 0 156 0x4>,
> + <0000 0 0 4 &gic 0 157 0x4>;
> + };
You wait ages for a bus, then three show up at once...
> +
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0x0 0x80000000 0 0x80000000>;
> + /* DRAM space 1 - 2 GB DRAM */
I don't understand the comment. This describes 2GB at 2GB.
Does the bootloader overwrite this?
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>, marc.zyngier@arm.com
To: Zhiqiang Hou <B48286@freescale.com>, marc.zyngier@arm.com
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"Shaohui.Xie@freescale.com" <Shaohui.Xie@freescale.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"bhupesh.sharma@freescale.com" <bhupesh.sharma@freescale.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"wim@iguana.be" <wim@iguana.be>,
"Wenbin.Song@freescale.com" <Wenbin.Song@freescale.com>,
"scottwood@freescale.com" <scottwood@freescale.com>,
"Mingkai.Hu@freescale.com" <Mingkai.Hu@frees>
Subject: Re: [PATCH 4/6] arm64/ls1043a: add DTS for Freescale LS1043A SoC
Date: Tue, 22 Sep 2015 02:24:03 +0100 [thread overview]
Message-ID: <20150922012403.GA1535@svinekod> (raw)
In-Reply-To: <1442838158-2964-5-git-send-email-B48286@freescale.com>
Hi,
> +/memreserve/ 0x80000000 0x00010000;
Why is this necessary?
If this is necessary, please add a comment stating what this is for.
> + cpu@3 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a53";
> + reg = <0x0 0x3>;
> + clocks = <&clockgen 1 0>;
> + };
Missing enable-method properties on all the secondary CPUs.
[...]
> + gic: interrupt-controller@1400000 {
> + compatible = "arm,gic-400";
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + reg = <0x0 0x1401000 0 0x1000>, /* GICD */
> + <0x0 0x1402000 0 0x1000>, /* GICC */
> + <0x0 0x1404000 0 0x2000>, /* GICH */
> + <0x0 0x1406000 0 0x2000>; /* GICV */
> + interrupts = <1 9 0xf08>;
> + };
These sizes don't look right.
To the best of my knowledge, GICC (and GICV) should be 0x2000 in size, while
GICD and GICH should be 0x1000.
[...]
> + ifc: ifc@1530000 {
> + compatible = "fsl,ifc", "simple-bus";
> + reg = <0x0 0x1530000 0x0 0x10000>;
> + interrupts = <0 43 0x4>;
> + };
Why simple-bus?
> + clockgen: clocking@1ee1000 {
> + compatible = "fsl,ls1043a-clockgen";
> + reg = <0x0 0x1ee1000 0x0 0x1000>;
> + #clock-cells = <2>;
> + clocks = <&sysclk>;
> + sysclk: sysclk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <100000000>;
> + clock-output-names = "sysclk";
> + };
> + };
Why does this fixed clock live under the clockgen? It should live directly
under the root node.
[...]
> + pcie@3400000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03400000 0x0 0x00100000 /* controller registers */
> + 0x40 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 118 0x4>, /* controller interrupt */
> + <0 117 0x4>; /* PME interrupt */
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <4>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x40 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x40 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi1>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 110 0x4>,
> + <0000 0 0 2 &gic 0 111 0x4>,
> + <0000 0 0 3 &gic 0 112 0x4>,
> + <0000 0 0 4 &gic 0 113 0x4>;
> + };
> +
> + pcie@3500000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03500000 0x0 0x00100000 /* controller registers */
> + 0x48 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 128 0x4>,
> + <0 127 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x48 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x48 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi2>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 120 0x4>,
> + <0000 0 0 2 &gic 0 121 0x4>,
> + <0000 0 0 3 &gic 0 122 0x4>,
> + <0000 0 0 4 &gic 0 123 0x4>;
> + };
> +
> + pcie@3600000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03600000 0x0 0x00100000 /* controller registers */
> + 0x50 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 162 0x4>,
> + <0 161 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x50 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x50 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi3>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 154 0x4>,
> + <0000 0 0 2 &gic 0 155 0x4>,
> + <0000 0 0 3 &gic 0 156 0x4>,
> + <0000 0 0 4 &gic 0 157 0x4>;
> + };
You wait ages for a bus, then three show up at once...
> +
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0x0 0x80000000 0 0x80000000>;
> + /* DRAM space 1 - 2 GB DRAM */
I don't understand the comment. This describes 2GB at 2GB.
Does the bootloader overwrite this?
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] arm64/ls1043a: add DTS for Freescale LS1043A SoC
Date: Tue, 22 Sep 2015 02:24:03 +0100 [thread overview]
Message-ID: <20150922012403.GA1535@svinekod> (raw)
In-Reply-To: <1442838158-2964-5-git-send-email-B48286@freescale.com>
Hi,
> +/memreserve/ 0x80000000 0x00010000;
Why is this necessary?
If this is necessary, please add a comment stating what this is for.
> + cpu at 3 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a53";
> + reg = <0x0 0x3>;
> + clocks = <&clockgen 1 0>;
> + };
Missing enable-method properties on all the secondary CPUs.
[...]
> + gic: interrupt-controller at 1400000 {
> + compatible = "arm,gic-400";
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + reg = <0x0 0x1401000 0 0x1000>, /* GICD */
> + <0x0 0x1402000 0 0x1000>, /* GICC */
> + <0x0 0x1404000 0 0x2000>, /* GICH */
> + <0x0 0x1406000 0 0x2000>; /* GICV */
> + interrupts = <1 9 0xf08>;
> + };
These sizes don't look right.
To the best of my knowledge, GICC (and GICV) should be 0x2000 in size, while
GICD and GICH should be 0x1000.
[...]
> + ifc: ifc at 1530000 {
> + compatible = "fsl,ifc", "simple-bus";
> + reg = <0x0 0x1530000 0x0 0x10000>;
> + interrupts = <0 43 0x4>;
> + };
Why simple-bus?
> + clockgen: clocking at 1ee1000 {
> + compatible = "fsl,ls1043a-clockgen";
> + reg = <0x0 0x1ee1000 0x0 0x1000>;
> + #clock-cells = <2>;
> + clocks = <&sysclk>;
> + sysclk: sysclk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <100000000>;
> + clock-output-names = "sysclk";
> + };
> + };
Why does this fixed clock live under the clockgen? It should live directly
under the root node.
[...]
> + pcie at 3400000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03400000 0x0 0x00100000 /* controller registers */
> + 0x40 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 118 0x4>, /* controller interrupt */
> + <0 117 0x4>; /* PME interrupt */
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <4>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x40 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x40 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi1>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 110 0x4>,
> + <0000 0 0 2 &gic 0 111 0x4>,
> + <0000 0 0 3 &gic 0 112 0x4>,
> + <0000 0 0 4 &gic 0 113 0x4>;
> + };
> +
> + pcie at 3500000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03500000 0x0 0x00100000 /* controller registers */
> + 0x48 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 128 0x4>,
> + <0 127 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x48 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x48 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi2>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 120 0x4>,
> + <0000 0 0 2 &gic 0 121 0x4>,
> + <0000 0 0 3 &gic 0 122 0x4>,
> + <0000 0 0 4 &gic 0 123 0x4>;
> + };
> +
> + pcie at 3600000 {
> + compatible = "fsl,ls1043a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03600000 0x0 0x00100000 /* controller registers */
> + 0x50 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 162 0x4>,
> + <0 161 0x4>;
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <2>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x50 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x50 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
> + msi-parent = <&msi3>;
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 154 0x4>,
> + <0000 0 0 2 &gic 0 155 0x4>,
> + <0000 0 0 3 &gic 0 156 0x4>,
> + <0000 0 0 4 &gic 0 157 0x4>;
> + };
You wait ages for a bus, then three show up at once...
> +
> + memory at 80000000 {
> + device_type = "memory";
> + reg = <0x0 0x80000000 0 0x80000000>;
> + /* DRAM space 1 - 2 GB DRAM */
I don't understand the comment. This describes 2GB at 2GB.
Does the bootloader overwrite this?
Thanks,
Mark.
next prev parent reply other threads:[~2015-09-22 1:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 12:22 [PATCH 0/6] Add LS1043A SoC support Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` [PATCH 1/6] i2c: Add i2c support to Freescale Layerscape platforms Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` [PATCH 2/6] watchdog: Add support for " Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 15:04 ` Guenter Roeck
2015-09-21 15:04 ` Guenter Roeck
2015-09-21 15:04 ` Guenter Roeck
2015-09-21 12:22 ` [PATCH 3/6] Documentation: DT: Add entry for FSL LS1043ARDB board Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` [PATCH 4/6] arm64/ls1043a: add DTS for Freescale LS1043A SoC Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-22 1:24 ` Mark Rutland, marc.zyngier [this message]
2015-09-22 1:24 ` Mark Rutland
2015-09-22 1:24 ` Mark Rutland, marc.zyngier
2015-09-22 1:30 ` Scott Wood
2015-09-22 1:30 ` Scott Wood
2015-09-22 1:30 ` Scott Wood
2015-09-22 1:30 ` Scott Wood
2015-09-22 9:50 ` Hou Zhiqiang
2015-09-22 9:50 ` Hou Zhiqiang
2015-09-22 9:50 ` Hou Zhiqiang
2015-09-22 9:50 ` Hou Zhiqiang
2015-09-22 17:23 ` Li Leo
2015-09-22 17:23 ` Li Leo
2015-09-22 17:23 ` Li Leo
2015-09-22 17:23 ` Li Leo
2015-09-22 19:04 ` Sharma Bhupesh
2015-09-22 19:04 ` Sharma Bhupesh
2015-09-22 19:04 ` Sharma Bhupesh
2015-09-23 3:05 ` Hou Zhiqiang
2015-09-23 3:05 ` Hou Zhiqiang
2015-09-23 3:05 ` Hou Zhiqiang
2015-09-23 3:05 ` Hou Zhiqiang
2015-09-23 4:16 ` Li Leo
2015-09-23 4:16 ` Li Leo
2015-09-23 4:16 ` Li Leo
2015-09-22 22:15 ` Mark Rutland
2015-09-22 22:15 ` Mark Rutland
2015-09-22 22:15 ` Mark Rutland
2015-09-22 22:39 ` Li Leo
2015-09-22 22:39 ` Li Leo
2015-09-22 22:39 ` Li Leo
2015-09-22 22:39 ` Li Leo
2015-09-22 22:43 ` Scott Wood
2015-09-22 22:43 ` Scott Wood
2015-09-22 22:43 ` Scott Wood
2015-09-23 3:57 ` Hou Zhiqiang
2015-09-23 3:57 ` Hou Zhiqiang
2015-09-23 3:57 ` Hou Zhiqiang
2015-09-21 12:22 ` [PATCH 5/6] clk: qoriq: Add ls1043a support Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-10-01 22:56 ` Stephen Boyd
2015-10-01 22:56 ` Stephen Boyd
2015-09-21 12:22 ` [PATCH 6/6] dts/ls1043a: add LS1043ARDB board support Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 12:22 ` Zhiqiang Hou
2015-09-21 23:13 ` Scott Wood
2015-09-21 23:13 ` Scott Wood
2015-09-21 23:13 ` Scott Wood
2015-09-22 9:51 ` Hou Zhiqiang
2015-09-22 9:51 ` Hou Zhiqiang
2015-09-22 9:51 ` Hou Zhiqiang
2015-09-22 9:51 ` Hou Zhiqiang
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=20150922012403.GA1535@svinekod \
--to=mark.rutland@arm.com \
--cc=B48286@freescale.com \
--cc=Catalin.Marinas@arm.com \
--cc=Mingkai.Hu@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=Wenbin.Song@freescale.com \
--cc=Will.Deacon@arm.com \
--cc=bhupesh.sharma@freescale.com \
--cc=corbet@lwn.net \
--cc=leoli@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=scottwood@freescale.com \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.