From: kbeldan@baylibre.com (Karl Beldan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: dts: da850: Add an aemif node
Date: Wed, 10 Aug 2016 08:26:31 +0000 [thread overview]
Message-ID: <20160810082631.GC16481@gobelin> (raw)
In-Reply-To: <57AAE1D1.5080000@ti.com>
On Wed, Aug 10, 2016 at 01:42:01PM +0530, Sekhar Nori wrote:
> On Wednesday 10 August 2016 01:37 PM, Karl Beldan wrote:
> > On Wed, Aug 10, 2016 at 01:32:03PM +0530, Sekhar Nori wrote:
> >> On Wednesday 10 August 2016 01:18 PM, Sekhar Nori wrote:
> >>> On Tuesday 09 August 2016 10:45 PM, Karl Beldan wrote:
> >>>> Currently the davinci da8xx boards use the mach-davinci aemif code.
> >>>> Instantiating an aemif node into the DT allows to use the ti-aemif
> >>>> memory driver and is another step to better DT support.
> >>>> Also it will allow to properly pass the emif timings via DT.
> >>>>
> >>>> Signed-off-by: Karl Beldan <kbeldan@baylibre.com>
> >>>> ---
> >>>> arch/arm/boot/dts/da850.dtsi | 10 ++++++++++
> >>>> 1 file changed, 10 insertions(+)
> >>>>
> >>>> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
> >>>> index bc10e7e..f62928c 100644
> >>>> --- a/arch/arm/boot/dts/da850.dtsi
> >>>> +++ b/arch/arm/boot/dts/da850.dtsi
> >>>> @@ -411,6 +411,16 @@
> >>>> dma-names = "tx", "rx";
> >>>> };
> >>>> };
> >>>> + aemif: aemif at 68000000 {
> >>>> + compatible = "ti,da850-aemif";
> >>>> + #address-cells = <2>;
> >>>> + #size-cells = <1>;
> >>>> +
> >>>> + reg = <0x68000000 0x00008000>;
> >>>> + ranges = <0 0 0x60000000 0x08000000
> >>>> + 1 0 0x68000000 0x00008000>;
> >>>> + status = "disabled";
> >>>> + };
> >>>> nand_cs3 at 62000000 {
> >>>> compatible = "ti,davinci-nand";
> >>>> reg = <0x62000000 0x807ff
> >>>
> >>> The nand node should be part of aemif node like it is done for keystone
> >>> boards.
> >>
> >> Actually, can you move the nand node out of da850.dtsi completely. Its
> >> much better to keep da850.dtsi restricted to soc-internal devices and
> >> keep the board level devices like NAND flash in <board>.dts file.
> >>
> >> Similarly, can you move the NAND pinmux definitions too to the
> >> da850-evm.dts file?
> >>
> >> There is advantage in keeping common pinmux definitions in da850.dtsi so
> >> each board doe not have to repeat them. But AEMIF is an exception as its
> >> usage can really be varied (NAND, NOR, SRAM, other). Plus, different
> >> boards are likely to use different chip selects so coming up with some
> >> pinmux definitions which will be reused widely is really unlikely.
> >>
> > This is exactly what I just did for the LCDK.
> > If everybody is happy with it I will do the same for the evm as I put it
> > in the cover letter.
>
> Yes please. We dont want duplication of data between da850.dtsi and
> da850-lcdk.dts files.
>
Then I'll wait for this series to be applied and then apply my changes
to the EVM while retiring the nand_cs3 together.
Karl
WARNING: multiple messages have this Message-ID (diff)
From: Karl Beldan <kbeldan@baylibre.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Karl Beldan <karl.beldan+oss@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] ARM: dts: da850: Add an aemif node
Date: Wed, 10 Aug 2016 08:26:31 +0000 [thread overview]
Message-ID: <20160810082631.GC16481@gobelin> (raw)
In-Reply-To: <57AAE1D1.5080000@ti.com>
On Wed, Aug 10, 2016 at 01:42:01PM +0530, Sekhar Nori wrote:
> On Wednesday 10 August 2016 01:37 PM, Karl Beldan wrote:
> > On Wed, Aug 10, 2016 at 01:32:03PM +0530, Sekhar Nori wrote:
> >> On Wednesday 10 August 2016 01:18 PM, Sekhar Nori wrote:
> >>> On Tuesday 09 August 2016 10:45 PM, Karl Beldan wrote:
> >>>> Currently the davinci da8xx boards use the mach-davinci aemif code.
> >>>> Instantiating an aemif node into the DT allows to use the ti-aemif
> >>>> memory driver and is another step to better DT support.
> >>>> Also it will allow to properly pass the emif timings via DT.
> >>>>
> >>>> Signed-off-by: Karl Beldan <kbeldan@baylibre.com>
> >>>> ---
> >>>> arch/arm/boot/dts/da850.dtsi | 10 ++++++++++
> >>>> 1 file changed, 10 insertions(+)
> >>>>
> >>>> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
> >>>> index bc10e7e..f62928c 100644
> >>>> --- a/arch/arm/boot/dts/da850.dtsi
> >>>> +++ b/arch/arm/boot/dts/da850.dtsi
> >>>> @@ -411,6 +411,16 @@
> >>>> dma-names = "tx", "rx";
> >>>> };
> >>>> };
> >>>> + aemif: aemif@68000000 {
> >>>> + compatible = "ti,da850-aemif";
> >>>> + #address-cells = <2>;
> >>>> + #size-cells = <1>;
> >>>> +
> >>>> + reg = <0x68000000 0x00008000>;
> >>>> + ranges = <0 0 0x60000000 0x08000000
> >>>> + 1 0 0x68000000 0x00008000>;
> >>>> + status = "disabled";
> >>>> + };
> >>>> nand_cs3@62000000 {
> >>>> compatible = "ti,davinci-nand";
> >>>> reg = <0x62000000 0x807ff
> >>>
> >>> The nand node should be part of aemif node like it is done for keystone
> >>> boards.
> >>
> >> Actually, can you move the nand node out of da850.dtsi completely. Its
> >> much better to keep da850.dtsi restricted to soc-internal devices and
> >> keep the board level devices like NAND flash in <board>.dts file.
> >>
> >> Similarly, can you move the NAND pinmux definitions too to the
> >> da850-evm.dts file?
> >>
> >> There is advantage in keeping common pinmux definitions in da850.dtsi so
> >> each board doe not have to repeat them. But AEMIF is an exception as its
> >> usage can really be varied (NAND, NOR, SRAM, other). Plus, different
> >> boards are likely to use different chip selects so coming up with some
> >> pinmux definitions which will be reused widely is really unlikely.
> >>
> > This is exactly what I just did for the LCDK.
> > If everybody is happy with it I will do the same for the evm as I put it
> > in the cover letter.
>
> Yes please. We dont want duplication of data between da850.dtsi and
> da850-lcdk.dts files.
>
Then I'll wait for this series to be applied and then apply my changes
to the EVM while retiring the nand_cs3 together.
Karl
WARNING: multiple messages have this Message-ID (diff)
From: Karl Beldan <kbeldan@baylibre.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Karl Beldan <karl.beldan+oss@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [PATCH 2/4] ARM: dts: da850: Add an aemif node
Date: Wed, 10 Aug 2016 08:26:31 +0000 [thread overview]
Message-ID: <20160810082631.GC16481@gobelin> (raw)
In-Reply-To: <57AAE1D1.5080000@ti.com>
On Wed, Aug 10, 2016 at 01:42:01PM +0530, Sekhar Nori wrote:
> On Wednesday 10 August 2016 01:37 PM, Karl Beldan wrote:
> > On Wed, Aug 10, 2016 at 01:32:03PM +0530, Sekhar Nori wrote:
> >> On Wednesday 10 August 2016 01:18 PM, Sekhar Nori wrote:
> >>> On Tuesday 09 August 2016 10:45 PM, Karl Beldan wrote:
> >>>> Currently the davinci da8xx boards use the mach-davinci aemif code.
> >>>> Instantiating an aemif node into the DT allows to use the ti-aemif
> >>>> memory driver and is another step to better DT support.
> >>>> Also it will allow to properly pass the emif timings via DT.
> >>>>
> >>>> Signed-off-by: Karl Beldan <kbeldan@baylibre.com>
> >>>> ---
> >>>> arch/arm/boot/dts/da850.dtsi | 10 ++++++++++
> >>>> 1 file changed, 10 insertions(+)
> >>>>
> >>>> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
> >>>> index bc10e7e..f62928c 100644
> >>>> --- a/arch/arm/boot/dts/da850.dtsi
> >>>> +++ b/arch/arm/boot/dts/da850.dtsi
> >>>> @@ -411,6 +411,16 @@
> >>>> dma-names = "tx", "rx";
> >>>> };
> >>>> };
> >>>> + aemif: aemif@68000000 {
> >>>> + compatible = "ti,da850-aemif";
> >>>> + #address-cells = <2>;
> >>>> + #size-cells = <1>;
> >>>> +
> >>>> + reg = <0x68000000 0x00008000>;
> >>>> + ranges = <0 0 0x60000000 0x08000000
> >>>> + 1 0 0x68000000 0x00008000>;
> >>>> + status = "disabled";
> >>>> + };
> >>>> nand_cs3@62000000 {
> >>>> compatible = "ti,davinci-nand";
> >>>> reg = <0x62000000 0x807ff
> >>>
> >>> The nand node should be part of aemif node like it is done for keystone
> >>> boards.
> >>
> >> Actually, can you move the nand node out of da850.dtsi completely. Its
> >> much better to keep da850.dtsi restricted to soc-internal devices and
> >> keep the board level devices like NAND flash in <board>.dts file.
> >>
> >> Similarly, can you move the NAND pinmux definitions too to the
> >> da850-evm.dts file?
> >>
> >> There is advantage in keeping common pinmux definitions in da850.dtsi so
> >> each board doe not have to repeat them. But AEMIF is an exception as its
> >> usage can really be varied (NAND, NOR, SRAM, other). Plus, different
> >> boards are likely to use different chip selects so coming up with some
> >> pinmux definitions which will be reused widely is really unlikely.
> >>
> > This is exactly what I just did for the LCDK.
> > If everybody is happy with it I will do the same for the evm as I put it
> > in the cover letter.
>
> Yes please. We dont want duplication of data between da850.dtsi and
> da850-lcdk.dts files.
>
Then I'll wait for this series to be applied and then apply my changes
to the EVM while retiring the nand_cs3 together.
Karl
next prev parent reply other threads:[~2016-08-10 8:26 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 17:15 [PATCH 0/4] Add DT support for NAND to LCDK Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-09 17:15 ` [PATCH 1/4] memory: ti-aemif: Get a named clock rather than an unnamed one Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-10 7:00 ` Karl Beldan
2016-08-10 7:00 ` Karl Beldan
2016-08-10 7:00 ` Karl Beldan
2016-08-10 7:27 ` Karl Beldan
2016-08-10 7:27 ` Karl Beldan
2016-08-10 7:27 ` Karl Beldan
2016-08-09 17:15 ` [PATCH 2/4] ARM: dts: da850: Add an aemif node Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-10 7:48 ` Sekhar Nori
2016-08-10 7:48 ` Sekhar Nori
2016-08-10 7:48 ` Sekhar Nori
2016-08-10 8:01 ` Karl Beldan
2016-08-10 8:01 ` Karl Beldan
2016-08-10 8:01 ` Karl Beldan
2016-08-10 8:02 ` Sekhar Nori
2016-08-10 8:02 ` Sekhar Nori
2016-08-10 8:02 ` Sekhar Nori
2016-08-10 8:07 ` Karl Beldan
2016-08-10 8:07 ` Karl Beldan
2016-08-10 8:07 ` Karl Beldan
2016-08-10 8:12 ` Sekhar Nori
2016-08-10 8:12 ` Sekhar Nori
2016-08-10 8:12 ` Sekhar Nori
2016-08-10 8:26 ` Karl Beldan [this message]
2016-08-10 8:26 ` Karl Beldan
2016-08-10 8:26 ` Karl Beldan
2016-08-10 8:29 ` Sekhar Nori
2016-08-10 8:29 ` Sekhar Nori
2016-08-10 8:29 ` Sekhar Nori
2016-08-10 8:34 ` Karl Beldan
2016-08-10 8:34 ` Karl Beldan
2016-08-10 8:34 ` Karl Beldan
2016-08-10 8:34 ` Sekhar Nori
2016-08-10 8:34 ` Sekhar Nori
2016-08-10 8:34 ` Sekhar Nori
2016-08-10 9:28 ` Karl Beldan
2016-08-10 9:28 ` Karl Beldan
2016-08-10 9:28 ` Karl Beldan
2016-08-10 9:38 ` Sekhar Nori
2016-08-10 9:38 ` Sekhar Nori
2016-08-10 9:42 ` Karl Beldan
2016-08-10 9:42 ` Karl Beldan
2016-08-10 9:42 ` Karl Beldan
2016-08-13 11:42 ` Karl Beldan
2016-08-13 11:42 ` Karl Beldan
2016-08-09 17:15 ` [PATCH 3/4] ARM: dts: da850-lcdk: Add NAND to DT Karl Beldan
2016-08-09 17:15 ` Karl Beldan
2016-08-10 8:31 ` Sekhar Nori
2016-08-10 8:31 ` Sekhar Nori
2016-08-10 9:04 ` Karl Beldan
2016-08-10 9:04 ` Karl Beldan
2016-08-10 9:04 ` Karl Beldan
2016-08-10 9:31 ` Sekhar Nori
2016-08-10 9:31 ` Sekhar Nori
2016-08-10 9:31 ` Sekhar Nori
2016-08-10 11:19 ` Karl Beldan
2016-08-10 11:19 ` Karl Beldan
2016-08-10 11:19 ` Karl Beldan
2016-08-10 11:53 ` Sekhar Nori
2016-08-10 11:53 ` Sekhar Nori
2016-08-10 11:53 ` Sekhar Nori
2016-08-16 23:20 ` Karl Beldan
2016-08-16 23:20 ` Karl Beldan
2016-08-29 7:49 ` Karl Beldan
2016-08-29 7:49 ` Karl Beldan
2016-08-29 7:49 ` Karl Beldan
2016-08-10 9:29 ` Karl Beldan
2016-08-10 9:29 ` Karl Beldan
2016-08-10 9:29 ` Karl Beldan
2016-08-09 17:15 ` [PATCH 4/4] ARM: davinci_all_defconfig: Enable AEMIF as a module Karl Beldan
2016-08-09 17:15 ` Karl Beldan
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=20160810082631.GC16481@gobelin \
--to=kbeldan@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.