From: Tony Lindgren <tony@atomide.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: "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>,
Felipe Balbi <balbi@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:06:22 -0700 [thread overview]
Message-ID: <20120907170621.GZ1303@atomide.com> (raw)
In-Reply-To: <504A11E4.6000406@ti.com>
* 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 :)
> DMA is still missing, but I hope that the discussion that happened during
> LPC will fixed that soon.
Yeah and that can be added when the binding is available. The drivers should
work with and without DMA as the channels can run out.
Regards,
Tony
next prev parent reply other threads:[~2012-09-07 17:06 UTC|newest]
Thread overview: 6+ 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 17:06 ` Tony Lindgren [this message]
2012-09-07 17:25 ` Felipe Balbi
2012-09-07 17:33 ` Tony Lindgren
2012-09-07 17:23 ` Felipe Balbi
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=20120907170621.GZ1303@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 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).