From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
santosh Shilimkar <santosh.shilimkar@ti.com>,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [PATCH] ARM: dts: OMAP4: Add reg and interrupts for every nodes
Date: Fri, 7 Sep 2012 10:33:37 -0700 [thread overview]
Message-ID: <20120907173337.GC1303@atomide.com> (raw)
In-Reply-To: <20120907172500.GB9208@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [120907 10:30]:
> Hi,
>
> On Fri, Sep 07, 2012 at 10:06:22AM -0700, Tony Lindgren wrote:
> > * Benoit Cousson <b-cousson@ti.com> [120907 08:26]:
> > > Thanks to Vaibhav <hvaibhav@ti.com> omap_device fix
> > > (ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
> > > we can now specify reg and interrupts using standard device tree
> > > attributes.
> > >
> > > Update the OMAP4 dtsi file with missing reg and interrupts attributes.
> > >
> > > Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> > > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > > Cc: Tony Lindgren <tony@atomide.com>
> > > Cc: Felipe Balbi <balbi@ti.com>
> > > ---
> > >
> > > Hi Tony,
> > >
> > > This is the first step toward reduction of the hwmod data inside mach-omap2.
> > > OMAP2/3/4 data still need to be there for legacy boards, but it will allow
> > > OMAP5/AM33XX pure DT board to reduce the amount of data provided by hwmod.
> >
> > That's good to hear, that should cut down the data by some hundreds of lines :)
>
> more than you think, I guess :-)
Very cool, we're only two board files away from making omap4 data shrink by:
omap_hwmod_44xx_data.c | 1432 -------------------------------------------------
But basically no need to merge similar data at all for am33xx and omap5.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: OMAP4: Add reg and interrupts for every nodes
Date: Fri, 7 Sep 2012 10:33:37 -0700 [thread overview]
Message-ID: <20120907173337.GC1303@atomide.com> (raw)
In-Reply-To: <20120907172500.GB9208@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [120907 10:30]:
> Hi,
>
> On Fri, Sep 07, 2012 at 10:06:22AM -0700, Tony Lindgren wrote:
> > * Benoit Cousson <b-cousson@ti.com> [120907 08:26]:
> > > Thanks to Vaibhav <hvaibhav@ti.com> omap_device fix
> > > (ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
> > > we can now specify reg and interrupts using standard device tree
> > > attributes.
> > >
> > > Update the OMAP4 dtsi file with missing reg and interrupts attributes.
> > >
> > > Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> > > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > > Cc: Tony Lindgren <tony@atomide.com>
> > > Cc: Felipe Balbi <balbi@ti.com>
> > > ---
> > >
> > > Hi Tony,
> > >
> > > This is the first step toward reduction of the hwmod data inside mach-omap2.
> > > OMAP2/3/4 data still need to be there for legacy boards, but it will allow
> > > OMAP5/AM33XX pure DT board to reduce the amount of data provided by hwmod.
> >
> > That's good to hear, that should cut down the data by some hundreds of lines :)
>
> more than you think, I guess :-)
Very cool, we're only two board files away from making omap4 data shrink by:
omap_hwmod_44xx_data.c | 1432 -------------------------------------------------
But basically no need to merge similar data at all for am33xx and omap5.
Regards,
Tony
next prev parent reply other threads:[~2012-09-07 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 15:25 [PATCH] ARM: dts: OMAP4: Add reg and interrupts for every nodes Benoit Cousson
2012-09-07 15:25 ` Benoit Cousson
2012-09-07 17:06 ` Tony Lindgren
2012-09-07 17:06 ` Tony Lindgren
2012-09-07 17:25 ` Felipe Balbi
2012-09-07 17:25 ` Felipe Balbi
2012-09-07 17:33 ` Tony Lindgren [this message]
2012-09-07 17:33 ` Tony Lindgren
2012-09-07 17:23 ` Felipe Balbi
2012-09-07 17:23 ` Felipe Balbi
2012-09-07 17:42 ` Benoit Cousson
2012-09-07 17:42 ` 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=20120907173337.GC1303@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.