From: Afzal Mohammed <afzal@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Paul Walmsley <paul@pwsan.com>,
Benoit Cousson <bcousson@baylibre.com>,
Tony Lindgren <tony@atomide.com>, Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH v6 00/11] ARM: OMAP2+: AM43x PRCM basic support
Date: Sat, 12 Oct 2013 15:43:20 +0530 [thread overview]
Message-ID: <cover.1381569236.git.afzal@ti.com> (raw)
Hi Paul,
This series adds PRCM support (except clock tree) for AM43x SoC's.
Please consider this for inclusion in the coming merge window.
This series has been tested on real silicon in AM43x EPOS EVM board with
the help of Tero's DT clock series and booted to prompt. This has been
tested on AM335x-EVM too.
These changes are made over your "for-v3.13/hwmod" tag
Changes compared to v5:
1. Rebased over "for-v3.13/hwmod" tag
2. rtc hwmod has been removed from AM43x hwmod database as rtc had
issues on EPOS EVM
3. spinlock hwmod has been removed from AM43x hwmod database since
sysconfig details has been recently added and as it doesn't have dt
node, that would cause warning, spinlock has to be added after dt
node has been added
4. Added Acked-by's from Tony and Rajendra
5. Minor fixing in comments
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-v6
Compared to v4, 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
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.
6. Remove the change that re-introduces SW_SLEEP for OMAP4, this will
be taken care separately.
Additional 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 (7):
ARM: OMAP2+: hwmod: AM335x/AM43x: move common data
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 | 196 ++
arch/arm/mach-omap2/cm33xx.c | 16 +-
arch/arm/mach-omap2/cm33xx.h | 12 +-
arch/arm/mach-omap2/cminst44xx.c | 29 +-
arch/arm/mach-omap2/cminst44xx.h | 26 +-
arch/arm/mach-omap2/io.c | 6 +
arch/arm/mach-omap2/omap_hwmod.c | 8 +
arch/arm/mach-omap2/omap_hwmod.h | 1 +
.../mach-omap2/omap_hwmod_33xx_43xx_common_data.h | 163 ++
.../omap_hwmod_33xx_43xx_interconnect_data.c | 643 +++++++
.../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 1469 +++++++++++++++
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 1979 +-------------------
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 619 ++++++
arch/arm/mach-omap2/powerdomain.h | 1 +
arch/arm/mach-omap2/powerdomains43xx_data.c | 136 ++
arch/arm/mach-omap2/prcm43xx.h | 141 ++
18 files changed, 3442 insertions(+), 2016 deletions(-)
create mode 100644 arch/arm/mach-omap2/clockdomains43xx_data.c
create mode 100644 arch/arm/mach-omap2/omap_hwmod_33xx_43xx_common_data.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-10-12 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 10:13 Afzal Mohammed [this message]
2013-10-12 10:14 ` [PATCH v6 01/11] ARM: OMAP2+: CM: cm_inst offset s16->u16 Afzal Mohammed
2013-10-12 10:15 ` [PATCH v6 03/11] ARM: OMAP2+: hwmod: AM335x: runtime register update Afzal Mohammed
2013-10-12 10:15 ` [PATCH v6 04/11] ARM: OMAP2+: hwmod: AM335x: remove static register offs Afzal Mohammed
2013-10-12 10:15 ` [PATCH v6 05/11] ARM: OMAP2+: PRCM: AM43x definitions Afzal Mohammed
2013-10-12 10:15 ` [PATCH v6 06/11] ARM: OMAP2+: PM: AM43x powerdomain data Afzal Mohammed
2013-10-12 10:16 ` [PATCH v6 07/11] ARM: OMAP2+: CM: AM43x clockdomain data Afzal Mohammed
2013-10-12 10:16 ` [PATCH v6 08/11] ARM: OMAP2+: hwmod: AM43x support Afzal Mohammed
2013-10-12 10:16 ` [PATCH v6 09/11] ARM: OMAP2+: hwmod: AM43x operations Afzal Mohammed
2013-10-12 10:16 ` [PATCH v6 10/11] ARM: OMAP2+: AM43x: PRCM kbuild Afzal Mohammed
2013-10-12 10:16 ` [PATCH v6 11/11] 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.1381569236.git.afzal@ti.com \
--to=afzal@ti.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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 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).