From: rnayak@ti•com (Rajendra Nayak)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 00/11] ARM: OMAP2+: AM43x PRCM basic support
Date: Thu, 10 Oct 2013 10:55:38 +0530 [thread overview]
Message-ID: <52563A52.7020209@ti.com> (raw)
In-Reply-To: <20131008181535.GF8313@atomide.com>
On Tuesday 08 October 2013 11:45 PM, Tony Lindgren wrote:
> * Rajendra Nayak <rnayak@ti•com> [131003 23:50]:
>> On Tuesday 01 October 2013 12:34 PM, Afzal Mohammed wrote:
>>> Hi Paul, Benoit, Tony,
>>>
>>> This series adds PRCM support (except clock tree) for AM43x SoC's.
>>> Please consider this for inclusion in the coming merge window.
>>>
>>> Patch 02/11 "ARM: OMAP2+: hwmod: AM335x/AM43x: move common data" may
>>> not reach mailing lists due to bigger size, this series is also present
>>> @git://gitorious.org/x0148406-public/linux-kernel.git tags/am43x-prcm-v5
>>>
>>> Compared to v4, only change is in fixing the powerdomain data.
>>>
>>> Major changes compared to rfc v3:
>>> 1. All register offsets properly taken care for AM43x (with rfc v3, a
>>> couple of issues was detected while testing on pre-silicon)
>>> 2. There were two patches for common hwmod data movement (one for
>>> interconnect and other for ip block data), both were combined to have
>>> a cleaner series that is bisectable.
>>> 3. Cleaner seperation of common data
>>>
>>> Major changes compared to v2 (v3 was only an rfc for current approach):
>>> 1. omap_hwmod_33xx_43xx_interconnect_data.c has the common interconnect
>>> ocp's structs shared between AM335x and AM43x
>>> 2. omap_hwmod_33xx_43xx_ipblock_data.c has the common hwmod structs
>>> shared between AM335x and AM43x
>>
>> This split and reuse looks much better and readable now.
>>
>> For the complete series,
>> Acked-by: Rajendra Nayak <rnayak@ti•com>
>
> Looks good to me too. I'm assuming that Paul will queue this.
>
> And let's everybody make note that this will be the _last_ set of
> hwmod data we'll _ever_ merge as this all should be replaced with
> device tree + bus driver based approach for future SoCs.
>
> But let's get the common clock framework conversion done first, so
> this can wait until after that.
Tony, I hope you meant the 'hwmod replaced with device tree + bus driver
based approach' is what can wait until after the common clock framework DT
conversion and not the $subject series itself :)
regards,
Rajendra
>
> Acked-by: Tony Lindgren <tony@atomide•com>
>
next prev parent reply other threads:[~2013-10-10 5:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 7:04 [PATCH v5 00/11] ARM: OMAP2+: AM43x PRCM basic support Afzal Mohammed
2013-10-01 7:06 ` [PATCH v5 01/11] ARM: OMAP2+: CM: cm_inst offset s16->u16 Afzal Mohammed
2013-10-01 7:07 ` [PATCH v5 03/11] ARM: OMAP2+: hwmod: AM335x: runtime register update Afzal Mohammed
2013-10-01 7:07 ` [PATCH v5 04/11] ARM: OMAP2+: hwmod: AM335x: remove static register offs Afzal Mohammed
2013-10-01 7:07 ` [PATCH v5 05/11] ARM: OMAP2+: PRCM: AM43x definitions Afzal Mohammed
2013-10-01 7:07 ` [PATCH v5 06/11] ARM: OMAP2+: PM: AM43x powerdomain data Afzal Mohammed
2013-10-01 7:07 ` [PATCH v5 07/11] ARM: OMAP2+: CM: AM43x clockdomain data Afzal Mohammed
2013-10-01 7:08 ` [PATCH v5 08/11] ARM: OMAP2+: hwmod: AM43x support Afzal Mohammed
2013-10-01 7:08 ` [PATCH v5 09/11] ARM: OMAP2+: hwmod: AM43x operations Afzal Mohammed
2013-10-01 7:08 ` [PATCH v5 10/11] ARM: OMAP2+: AM43x: PRCM kbuild Afzal Mohammed
2013-10-01 7:14 ` [PATCH v5 11/11] ARM: OMAP2+: AM43x PRCM init Afzal Mohammed
2013-10-04 6:42 ` [PATCH v5 00/11] ARM: OMAP2+: AM43x PRCM basic support Rajendra Nayak
2013-10-08 18:15 ` Tony Lindgren
2013-10-10 5:25 ` Rajendra Nayak [this message]
2013-10-10 16:31 ` Tony Lindgren
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=52563A52.7020209@ti.com \
--to=rnayak@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