[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de22c568-22b8-7809-5506-cac23fad252d@ti.com>
Date: Tue, 15 Nov 2016 15:35:52 +0530
From: Sekhar Nori <nsekhar@...com>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>,
Kevin Hilman <khilman@...libre.com>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Mark Rutland <mark.rutland@....com>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Russell King <linux@...linux.org.uk>
CC: LKML <linux-kernel@...r.kernel.org>,
arm-soc <linux-arm-kernel@...ts.infradead.org>,
linux-drm <dri-devel@...ts.freedesktop.org>,
linux-devicetree <devicetree@...r.kernel.org>,
Jyri Sarha <jsarha@...com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
David Airlie <airlied@...ux.ie>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 1/2] ARM: dts: da850: add the mstpri and ddrctl nodes
On Monday 14 November 2016 11:02 PM, Bartosz Golaszewski wrote:
> Add the nodes for the MSTPRI configuration and DDR2/mDDR memory
> controller drivers to da850.dtsi.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
> ---
> arch/arm/boot/dts/da850.dtsi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
> index 1bb1f6d..1635218 100644
> --- a/arch/arm/boot/dts/da850.dtsi
> +++ b/arch/arm/boot/dts/da850.dtsi
> @@ -440,6 +440,11 @@
> interrupts = <52>;
> status = "disabled";
> };
> +
> + mstpri: mstpri@...10 {
> + compatible = "ti,da850-mstpri";
> + reg = <0x14110 0x0c>;
> + };
Instead of adding the node to the end, can you place it above the
cfgchip node to keep it sorted by reg. We have not really followed that
in this file. May be we should have. But lets start with this.
> };
> aemif: aemif@...00000 {
> compatible = "ti,da850-aemif";
> @@ -451,4 +456,8 @@
> 1 0 0x68000000 0x00008000>;
> status = "disabled";
> };
> + ddrctl: ddrctl@...00000 {
> + compatible = "ti,da850-ddr-controller";
> + reg = <0xb0000000 0xe8>;
> + };
Can you name the node memory-controller@...00000? Thats the generic name
suggested by ePAPR 1.1 for memory controllers.
I could not find any naming suggestions for the bus master priority
controller above, but based on the pattern used for other controllers,
may be it should be called priority-controller@...10 instead of mstpri@...10
Thanks,
Sekhar
Powered by blists - more mailing lists