linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm/dts: AM33XX: Add reg and interrupt property for all nodes
Date: Thu, 6 Sep 2012 15:57:51 +0200	[thread overview]
Message-ID: <5048ABDF.6020609@ti.com> (raw)
In-Reply-To: <1346070714-6122-1-git-send-email-hvaibhav@ti.com>

Hi Vaihbav,

On 08/27/2012 02:31 PM, Vaibhav Hiremath wrote:
> This series is trivial patch-series and should be considered as
> preparation for the future where we supposed to get rid of
> hwmod dependency.
> 
> 1/2: Converts all hex numbers to lowercase, fixing inconsistency
> 2/2: Add reg and interrupt property  to all device/module nodes inside
>      DTS files. 
> 
> Although currently hwmod overwrites resources, I have validated this
> patch series by changing the omap_device layer to respect DT resources
> and boot Tested on BeagleBone platform.
> I will be submitting the changes for omap_device layer as well, still
> needs to fix on certain things.
> 
> Vaibhav Hiremath (2):
>   arm/dts: AM33XX: Convert all hex numbers to lower-case
>   arm/dts: AM33XX: Specify reg and interrupt property for all nodes
> 
>  arch/arm/boot/dts/am335x-bone.dts |    2 +-
>  arch/arm/boot/dts/am335x-evm.dts  |    2 +-
>  arch/arm/boot/dts/am33xx.dtsi     |   62 +++++++++++++++++++++++++++++++------
>  3 files changed, 54 insertions(+), 12 deletions(-)

I'll queue that along with the other DT stuff for 3.7.

Thanks,
Benoit

      parent reply	other threads:[~2012-09-06 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 12:31 [PATCH 0/2] arm/dts: AM33XX: Add reg and interrupt property for all nodes Vaibhav Hiremath
2012-08-27 12:31 ` [PATCH 1/2] arm/dts: AM33XX: Convert all hex numbers to lower-case Vaibhav Hiremath
2012-08-27 12:31 ` [PATCH 2/2] arm/dts: AM33XX: Specify reg and interrupt property for all nodes Vaibhav Hiremath
2012-09-06 13:57 ` Benoit Cousson [this message]

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=5048ABDF.6020609@ti.com \
    --to=b-cousson@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).