From: manjugk@ti.com (G, Manjunath Kondaiah)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/5] OMAP4:I2C: Add device tree nodes for panda board
Date: Thu, 7 Jul 2011 22:29:14 +0530 [thread overview]
Message-ID: <20110707165914.GA3124@manju-desktop> (raw)
In-Reply-To: <20110706185712.GK4871@ponder.secretlab.ca>
On Wed, Jul 06, 2011 at 12:57:12PM -0600, Grant Likely wrote:
> On Thu, Jun 30, 2011 at 03:07:24PM +0500, G, Manjunath Kondaiah wrote:
> >
> > Add I2C and it's child device nodes for beagle board.
> > The I2C1 controller child devices are not populated and it
> > should be handled along with OMAP clock changes.
> >
> > Signed-off-by: G, Manjunath Kondaiah <manjugk@ti.com>
> > ---
> > arch/arm/boot/dts/omap4-panda.dts | 57 +++++++++++++++++++++++++++++++++++++
> > 1 files changed, 57 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> > index 58909e9..f9af72f 100644
> > --- a/arch/arm/boot/dts/omap4-panda.dts
> > +++ b/arch/arm/boot/dts/omap4-panda.dts
> > @@ -8,4 +8,61 @@
> > / {
> > model = "TI OMAP4 PandaBoard";
> > compatible = "ti,omap4-panda", "ti,omap4430";
> > + interrupt-parent = <&gic>;
> > +
> > + gic: interrupt-controller at 48241000 {
> > + compatible = "ti,omap-gic", "arm,gic";
>
> ti,omap4-gic
>
> > + interrupt-controller;
> > + #interrupt-cells = <1>;
> > + reg = <0x48241000 0x1000>,
> > + <0X48240100 0x0200>;
> > + };
> > +
> > + i2c at 48070000 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + compatible = "ti,omap_i2c";
>
> ti,omap4-i2c. Actually, it is quite possibly appropriate to do:
>
> compatible = "ti,omap4-i2c", "ti,omap3-i2c";
ok. can also have "ti,omap2-i2c"
>
> > + reg = <0x48070000 0x100>;
> > + interrupts = < 88 >;
> > + interrupt-parent = <&gic>;
> > + clock-frequency = <400>;
>
> Frequency should be a Hz value, not kHz or MHz.
current i2c-omap driver expects value to be in KHz. Will change it in driver
and pass value in Hz here.
-Manjunath
next prev parent reply other threads:[~2011-07-07 16:59 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 ` [RFC PATCH 1/5] OMAP3:I2C: Add device tree nodes for beagle board Tony Lindgren
2011-07-06 18:49 ` 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 [this message]
[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=20110707165914.GA3124@manju-desktop \
--to=manjugk@ti.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).