linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/5] OMAP3:I2C: Add device tree nodes for beagle board
Date: Thu, 30 Jun 2011 07:27:02 -0700	[thread overview]
Message-ID: <20110630142702.GV23145@atomide.com> (raw)
In-Reply-To: <1309426647-31587-2-git-send-email-manjugk@ti.com>

Hi,

Few comments on the .dts data layout below.

* G, Manjunath Kondaiah <manjugk@ti.com> [110630 02:44]:
> --- a/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
> @@ -2,11 +2,6 @@
>  
>  / {
>  	i2c at 48072000 {
> -		compatible = "ti,omap3-i2c";
> -		reg = <0x48072000 0x80>;
> -		#address-cells = <1>;
> -		#size-cells = <0>;
> -
>  		eeprom at 50 {
>  			compatible = "at,at24c01";
>  			reg = < 0x50 >;

The board .dts file should include the omap3 SoC .dts file.

The omap3 SoC .dts file should have the devices mapped to L3 and L4
busses, and the then i2c at 1 would just contain the bus offset.

Then the i2c at 1 entry would be repeated in the board specific
.dts and tell that the i2c at 1 is enabled.

> --- a/arch/arm/boot/dts/omap3-beagle.dts
> +++ b/arch/arm/boot/dts/omap3-beagle.dts
> @@ -4,4 +4,46 @@
>  / {
>  	model = "TI OMAP3 BeagleBoard";
>  	compatible = "ti,omap3-beagle";
> +	interrupt-parent = <&gic>;
> +
> +	gic: interrupt-controller at 48241000 {
> +		compatible = "ti,omap-gic", "arm,gic";
> +		interrupt-controller;
> +		#interrupt-cells = <1>;
> +		reg = <0x48200000 0x1000>;
> +	};

There's no GIC on omap3, that's only on Cortex A9 systems.

Regards,

Tony

       reply	other threads:[~2011-06-30 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1309426647-31587-1-git-send-email-manjugk@ti.com>
     [not found] ` <1309426647-31587-2-git-send-email-manjugk@ti.com>
2011-06-30 14:27   ` Tony Lindgren [this message]
2011-07-06 18:49     ` [RFC PATCH 1/5] OMAP3:I2C: Add device tree nodes for beagle board Grant Likely
2011-07-06 18:55   ` Grant Likely
2011-07-06 23:26     ` Stephen Warren
2011-07-07  0:12       ` Grant Likely
2011-07-20 11:04         ` Shawn Guo
2011-07-20 18:55           ` Grant Likely
2011-07-20 22:33             ` Shawn Guo
2011-07-20 23:14               ` Grant Likely
     [not found] ` <1309426647-31587-3-git-send-email-manjugk@ti.com>
2011-07-06 18:57   ` [RFC PATCH 2/5] OMAP4:I2C: Add device tree nodes for panda board Grant Likely
2011-07-07 16:59     ` G, Manjunath Kondaiah
     [not found] ` <1309426647-31587-4-git-send-email-manjugk@ti.com>
2011-07-06 19:00   ` [RFC PATCH 3/5] OMAP3: Beagle: Update beagle board file to use DT Grant Likely
2011-07-07 17:04     ` G, Manjunath Kondaiah
     [not found] ` <1309426647-31587-5-git-send-email-manjugk@ti.com>
2011-07-06 19:01   ` [RFC PATCH 4/5] OMAP4: Panda: Update panda " Grant Likely
     [not found] ` <1309426647-31587-6-git-send-email-manjugk@ti.com>
2011-07-06 19:08   ` [RFC PATCH 5/5] OMAP: I2C: Convert I2C driver to use device tree Grant Likely
2011-07-07 17:13     ` G, Manjunath Kondaiah
2011-07-07 18:28       ` Grant Likely

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=20110630142702.GV23145@atomide.com \
    --to=tony@atomide.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 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).