From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] OMAP4: Add 4460 base support
Date: Sat, 2 Jul 2011 08:00:20 +0530 [thread overview]
Message-ID: <1309573826-10615-1-git-send-email-rnayak@ti.com> (raw)
This series adds base support needed to be able
to boot on a OMAP4460 device.
Patches are based on
git://gitorious.org/omap-pm/linux.git for_3.1/7_hwmod_modulemode
and boot tested on 4430sdp and 4460sdp boards.
The series updates the prcm/clock and clockdomain/powerdomain
data files which are also cleaned up/fixed by the various series
posted by Benoit, and hence the dependency.
Changes since v1:
1. Removed the minor issues in the ID detection patches
2. Dropped '4460sdp/blaze/panda: hwmod: Prevent gpio1 reset during hwmod init'
since the right way to fix it is to do a lazy-disable in hmwod as suggested
by Tony.
For now, with this patch dropped and until the lazy-disable for hwmod
gets in, 4460 based devices can only boot reliably at OPP50 on MPU.
Aneesh V (2):
OMAP: ID: introduce chip detection for OMAP4460
OMAP4: ID: add omap_has_feature for max freq supported
Rajendra Nayak (4):
OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts
OMAP4: clocks: Update the clock tree with 4460 clock nodes
OMAP4: powerdomain: Reuse on 4460 using CHIP_IS_44XX
OMAP4: clockdomain: Reuse on 4460 using CHIP_IS_44XX
arch/arm/mach-omap2/clock44xx_data.c | 39 +++++
arch/arm/mach-omap2/clockdomains44xx_data.c | 200 ++++++++++++------------
arch/arm/mach-omap2/cm-regbits-44xx.h | 36 +++++
arch/arm/mach-omap2/id.c | 53 ++++++-
arch/arm/mach-omap2/powerdomains44xx_data.c | 32 ++--
arch/arm/mach-omap2/prm-regbits-44xx.h | 8 +
arch/arm/plat-omap/include/plat/clkdev_omap.h | 2 +-
arch/arm/plat-omap/include/plat/clock.h | 3 +-
arch/arm/plat-omap/include/plat/cpu.h | 36 ++++-
9 files changed, 279 insertions(+), 130 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-07-02 2:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 2:30 Rajendra Nayak [this message]
2011-07-02 2:30 ` [PATCH v2 1/6] OMAP: ID: introduce chip detection for OMAP4460 Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 2/6] OMAP4: ID: add omap_has_feature for max freq supported Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 3/6] OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 4/6] OMAP4: clocks: Update the clock tree with 4460 clock nodes Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 5/6] OMAP4: powerdomain: Reuse on 4460 using CHIP_IS_44XX Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 6/6] OMAP4: clockdomain: " Rajendra Nayak
2011-07-08 6:51 ` Paul Walmsley
2011-07-08 6:51 ` [PATCH v2 5/6] OMAP4: powerdomain: " Paul Walmsley
2011-07-08 6:49 ` [PATCH v2 4/6] OMAP4: clocks: Update the clock tree with 4460 clock nodes Paul Walmsley
2011-07-08 7:09 ` Rajendra Nayak
2011-07-08 7:35 ` Paul Walmsley
2011-07-08 10:52 ` Tony Lindgren
2011-07-08 6:30 ` [PATCH v2 3/6] OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts Paul Walmsley
2011-07-08 7:01 ` Rajendra Nayak
2011-07-08 7:34 ` Paul Walmsley
2011-07-08 10:51 ` Tony Lindgren
2011-07-08 6:42 ` [PATCH v2 2/6] OMAP4: ID: add omap_has_feature for max freq supported Paul Walmsley
2011-08-04 23:33 ` Menon, Nishanth
2011-07-08 6:39 ` [PATCH v2 1/6] OMAP: ID: introduce chip detection for OMAP4460 Paul Walmsley
2011-07-08 10:49 ` 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=1309573826-10615-1-git-send-email-rnayak@ti.com \
--to=rnayak@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).