From: lokeshvutla@ti•com (Lokesh Vutla)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] ARM: dts: Renaming elpida_ecb240abacn.dtsi as lpddr2_data.dtsi
Date: Thu, 11 Oct 2012 11:46:45 +0530 [thread overview]
Message-ID: <5076644D.5050703@ti.com> (raw)
In-Reply-To: <50758AA0.5080307@ti.com>
+ devicetree-discuss
Hi Benoit,
On Wednesday 10 October 2012 08:18 PM, Benoit Cousson wrote:
> Hi Lokesh,
>
> On 10/10/2012 02:05 PM, Lokesh Vutla wrote:
>> Renaming elpida_ecb240abacn.dtsi file generic, so that the
>> same file can be reused for other parts from different vendors.
>
> Could you elaborate a little bit?
> Are these settings purely reflecting lpddr2 spec timings?
The basic idea is to group data for all the lpddr2 devices in a single
file instead of creating separate file for each lpddr2 device.
Right now the file elpida_ecb240abacn.dtsi contains only data for
lpddr2-s4 2G parts from Elpida.
I wanted to add data for lpddr2-s4 4G parts from Samsung.
So I renamed the file elpida_ecb240abacn.dtsi as lpddr2_data.dtsi.
Please let me know if more clarification is needed.
Thanks,
Lokesh
>
> Regards,
> Benoit
>
>
>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti•com>
>> ---
>> arch/arm/boot/dts/{elpida_ecb240abacn.dtsi => lpddr2_data.dtsi} | 0
>> arch/arm/boot/dts/omap4-panda.dts | 2 +-
>> arch/arm/boot/dts/omap4-sdp.dts | 2 +-
>> 3 files changed, 2 insertions(+), 2 deletions(-)
>> rename arch/arm/boot/dts/{elpida_ecb240abacn.dtsi => lpddr2_data.dtsi} (100%)
>>
>> diff --git a/arch/arm/boot/dts/elpida_ecb240abacn.dtsi b/arch/arm/boot/dts/lpddr2_data.dtsi
>> similarity index 100%
>> rename from arch/arm/boot/dts/elpida_ecb240abacn.dtsi
>> rename to arch/arm/boot/dts/lpddr2_data.dtsi
>> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
>> index 20b966e..09d3a32 100644
>> --- a/arch/arm/boot/dts/omap4-panda.dts
>> +++ b/arch/arm/boot/dts/omap4-panda.dts
>> @@ -8,7 +8,7 @@
>> /dts-v1/;
>>
>> /include/ "omap4.dtsi"
>> -/include/ "elpida_ecb240abacn.dtsi"
>> +/include/ "lpddr2_data.dtsi"
>>
>> / {
>> model = "TI OMAP4 PandaBoard";
>> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
>> index 94a23b3..dd749fc 100644
>> --- a/arch/arm/boot/dts/omap4-sdp.dts
>> +++ b/arch/arm/boot/dts/omap4-sdp.dts
>> @@ -8,7 +8,7 @@
>> /dts-v1/;
>>
>> /include/ "omap4.dtsi"
>> -/include/ "elpida_ecb240abacn.dtsi"
>> +/include/ "lpddr2_data.dtsi"
>>
>> / {
>> model = "TI OMAP4 SDP board";
>>
>
next prev parent reply other threads:[~2012-10-11 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 12:05 [PATCH 0/3] ARM: dts: EMIF and LPDDR2 device tree data for OMAP5 boards Lokesh Vutla
2012-10-10 12:05 ` [PATCH 1/3] ARM: dts: Renaming elpida_ecb240abacn.dtsi as lpddr2_data.dtsi Lokesh Vutla
2012-10-10 14:48 ` Benoit Cousson
2012-10-11 6:16 ` Lokesh Vutla [this message]
2012-10-11 8:28 ` Benoit Cousson
2012-10-11 8:31 ` Lokesh Vutla
2012-10-10 12:05 ` [PATCH 2/3] ARM: dts: Correcting size of memory defined for omap5 Lokesh Vutla
2012-10-10 15:15 ` Benoit Cousson
2012-10-10 12:05 ` [PATCH 3/3] ARM: dts: EMIF and LPDDR2 device tree data for OMAP5 boards Lokesh Vutla
2012-10-10 15:01 ` Benoit Cousson
2012-10-11 6:16 ` Lokesh Vutla
2012-10-11 8:11 ` Benoit Cousson
2012-10-11 8:15 ` Santosh Shilimkar
2012-10-10 15:50 ` [PATCH 0/3] " Benoit Cousson
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=5076644D.5050703@ti.com \
--to=lokeshvutla@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox