From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 00/12] Update OMAP2/3 powerdomains, clockdomains
Date: Fri, 12 Sep 2008 15:33:50 -0700 [thread overview]
Message-ID: <20080912223349.GI10675@atomide.com> (raw)
In-Reply-To: <20080910164631.17024.43733.stgit@localhost.localdomain>
* Paul Walmsley <paul@pwsan.com> [080910 09:51]:
> This second version adds two fixes: it removes the extraneous init
> from csi2_96m_fck, and associates virt_opp_clkdm with wkup_pwrdm.
>
> ...
>
> This series updates the in-kernel OMAP2/3 clockdomain and powerdomain
> structures:
>
> - Split the placeholder clockdomain "wkup_clkdm" into "cm_clkdm" and
> "prm_clkdm". This more accurately reflects the hardware.
>
> - Add powerdomains and clockdomains for DPLLs 1 through 5 on OMAP3.
>
> - Associate every clock in OMAP2/3 clock tree with an appropriate
> clockdomain.
>
> Boot-tested on 2430SDP and 3430SDP.
Pushed these. Sounds like we need to queue up bunch of clock and
powerdomain patches for mainline.
Tony
>
> ---
>
> size:
> text data bss dec hex filename
> 3441382 157936 105728 3705046 3888d6 vmlinux.3430sdp.orig
> 3441638 158440 105728 3705806 388bce vmlinux.3430sdp
>
> arch/arm/mach-omap2/clock.c | 8 +
> arch/arm/mach-omap2/clock24xx.h | 56 ++++++----
> arch/arm/mach-omap2/clock34xx.h | 140 ++++++++++++++++++-------
> arch/arm/mach-omap2/clockdomains.h | 65 +++++++++++-
> arch/arm/mach-omap2/powerdomains.h | 5 +
> arch/arm/mach-omap2/powerdomains34xx.h | 31 ++++++
> arch/arm/plat-omap/include/mach/powerdomain.h | 4 -
> 7 files changed, 239 insertions(+), 70 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-09-12 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 16:47 [PATCH v2 00/12] Update OMAP2/3 powerdomains, clockdomains Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 01/12] OMAP2/3 clockdomains: add CM and PRM clkdms Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 02/12] OMAP2/3 clock: convert wkup_clkdm PRM clocks to prm_clkdm Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 03/12] OMAP2/3 clock: annotate PRM clocks that are missing clockdomains Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 04/12] OMAP2/3 clock: convert wkup_clkdm CM clocks to cm_clkdm Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 05/12] OMAP2/3 clock: mark the rest of the CM clocks as belonging " Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 06/12] OMAP2/3 clockdomain: remove wkup_clkdm Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 07/12] OMAP3 PRCM: add DPLL1-5 powerdomains, clockdomains Paul Walmsley
2008-09-10 16:47 ` [PATCH v2 08/12] OMAP3 clock: mark DPLL clocks with their DPLLx clockdomains Paul Walmsley
2008-09-10 16:48 ` [PATCH v2 09/12] OMAP2/3 clock: note clockdomains for remaining clocks Paul Walmsley
2008-09-10 16:48 ` [PATCH v2 10/12] OMAP2 clockdomain: add virt_opp_clkdm Paul Walmsley
2008-09-10 16:48 ` [PATCH v2 11/12] OMAP3 clock: remove duplicate call to omap2_init_clk_clkdm() Paul Walmsley
2008-09-10 16:48 ` [PATCH v2 12/12] OMAP2/3 clock: warn if clock is missing clockdomain Paul Walmsley
2008-09-12 22:33 ` Tony Lindgren [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=20080912223349.GI10675@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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