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/8] ARM: dts: OMAP5: ocp address space and few updates
Date: Fri, 15 Mar 2013 13:45:32 +0100	[thread overview]
Message-ID: <514317EC.6040400@ti.com> (raw)
In-Reply-To: <5142F6EF.7010900@ti.com>

Hi Santosh,

On 03/15/2013 11:24 AM, Santosh Shilimkar wrote:
> Benoit,
> 
> On Wednesday 20 February 2013 09:08 PM, Santosh Shilimkar wrote:
>> Few updates for OMAP5 found during testing OMAP5 DT builds. Couple
>> of patches were already posted on the list. The series also contains
>> a patch which adds DMA request, IRQ lines and IO address space 
>> DT extraction support to hwmod code so that we can get rid of
>> such information from hwmod data files. It has been tested on OMAP5
>> and OMAP4 devices.
>>
> [..]
> 
>>   ARM: OMAP: hwmod: extract module address space from DT blob
> Above patch even though dt extraction code touches the hwmod file.
> Are you ok to keep this patch is the current series considering
> both the patches needs to go through your tree. If it needs to
> be in separate branch, then I can add that as part of the
> other generic patches with your ack.
> 
>>  arch/arm/boot/dts/omap5-evm.dts  |    2 +-
>>  arch/arm/boot/dts/omap5.dtsi     |  282 +++++++++++++++++++++++++++++++++++---
>>  arch/arm/mach-omap2/omap_hwmod.c |   31 ++++-
>>  3 files changed, 293 insertions(+), 22 deletions(-)
>>
> 
> Let me know your preference. Either way is fine by me.

I can take both DTS and hwmod patches, so you can keep then in the same
series.

Thanks,
Benoit

  reply	other threads:[~2013-03-15 12:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 15:38 [PATCH 0/8] ARM: dts: OMAP5: ocp address space and few updates Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 1/8] ARM: dts: omap5-evm: Update available memory to 2032 MB Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 2/8] ARM: dts: OMAP5: Align the local timer dt node as per the current binding code Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 3/8] ARM: dts: OMAP5: Specify nonsecure PPI IRQ for arch timer Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 4/8] ARM: dts: OMAP5: Move the gic node out of ocp space Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 5/8] ARM: dts: OMAP5: Update the timer and gic nodes for HYP kernel support Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 6/8] ARM: dts: OMAP5: Update keypad reg property Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 7/8] ARM: OMAP: hwmod: extract module address space from DT blob Santosh Shilimkar
2013-02-20 15:42   ` Felipe Balbi
2013-02-20 15:46     ` Santosh Shilimkar
2013-02-20 15:38 ` [PATCH 8/8] ARM: dts: OMAP5: Add ocp address space for all hwmods Santosh Shilimkar
2013-02-25 10:56   ` Benoit Cousson
2013-02-25 11:16     ` Santosh Shilimkar
2013-03-15 10:24 ` [PATCH 0/8] ARM: dts: OMAP5: ocp address space and few updates Santosh Shilimkar
2013-03-15 12:45   ` Benoit Cousson [this message]
2013-03-15 12:53     ` Santosh Shilimkar

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=514317EC.6040400@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).