From: "Nayak, Rajendra" <rnayak@ti.com>
To: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2 register defs for OMAP4
Date: Thu, 13 Aug 2009 13:49:08 +0530 [thread overview]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB030605080A@dbde02.ent.ti.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89444A6ED6C0@dlee02.ent.ti.com>
>-----Original Message-----
>From: Aguirre Rodriguez, Sergio Alberto
>Sent: Wednesday, August 12, 2009 11:11 PM
>To: Nayak, Rajendra; linux-arm-kernel@lists.arm.linux.org.uk
>Cc: linux-omap@vger.kernel.org
>Subject: RE: [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2
>register defs for OMAP4
>
>Rajendra,
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of Nayak, Rajendra
>> Sent: Wednesday, August 12, 2009 9:28 AM
>> To: linux-arm-kernel@lists.arm.linux.org.uk
>> Cc: linux-omap@vger.kernel.org; Nayak, Rajendra
>> Subject: [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2 register
>defs for OMAP4
>>
>> This patch adds OMAP4 specific CM1 and CM2 module
>> register defs and corresponding register field bit
>> shifts
>>
>> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
>> ---
>> arch/arm/mach-omap2/cm.h | 249
>> +++++++++++++++++++++++++++++-
>> arch/arm/mach-omap2/cm1-regbits-44xx.h | 161 +++++++++++++++++++
>> arch/arm/mach-omap2/cm2-regbits-44xx.h | 269
>> ++++++++++++++++++++++++++++++++
>> 3 files changed, 678 insertions(+), 1 deletions(-)
>> create mode 100644 arch/arm/mach-omap2/cm1-regbits-44xx.h
>> create mode 100644 arch/arm/mach-omap2/cm2-regbits-44xx.h
>>
>> diff --git a/arch/arm/mach-omap2/cm.h b/arch/arm/mach-omap2/cm.h
>> index 1d3c93b..19f7aeb 100644
>> --- a/arch/arm/mach-omap2/cm.h
>> +++ b/arch/arm/mach-omap2/cm.h
>> @@ -4,10 +4,11 @@
>> /*
>> * OMAP2/3 Clock Management (CM) register definitions
>
>According to the new content, this should be updated aswell, like:
>
>OMAP2/3/4 Clock Management (CM) register definitions
Yes, I'll update that, thanks.
>
>Regards,
>Sergio
>
><snip>
>
>
next prev parent reply other threads:[~2009-08-13 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 14:27 [PATCH v2 1/6] ARM: OMAP4: PM: Fix the PRM and CM base addresses Rajendra Nayak
2009-08-12 14:27 ` [PATCH v2 2/6] ARM: OMAP4: PM: PRM/CM module offsets for OMAP4 Rajendra Nayak
2009-08-12 14:27 ` [PATCH v2 3/6] ARM: OMAP4: PM: Adds PRM register defs " Rajendra Nayak
2009-08-12 14:27 ` [PATCH v2 4/6] ARM: OMAP4: PM: Adds PRM register shift and mask bits Rajendra Nayak
2009-08-12 14:27 ` [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2 register defs for OMAP4 Rajendra Nayak
2009-08-12 14:27 ` [PATCH v2 6/6] ARM: OMAP4: PM: Adds CM1/2 register field masks Rajendra Nayak
2009-08-12 17:40 ` [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2 register defs for OMAP4 Aguirre Rodriguez, Sergio Alberto
2009-08-13 8:19 ` Nayak, Rajendra [this message]
2009-08-13 13:33 ` [PATCH v2 4/6] ARM: OMAP4: PM: Adds PRM register shift and mask bits Paul Walmsley
2009-08-12 17:37 ` [PATCH v2 3/6] ARM: OMAP4: PM: Adds PRM register defs for OMAP4 Aguirre Rodriguez, Sergio Alberto
2009-08-13 13:41 ` [PATCH v2 2/6] ARM: OMAP4: PM: PRM/CM module offsets " Paul Walmsley
2009-08-12 15:45 ` [PATCH v2 1/6] ARM: OMAP4: PM: Fix the PRM and CM base addresses Aguirre Rodriguez, Sergio Alberto
2009-08-13 8:18 ` Nayak, Rajendra
2009-08-13 13:06 ` Aguirre Rodriguez, Sergio Alberto
2009-12-08 18:15 Rajendra Nayak
2009-12-08 18:15 ` [PATCH v2 2/6] ARM: OMAP4: PM: PRM/CM module offsets for OMAP4 Rajendra Nayak
2009-12-08 18:16 ` [PATCH v2 3/6] ARM: OMAP4: PM: Adds PRM register defs " Rajendra Nayak
2009-12-08 18:16 ` [PATCH v2 4/6] ARM: OMAP4: PM: Adds PRM register shift and mask bits Rajendra Nayak
2009-12-08 18:16 ` [PATCH v2 5/6] ARM: OMAP4: PM: Adds CM1/2 register defs for OMAP4 Rajendra Nayak
2009-12-08 18:16 ` Rajendra Nayak
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=5A47E75E594F054BAF48C5E4FC4B92AB030605080A@dbde02.ent.ti.com \
--to=rnayak@ti.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@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.