From: afzal@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 00/13] ARM: OMAP2+: AM43x PRCM support
Date: Thu, 18 Jul 2013 16:37:06 +0530 [thread overview]
Message-ID: <51E7CC5A.8020906@ti.com> (raw)
In-Reply-To: <cover.1373519192.git.afzal@ti.com>
Hi Tony, Paul,
On 7/11/2013 12:03 PM, Afzal Mohammed wrote:
> AM43x PRCM support (excluding clock tree) is being added with this
> series. AM43x reuses most of the IP's from AM335x, as that is the
> case, it was felt that reusing AM335x code as much as possible for
> AM43x is better - it also helps to keep LOC less.
> Major reuse has been with hwmod database of AM335x, moving common
> elements to a new array and keeping separate arrays for elements that
> are specific only to either one of AM335x or AM43x. And in the cases
> where relevant IP is present in both that has difference in details
> like CLKCTRL register offsets, it is being updated at runtime based on
> the SoC detected.
> This series is being developed with additional clock tree changes that
> would be DT'fied.
> Additional DTS changes are also required for hwmod to get register
> target address space as most of AM335x hwmod address space details has
> been recently cleaned up and moved to DTS.
> ********
>
> This RFC is being posted to get an early feedback on approach taken
> here mainly w.r.t reusing AM335x hwmod database for AM43x.
>
> ********
Please let me know your comments on this series.
Most of the IP's in AM335x is reused on AM43x and hence out of the
existing 77 hwmod ocpif entries on AM335x, 73 are reused on AM43x by
moving to a common array (only 4 is left AM335x specific).
Even the address space of those peripherals that are common between
AM335x & AM43x is same. And AM43x has only a few newer IP's as
compared to AM335x.
Regards
Afzal
prev parent reply other threads:[~2013-07-18 11:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 6:33 [PATCH RFC 00/13] ARM: OMAP2+: AM43x PRCM support Afzal Mohammed
2013-07-11 6:34 ` [PATCH RFC 01/13] ARM: OMAP2+: hwmod: AM335x: prepare for AM43x reuse Afzal Mohammed
2013-07-11 6:35 ` [PATCH RFC 02/13] ARM: OMAP2+: hwmod: AMx3: runtime AM335x handling Afzal Mohammed
2013-07-11 6:35 ` [PATCH RFC 03/13] ARM: OMAP2+: hwmod: AMx3: remove common static fields Afzal Mohammed
2013-07-11 6:35 ` [PATCH RFC 04/13] ARM: OMAP2+: CM: cm_inst offset s16->u16 Afzal Mohammed
2013-07-11 6:35 ` [PATCH RFC 05/13] ARM: OMAP2+: PRCM: AM43x definitions Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 06/13] ARM: OMAP2+: PM: AM43x powerdomain data Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 07/13] ARM: OMAP2+: CM: AM43x clockdomain data Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 08/13] ARM: OMAP2+: hwmod: AMx3: runtime AM43x handling Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 09/13] ARM: OMAP2+: hwmod: AM43x operations Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 10/13] ARM: OMAP2+: AM43x: PRCM kbuild Afzal Mohammed
2013-07-11 6:36 ` [PATCH RFC 11/13] ARM: OMAP2+: AM43x PRCM init Afzal Mohammed
2013-07-11 6:37 ` [PATCH RFC 12/13] ARM: OMAP2+: hwmod: type4 sysc Afzal Mohammed
2013-07-11 6:37 ` [PATCH RFC 13/13] ARM: OMAP2+: hwmod: AM43x: new w.r.t AM335x Afzal Mohammed
2013-07-11 7:06 ` Gupta, Pekon
2013-07-18 11:07 ` Afzal Mohammed [this message]
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=51E7CC5A.8020906@ti.com \
--to=afzal@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).