Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Anil Kumar <anilk4.v@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <b-cousson@ti.com>,
	device-tree <devicetree-discuss@lists.ozlabs.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/9] ARM: dts: OMAP3: Add support for OMAP3430 SDP board
Date: Mon, 11 Mar 2013 12:53:32 -0500	[thread overview]
Message-ID: <513E1A1C.8070206@ti.com> (raw)
In-Reply-To: <CABYxbz7Bg3Uf2wkhH=4d6nEPUjyHF8BiixN6rGCOgEVG_us8Jw@mail.gmail.com>


On 03/08/2013 08:25 PM, Anil Kumar wrote:
> Hi Jon,
> 
> On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter <jon-hunter@ti.com> wrote:
>> Adds basic device-tree support for OMAP3430 SDP board which has 256MB
>> of RAM and uses the TWL4030 power management IC.
> 
> I think this board support should be in separate patch series with
> related patches.

Well I wanted to keep them altogether so that I can send a pull request
to Benoit and Tony.

>>
>> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
>> ---
>>  arch/arm/boot/dts/Makefile         |    1 +
>>  arch/arm/boot/dts/omap3430-sdp.dts |   46 ++++++++++++++++++++++++++++++++++++
>>  2 files changed, 47 insertions(+)
>>  create mode 100644 arch/arm/boot/dts/omap3430-sdp.dts
>>
>> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
>> index 9c62558..89013ed 100644
>> --- a/arch/arm/boot/dts/Makefile
>> +++ b/arch/arm/boot/dts/Makefile
>> @@ -119,6 +119,7 @@ dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \
>>         omap3-beagle-xm.dtb \
>>         omap3-evm.dtb \
>>         omap3-tobi.dtb \
>> +       omap3430-sdp.dtb \
>>         omap4-panda.dtb \
>>         omap4-panda-a4.dtb \
>>         omap4-panda-es.dtb \
>> diff --git a/arch/arm/boot/dts/omap3430-sdp.dts b/arch/arm/boot/dts/omap3430-sdp.dts
>> new file mode 100644
>> index 0000000..be0650d
>> --- /dev/null
>> +++ b/arch/arm/boot/dts/omap3430-sdp.dts
>> @@ -0,0 +1,46 @@
>> +/*
>> + * Copyright (C) 2013 Texas Instruments Incorporated - http://www.ti.com/
>> + *
>> + * 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/ "omap3.dtsi"
>> +
>> +/ {
>> +       model = "TI OMAP3430 SDP";
>> +       compatible = "ti,omap3430-sdp", "ti,omap3";
> 
> I have not seen any related changes in "board-generic.c" for your board.
> So just wanted know, how this board is booting ?

If you look at board-generic.c you will see that "ti,omap3" will match
the OMAP3 generic machine. So you don't need to modify the board-generic.c.

>> +
>> +       memory {
>> +               device_type = "memory";
>> +               reg = <0x80000000 0x10000000>; /* 256 MB */
>> +       };
>> +};
>> +
>> +&i2c1 {
>> +       clock-frequency = <2600000>;
>> +
>> +       twl: twl@48 {
>> +               reg = <0x48>;
>> +               interrupts = <7>; /* SYS_NIRQ cascaded to intc */
>> +               interrupt-parent = <&intc>;
>> +       };
>> +};
>> +
>> +/include/ "twl4030.dtsi"
>> +
>> +&mmc1 {
>> +       vmmc-supply = <&vmmc1>;
>> +       vmmc_aux-supply = <&vsim>;
>> +       bus-width = <8>;
>> +};
>> +
>> +&mmc2 {
>> +       status = "disabled";
>> +};
>> +
>> +&mmc3 {
>> +       status = "disabled";
>> +};
> 
> I think you should disable modules those are not currently used
> as they are enabled by default in omap3.dtsi.
> 
> exp:-
> 
> &mcbsp2 {
>         status = "disabled";
> };

Well may be we could do that in a follow-up patch. If you look at other
omap3 boards we have not gone through and disabled all unused modules
either. So although I agree, right now I just want to get minimal
support added.

Jon

  reply	other threads:[~2013-03-11 17:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 17:27 [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Jon Hunter
2013-03-08 17:27 ` [PATCH 1/9] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-03-08 17:27 ` [PATCH 2/9] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 3/9] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 4/9] ARM: dts: OMAP3: Add support for OMAP3430 SDP board Jon Hunter
2013-03-09  2:25   ` Anil Kumar
2013-03-11 17:53     ` Jon Hunter [this message]
2013-03-12  2:42       ` Kumar, Anil
2013-03-12  8:50         ` Javier Martinez Canillas
2013-03-13  2:50           ` Kumar, Anil
2013-03-12 21:27         ` Jon Hunter
2013-03-13  2:59           ` Kumar, Anil
2013-03-11  2:45   ` Anil Kumar
2013-03-11 17:54     ` Jon Hunter
2013-03-08 17:27 ` [PATCH 5/9] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5 Jon Hunter
2013-03-08 20:25   ` Javier Martinez Canillas
2013-03-08 21:41     ` Jon Hunter
2013-03-09  1:25       ` Javier Martinez Canillas
2013-03-09 12:42         ` Ezequiel Garcia
2013-03-11 17:56           ` Jon Hunter
2013-03-14 15:45             ` Benoit Cousson
2013-03-14 15:50               ` Jon Hunter
2013-03-14 15:57                 ` Ezequiel Garcia
2013-03-14 15:58                 ` Benoit Cousson
2013-03-14 16:00                   ` Jon Hunter
2013-03-14 16:03                     ` Benoit Cousson
2013-03-08 17:27 ` [PATCH 6/9] ARM: dts: Add OMAP3430 SDP flash memory bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 7/9] ARM: dts: Add OMAP2 gpio bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 8/9] ARM: dts: OMAP3+: Correct gpio #interrupts-cells property Jon Hunter
2013-03-08 17:27 ` [PATCH 9/9] ARM: dts: OMAP3: Add reg and interrupt properties for gpio Jon Hunter
2013-03-14 14:57 ` [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Benoit Cousson
2013-03-14 15:45   ` Florian Vaussard
2013-03-14 15:59     ` Jon Hunter
2013-03-14 16:06       ` Benoit Cousson
2013-03-14 16:02   ` Javier Martinez Canillas
2013-03-14 16:04     ` Jon Hunter
2013-03-14 16:08     ` 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=513E1A1C.8070206@ti.com \
    --to=jon-hunter@ti.com \
    --cc=anilk4.v@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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