From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx
Date: Wed, 16 Feb 2011 16:45:17 +0530 [thread overview]
Message-ID: <43af56d25809fa616f0e17d7e641ebc0@mail.gmail.com> (raw)
In-Reply-To: <20110216065030.22089.61217.stgit@twilight.localdomain>
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org
[mailto:linux-arm-kernel-bounces at lists.infradead.org] On Behalf
> Of Paul Walmsley
> Sent: Wednesday, February 16, 2011 12:23 PM
> To: linux-omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
> Subject: [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks,
OMAP2xxx
>
> Hello,
>
> This patch series adds clock framework-controlled autoidle support for
> the OMAP2xxx DPLL, APLLs, and OMAP2/3 interface clocks. The old
> direct register writes in the PM code to enable clock autoidle have been
> removed.
>
> This series also ensures that all clock autoidle is disabled during
> boot and only re-enabled if CONFIG_PM is enabled.
>
> The series applies on the 'clk_autoidle_a_2.6.39' branch of
> git://git.pwsan.com/linux-2.6.
>
> Boot-tested on N800, and dynamic idle-tested on OMAP3430 Beagleboard.
> Compile-tested with omap1_defconfig, omap2plus_defconfig, a 5912
> OSK-only config, an N8x0-only config, an OMAP3-only config, and an
OMAP4-only
> config.
Boot-tested on 3430sdp/4430sdp, with CONFIG_PM and with !CONFIG_PM.
suspend-offmode tested on 3430sdp and suspend-retmode on 4430sdp (with
some out-of-tree patches)
Dynamic idle testing on 3430sdp showed me some very jerky debug console
the
moment a 'echo 1 > /debug/pm_debug/sleep_while_idle' is done.
This however seems to be the case even on 2.6.38-rc4 and not related to
the
current patch series. Will debug further, but seems to some 3430sdp
specific
issue, since you did not see it on Beagleboard and seems it is not seen on
OMAP3
zoom's either.
Just out of curiosity, what dynamic-idle state where you able to achieve
on
Beagle? And what was the debug console timeout that you configured?
Regards,
Rajendra
>
>
> - Paul
>
> ---
>
> clk_autoidle_b_2.6.39
> text data bss dec hex filename
> 5530703 330544 5594520 11455767 aecd17
vmlinux.omap2plus_defconfig.orig
> 5531167 330544 5594520 11456231 aecee7
vmlinux.omap2plus_defconfig.patched
>
> Paul Walmsley (11):
> OMAP2+: clock: disable autoidle on all clocks during clock init
> OMAP2: clock: add DPLL autoidle support
> OMAP2xxx: clock: add clockfw autoidle support for APLLs
> OMAP2+: clock: comment that osc_ck/osc_sys_ck should use clockfw
autoidle control
> OMAP2+: clock: add interface clock type code with autoidle support
> OMAP2420: clock: add sdrc_ick
> OMAP2420: clock: use autoidle clkops for all autoidle-controllable
interface clocks
> OMAP2430/3xxx: clock: add modem clock autoidle support
> OMAP2430: clock: use autoidle clkops for all autoidle-controllable
interface clocks
> OMAP3: clock: use autoidle clkops for all autoidle-controllable
interface clocks
> OMAP2/3: PM: remove manual CM_AUTOIDLE bit setting in
mach-omap2/pm*xx.c
>
>
> arch/arm/mach-omap2/Makefile | 7 +
> arch/arm/mach-omap2/clkt2xxx_apll.c | 24 +++++
> arch/arm/mach-omap2/clkt2xxx_dpll.c | 63 +++++++++++++
> arch/arm/mach-omap2/clkt2xxx_osc.c | 14 +++
> arch/arm/mach-omap2/clkt_iclk.c | 82 +++++++++++++++++
> arch/arm/mach-omap2/clock.h | 11 ++
> arch/arm/mach-omap2/clock2420_data.c | 130
+++++++++++++++++-----------
> arch/arm/mach-omap2/clock2430_data.c | 130
++++++++++++++++------------
> arch/arm/mach-omap2/clock34xx.c | 29 ++++++
> arch/arm/mach-omap2/clock34xx.h | 5 +
> arch/arm/mach-omap2/clock3517.c | 4 +
> arch/arm/mach-omap2/clock3xxx.c | 3 -
> arch/arm/mach-omap2/clock3xxx_data.c | 155
+++++++++++++++++----------------
> arch/arm/mach-omap2/clock44xx_data.c | 3 +
> arch/arm/mach-omap2/cm-regbits-24xx.h | 3 +
> arch/arm/mach-omap2/cm2xxx_3xxx.c | 69 +++++++++++++++
> arch/arm/mach-omap2/cm2xxx_3xxx.h | 8 ++
> arch/arm/mach-omap2/pm24xx.c | 69 +--------------
> arch/arm/mach-omap2/pm34xx.c | 105 ----------------------
> 19 files changed, 557 insertions(+), 357 deletions(-)
> create mode 100644 arch/arm/mach-omap2/clkt2xxx_dpll.c
> create mode 100644 arch/arm/mach-omap2/clkt_iclk.c
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2011-02-16 11:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:52 [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx Paul Walmsley
2011-02-16 6:52 ` [PATCH 01/11] OMAP2+: clock: disable autoidle on all clocks during clock init Paul Walmsley
2011-02-16 6:52 ` [PATCH 02/11] OMAP2: clock: add DPLL autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 03/11] OMAP2xxx: clock: add clockfw autoidle support for APLLs Paul Walmsley
2011-02-16 6:52 ` [PATCH 04/11] OMAP2+: clock: comment that osc_ck/osc_sys_ck should use clockfw autoidle control Paul Walmsley
2011-02-16 6:52 ` [PATCH 05/11] OMAP2+: clock: add interface clock type code with autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 06/11] OMAP2420: clock: add sdrc_ick Paul Walmsley
2011-02-16 6:52 ` [PATCH 07/11] OMAP2420: clock: use autoidle clkops for all autoidle-controllable interface clocks Paul Walmsley
2011-02-16 6:52 ` [PATCH 08/11] OMAP2430/3xxx: clock: add modem clock autoidle support Paul Walmsley
2011-02-16 6:52 ` [PATCH 09/11] OMAP2430: clock: use autoidle clkops for all autoidle-controllable interface clocks Paul Walmsley
2011-02-16 6:52 ` [PATCH 10/11] OMAP3: " Paul Walmsley
2011-02-16 6:52 ` [PATCH 11/11] OMAP2/3: PM: remove manual CM_AUTOIDLE bit setting in mach-omap2/pm*xx.c Paul Walmsley
2011-02-16 9:37 ` [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx Rajendra Nayak
2011-02-16 22:14 ` Paul Walmsley
2011-02-18 5:33 ` Rajendra Nayak
2011-02-16 11:15 ` Rajendra Nayak [this message]
2011-02-16 23:05 ` Paul Walmsley
2011-02-18 5:35 ` Rajendra Nayak
2011-03-01 20:58 ` Kevin Hilman
2011-03-08 3:06 ` Paul Walmsley
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=43af56d25809fa616f0e17d7e641ebc0@mail.gmail.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).