From: nm@ti•com (Nishanth Menon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFC v3 08/12] ARM: OMAP2+: CM: AM43x clockdomain data
Date: Tue, 17 Sep 2013 09:33:40 -0500 [thread overview]
Message-ID: <52386844.9070501@ti.com> (raw)
In-Reply-To: <523867AD.9080905@ti.com>
On 09/17/2013 09:31 AM, Afzal Mohammed wrote:
> Hi Nishant,
>
> On Monday 16 September 2013 08:56 PM, Nishanth Menon wrote:
>> On 09/16/2013 08:48 AM, Afzal Mohammed wrote:
>
>>> From: Ambresh K <ambresh@ti•com>
>>>
>>> Add the data file to describe clock domains in AM43x SoC.
>>> OMAP4 clockdomain operations is being reused here.
>>>
>>> Signed-off-by: Ambresh K <ambresh@ti•com>
>>> Signed-off-by: Afzal Mohammed <afzal@ti•com>
>>> ---
>>> arch/arm/mach-omap2/clockdomain.h | 2 +
>>> arch/arm/mach-omap2/clockdomains43xx_data.c | 199 ++++++++++++++++++++++++++++
>>> arch/arm/mach-omap2/cminst44xx.c | 9 ++
>>> 3 files changed, 210 insertions(+)
>>> create mode 100644 arch/arm/mach-omap2/clockdomains43xx_data.c
>>
>> I suggest we drop this. this can be addressed by Tero's clk series.
>
> Probably you misunderstood clock domain data as clock data, as Tero's
> series does not take care of clock domain data, we would require this.
Arrgh.. yes - my bad. thanks for clarifying.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-09-17 14:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:46 [PATCH RFC v3 00/12] ARM: OMAP2+: AM43x PRCM basic support Afzal Mohammed
2013-09-16 13:47 ` [PATCH RFC v3 01/12] ARM: OMAP2+: CM: cm_inst offset s16->u16 Afzal Mohammed
2013-09-16 13:47 ` [PATCH RFC v3 02/12] ARM: OMAP2+: hwmod: AM335x/AM43x: move common ocpif Afzal Mohammed
2013-09-16 13:47 ` [PATCH RFC v3 03/12] ARM: OMAP2+: hwmod: AM335x/AM43x: move common hwmod Afzal Mohammed
2013-09-16 13:47 ` [PATCH RFC v3 04/12] ARM: OMAP2+: hwmod: AM335x: runtime register update Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 05/12] ARM: OMAP2+: hwmod: AM335x: remove static register offs Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 06/12] ARM: OMAP2+: PRCM: AM43x definitions Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 07/12] ARM: OMAP2+: PM: AM43x powerdomain data Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 08/12] ARM: OMAP2+: CM: AM43x clockdomain data Afzal Mohammed
2013-09-16 15:26 ` Nishanth Menon
2013-09-17 14:31 ` Afzal Mohammed
2013-09-17 14:33 ` Nishanth Menon [this message]
2013-09-16 13:48 ` [PATCH RFC v3 09/12] ARM: OMAP2+: hwmod: AM43x support Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 10/12] ARM: OMAP2+: hwmod: AM43x operations Afzal Mohammed
2013-09-16 13:48 ` [PATCH RFC v3 11/12] ARM: OMAP2+: AM43x: PRCM kbuild Afzal Mohammed
2013-09-16 13:49 ` [PATCH RFC v3 12/12] ARM: OMAP2+: AM43x PRCM init Afzal Mohammed
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=52386844.9070501@ti.com \
--to=nm@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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