From: afzal@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v3 00/12] ARM: OMAP2+: AM43x PRCM basic support
Date: Mon, 16 Sep 2013 19:16:02 +0530 [thread overview]
Message-ID: <cover.1379337301.git.afzal@ti.com> (raw)
Hi Paul, Benoit,
This series adds PRCM support for AM43x SoC's. It has been modified
as compared to last version based on Rajendra's comments and discussion
with him, please let me know your comments on this series.
Major changes (as compared to v2):
1. omap_hwmod_33xx_43xx_interconnect_data.c has all the common
interconnect ocp's structs shared between AM335x and AM43x
2. omap_hwmod_33xx_43xx_ipblock_data.c has all the common hwmod structs
shared between AM335x and AM43x
3. Instances where clock domain or clock topology has changed in the few
cases, have separate structures for AM335x and AM43x
4. To handle scenarios where register offsets are different, they are
dynamically init-ed in omap_hwmod_33xx_43xx_ipblock_data.c
5. Register offsets for hwmod's that are present either in AM335x or
AM43x are updated statically in omap_hwmod_33xx_data.c or
omap_hwmod_43xx_data.c as that was cleaner.
Please note that this series is only compile tested, yet to be tested on
pre-silicon platform (hence RFC), testing on pre-silicon platform takes
huge amount of time (1 second realtime ~ 1 hour on pre-silicon). Here
the intention is to get early feedback on the approach taken for hwmod.
This series has been boot tested on AM335x-EVM.
And the diffstat is now +1500 (+3500 -2000).
The change that re-introduces SW_SLEEP for OMAP4 has been left out from
this series, it will be properly taken care in the next version - as
here main intention is to know acceptability of approach towards hwmod.
Some more details:
AM43x reuses most of the IP's from AM335x, as that is the case, much of
the AM335x hwmod data is reused. As AM43x PRCM register layout differs
from AM335x and is similar to OMAP4, power domain, clock domain & hwmod
operations are reused from OMAP4. Currently there is no public TRM
available for AM43x.
Regards
Afzal
Afzal Mohammed (8):
ARM: OMAP2+: hwmod: AM335x/AM43x: move common ocpif
ARM: OMAP2+: hwmod: AM335x/AM43x: move common hwmod
ARM: OMAP2+: hwmod: AM335x: runtime register update
ARM: OMAP2+: hwmod: AM335x: remove static register offs
ARM: OMAP2+: PRCM: AM43x definitions
ARM: OMAP2+: hwmod: AM43x support
ARM: OMAP2+: hwmod: AM43x operations
ARM: OMAP2+: AM43x: PRCM kbuild
Ambresh K (3):
ARM: OMAP2+: PM: AM43x powerdomain data
ARM: OMAP2+: CM: AM43x clockdomain data
ARM: OMAP2+: AM43x PRCM init
Ankur Kishore (1):
ARM: OMAP2+: CM: cm_inst offset s16->u16
arch/arm/mach-omap2/Makefile | 9 +-
arch/arm/mach-omap2/clockdomain.h | 4 +-
arch/arm/mach-omap2/clockdomains43xx_data.c | 199 ++
arch/arm/mach-omap2/cm33xx.c | 30 +-
arch/arm/mach-omap2/cm33xx.h | 28 +-
arch/arm/mach-omap2/cminst44xx.c | 40 +-
arch/arm/mach-omap2/cminst44xx.h | 25 +-
arch/arm/mach-omap2/io.c | 6 +
arch/arm/mach-omap2/omap_hwmod.c | 8 +
arch/arm/mach-omap2/omap_hwmod.h | 1 +
arch/arm/mach-omap2/omap_hwmod_33xx_43xx_common.h | 157 ++
.../omap_hwmod_33xx_43xx_interconnect_data.c | 656 +++++++
.../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 1475 +++++++++++++++
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 1969 +-------------------
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 645 +++++++
arch/arm/mach-omap2/powerdomain.h | 1 +
arch/arm/mach-omap2/powerdomains43xx_data.c | 145 ++
arch/arm/mach-omap2/prcm43xx.h | 141 ++
18 files changed, 3514 insertions(+), 2025 deletions(-)
create mode 100644 arch/arm/mach-omap2/clockdomains43xx_data.c
create mode 100644 arch/arm/mach-omap2/omap_hwmod_33xx_43xx_common.h
create mode 100644 arch/arm/mach-omap2/omap_hwmod_33xx_43xx_interconnect_data.c
create mode 100644 arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
create mode 100644 arch/arm/mach-omap2/omap_hwmod_43xx_data.c
create mode 100644 arch/arm/mach-omap2/powerdomains43xx_data.c
create mode 100644 arch/arm/mach-omap2/prcm43xx.h
--
1.8.3.4
next reply other threads:[~2013-09-16 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:46 Afzal Mohammed [this message]
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
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=cover.1379337301.git.afzal@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).