All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [PATCH 11/14] OMAP4: PRCM: reorganize existing OMAP4 PRCM header files
Date: Thu, 9 Dec 2010 23:31:57 +0100	[thread overview]
Message-ID: <4D0158DD.30200@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012072340250.13430@utopia.booyaka.com>

Salut Paul,

On 12/8/2010 7:47 AM, Paul Walmsley wrote:
> Salut Benoît,
>
> On Tue, 7 Dec 2010, Cousson, Benoit wrote:
>
>> Salut Paul,
>>
>> On 12/7/2010 2:25 AM, Paul Walmsley wrote:
>>> Split the existing cm44xx.h file into cm1_44xx.h and cm2_44xx.h files
>>> so they match their underlying OMAP hardware modules.  Add clockdomain
>>> offset information.
>>>
>>> Add header files for the MPU local PRCM, prcm_mpu44xx.h, and for the
>>> SCRM, scrm44xx.h.  SCRM register offsets still need to be added; TI
>>> should do this.
>>
>> And we did it :-)
>
> Even better :-)
>
>> I sent it last week along with clock data series:
>> https://patchwork.kernel.org/patch/373751/
>>
>> OK, I've just realized that it was a little bit hidden in the clock data
>> patch, and maybe we should have been sent two patches.
>> Sorry for that. Do you want to take it in that series, or should I re-sent the
>> clock data one?
>
> I guess it's better done in the clock series; that should avoid a branch
> dependency between the PRCM patchsets and the clock patch sets.
>
> One thing that would be nice on the scrm44xx.h file is to keep the _OFFSET
> macros.  It would be nice in the long run to get rid of the absolute
> addressing macros in case someone decides to shuffle around the IP block
> addresses again... can you update your clock series with that change?

OK, this is done. I've just posted it.

Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/14] OMAP4: PRCM: reorganize existing OMAP4 PRCM header files
Date: Thu, 9 Dec 2010 23:31:57 +0100	[thread overview]
Message-ID: <4D0158DD.30200@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012072340250.13430@utopia.booyaka.com>

Salut Paul,

On 12/8/2010 7:47 AM, Paul Walmsley wrote:
> Salut Beno?t,
>
> On Tue, 7 Dec 2010, Cousson, Benoit wrote:
>
>> Salut Paul,
>>
>> On 12/7/2010 2:25 AM, Paul Walmsley wrote:
>>> Split the existing cm44xx.h file into cm1_44xx.h and cm2_44xx.h files
>>> so they match their underlying OMAP hardware modules.  Add clockdomain
>>> offset information.
>>>
>>> Add header files for the MPU local PRCM, prcm_mpu44xx.h, and for the
>>> SCRM, scrm44xx.h.  SCRM register offsets still need to be added; TI
>>> should do this.
>>
>> And we did it :-)
>
> Even better :-)
>
>> I sent it last week along with clock data series:
>> https://patchwork.kernel.org/patch/373751/
>>
>> OK, I've just realized that it was a little bit hidden in the clock data
>> patch, and maybe we should have been sent two patches.
>> Sorry for that. Do you want to take it in that series, or should I re-sent the
>> clock data one?
>
> I guess it's better done in the clock series; that should avoid a branch
> dependency between the PRCM patchsets and the clock patch sets.
>
> One thing that would be nice on the scrm44xx.h file is to keep the _OFFSET
> macros.  It would be nice in the long run to get rid of the absolute
> addressing macros in case someone decides to shuffle around the IP block
> addresses again... can you update your clock series with that change?

OK, this is done. I've just posted it.

Regards,
Benoit

  reply	other threads:[~2010-12-09 22:32 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07  1:24 [PATCH 00/14] OMAP: PRCM/powerdomain/clockdomain patches for 2.6.38, part one Paul Walmsley
2010-12-07  1:24 ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 01/14] OMAP: powerdomain: Move static allocations from powerdomains.h to a .c file Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 02/14] OMAP: powerdomain: Infrastructure to put arch specific code Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 03/14] OMAP: powerdomain: Arch specific funcs for state control Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 04/14] OMAP: powerdomain: Arch specific funcs for logic control Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 05/14] OMAP: powerdomain: Arch specific funcs for mem control Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 06/14] OMAP4: powerdomain: Add pwrdm_clear_all_prev_pwrst Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 07/14] OMAP2+: powerdomains: move powerdomain static data to .c files Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 08/14] OMAP2+: clockdomains: move clockdomain " Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 09/14] OMAP3: control/PRCM: add omap3_ctrl_write_boot_mode() Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 10/14] OMAP3: control/PRCM: move CONTROL_PADCONF_SYS_NIRQ save/restore to SCM code Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 11/14] OMAP4: PRCM: reorganize existing OMAP4 PRCM header files Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  8:09   ` Cousson, Benoit
2010-12-07  8:09     ` Cousson, Benoit
2010-12-08  6:47     ` Paul Walmsley
2010-12-08  6:47       ` Paul Walmsley
2010-12-09 22:31       ` Cousson, Benoit [this message]
2010-12-09 22:31         ` Cousson, Benoit
2010-12-07 20:43   ` Cousson, Benoit
2010-12-07 20:43     ` Cousson, Benoit
2010-12-08  6:40     ` Paul Walmsley
2010-12-08  6:40       ` Paul Walmsley
2010-12-08 20:57       ` Kevin Hilman
2010-12-08 20:57         ` Kevin Hilman
2010-12-07  1:25 ` [PATCH 12/14] OMAP4: PRCM: rename _MOD macros to _INST Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 13/14] OMAP2/3: PRCM: split OMAP2/3-specific PRCM code into OMAP2/3-specific files Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-07 13:37   ` Mark Brown
2010-12-07 13:37     ` Mark Brown
2010-12-15  4:50   ` Paul Walmsley
2010-12-15  4:50     ` Paul Walmsley
2010-12-15 12:23     ` Felipe Contreras
2010-12-15 12:23       ` Felipe Contreras
2010-12-22  3:51       ` Paul Walmsley
2010-12-22  3:51         ` Paul Walmsley
2010-12-15 16:39     ` Ramirez Luna, Omar
2010-12-15 16:39       ` Ramirez Luna, Omar
2010-12-22  4:10       ` Paul Walmsley
2010-12-22  4:10         ` Paul Walmsley
2010-12-07  1:25 ` [PATCH 14/14] OMAP3: PRM/CM: separate CM context save/restore; remove PRM context save/restore Paul Walmsley
2010-12-07  1:25   ` Paul Walmsley
2010-12-08  0:16 ` [PATCH 00/14] OMAP: PRCM/powerdomain/clockdomain patches for 2.6.38, part one Kevin Hilman
2010-12-08  0:16   ` Kevin Hilman
2010-12-08  6:20   ` Paul Walmsley
2010-12-08  6:20     ` Paul Walmsley

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=4D0158DD.30200@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@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.