From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 1/2] ARM: dts: AM33XX: Add support for IGEP COM AQUILA
Date: Wed, 19 Jun 2013 15:32:18 +0200 [thread overview]
Message-ID: <CAAwP0s3BaCte1qWM0mgK+VyXmOPy5WLmgYJfAhRtmANcwwfn_A@mail.gmail.com> (raw)
In-Reply-To: <51C18BEE.4020405@ti.com>
Hi,
On Wed, Jun 19, 2013 at 12:46 PM, Benoit Cousson <b-cousson@ti.com> wrote:
> Hi Enric,
>
>
> On 06/19/2013 03:27 AM, Enric Balletbo i Serra wrote:
>>
>> The IGEP COM AQUILA is industrial processors SODIMM module with
>> following highlights:
>>
>> o AM3352/AM3354/AM3358/AM3359 Texas Instruments processor
>> o Cortex-A8 ARM CPU
>> o 3.3 volts Inputs / Outputs use industrial
>> o 256 MB DDR3 SDRAM / 128 Megabytes FLASH
>> o MicroSD card reader on-board
>> o Ethernet controller on-board
>> o JTAG debug connector available
>> o Designed for industrial range purposes
>>
>> Signed-off-by: Enric Balletbo i Serra <eballetbo@iseebcn.com>
>> ---
>> arch/arm/boot/dts/am335x-igep0033.dtsi | 269
>> +++++++++++++++++++++++++++++++++
>> 1 file changed, 269 insertions(+)
>> create mode 100644 arch/arm/boot/dts/am335x-igep0033.dtsi
>>
>> diff --git a/arch/arm/boot/dts/am335x-igep0033.dtsi
>> b/arch/arm/boot/dts/am335x-igep0033.dtsi
>> new file mode 100644
>> index 0000000..1d70141
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/am335x-igep0033.dtsi
>> @@ -0,0 +1,269 @@
>> +/*
>> + * Copyright (C) 2013 ISEE 2007 SL - http://www.isee.biz/
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +
>> +/dts-v1/;
>> +
>> +#include "am33xx.dtsi"
>> +
>> +/ {
>> + cpus {
>> + cpu@0 {
>> + cpu0-supply = <&vdd1_reg>;
>> + };
>> + };
>> +
>> + memory {
>> + device_type = "memory";
>> + reg = <0x80000000 0x10000000>; /* 256 MB */
>> + };
>> +
>> + am33xx_pinmux: pinmux@44e10800 {
>
>
> That node should be inside the ocp one since the control module is a regular
> IP connected to the OCP interconnect.
>
>
>
In fact, I don't think that there should be a definition of the On
Chip Peripherals interconnect or any child node of the ocp in a DTS
file.
These should be defined in the included dtsi file since it will be
common to all boards based on this SoC.
DTS files that describe a board can reference these nodes defined in
the dtsi and add their custom peripherals as childs of them.
So, instead defining in the DTS:
am33xx_pinmux: pinmux@44e10800 {
...
};
gpmc: gpmc@50000000 {
...
};
i2c0: i2c@44e0b000 {
...
};
uart0: serial@44e09000 {
..
};
It has to be defined as:
&am33xx_pinmux {
...
};
&gpmc {
...
};
&i2c0 {
...
}
I'm looking at other am33xx dts such as am335x-bone.dts and
am335x-evm.dts and I see that these define device nodes already
defined in the included .dtsi which is wrong in my opinion.
The OMAP{3,4,5} dtsi and dts do correctly and can be used as a
reference on how the device nodes have to be defined and referenced.
Best regards,
Javier
next prev parent reply other threads:[~2013-06-19 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 8:27 [PATCH 0/2] ARM: dts: Add initial support for IGEP AQUILA Enric Balletbo i Serra
2013-06-19 8:27 ` [PATCH 1/2] ARM: dts: AM33XX: Add support for IGEP COM AQUILA Enric Balletbo i Serra
2013-06-19 10:46 ` Benoit Cousson
2013-06-19 13:32 ` Javier Martinez Canillas [this message]
2013-06-20 14:16 ` Cousson, Benoit
2013-06-19 8:27 ` [PATCH 2/2] ARM: dts: AM33XX: Add support for IGEP AQUILA EXPANSION board Enric Balletbo i Serra
-- strict thread matches above, loose matches on Subject: below --
2013-09-10 14:55 [PATCHv3 0/2] ARM: dts: Add initial support for IGEP AQUILA Enric Balletbo i Serra
2013-09-10 14:55 ` [PATCH 1/2] ARM: dts: AM33XX: Add support for IGEP COM AQUILA Enric Balletbo i Serra
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=CAAwP0s3BaCte1qWM0mgK+VyXmOPy5WLmgYJfAhRtmANcwwfn_A@mail.gmail.com \
--to=martinez.javier@gmail.com \
--cc=b-cousson@ti.com \
--cc=eballetbo@iseebcn.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).