From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/13] OMAP: clock: cleanup series for 2.6.34
Date: Mon, 15 Feb 2010 17:55:32 -0700 (MST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002151754570.28188@utopia.booyaka.com> (raw)
In-Reply-To: <20100211181236.795.56094.stgit@localhost.localdomain>
On Thu, 11 Feb 2010, Paul Walmsley wrote:
> this series, targeted for 2.6.34,
>
> - fixes several OMAP clock bugs,
>
> - removes several unnecessary clock structure fields and clock flags,
>
> - splits the OMAP2420 and OMAP2430 clock trees in preparation for
> multi-OMAP 2 kernels,
>
> - and modularizes the OMAP3 chip family-specific clock code so
> some code and data that is not applicable to a targeted build
> can be elided during compilation.
>
> The series has been boot-tested on the OMAP2430 SDP. Further testing
> is now being undertaken on OMAP5912 OSK, N800 and OMAP3530 Beagle.
This series worked on N800 and Overo after minor changes to two of the
patches - to follow shortly.
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/13] OMAP: clock: cleanup series for 2.6.34
Date: Mon, 15 Feb 2010 17:55:32 -0700 (MST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002151754570.28188@utopia.booyaka.com> (raw)
In-Reply-To: <20100211181236.795.56094.stgit@localhost.localdomain>
On Thu, 11 Feb 2010, Paul Walmsley wrote:
> this series, targeted for 2.6.34,
>
> - fixes several OMAP clock bugs,
>
> - removes several unnecessary clock structure fields and clock flags,
>
> - splits the OMAP2420 and OMAP2430 clock trees in preparation for
> multi-OMAP 2 kernels,
>
> - and modularizes the OMAP3 chip family-specific clock code so
> some code and data that is not applicable to a targeted build
> can be elided during compilation.
>
> The series has been boot-tested on the OMAP2430 SDP. Further testing
> is now being undertaken on OMAP5912 OSK, N800 and OMAP3530 Beagle.
This series worked on N800 and Overo after minor changes to two of the
patches - to follow shortly.
- Paul
next prev parent reply other threads:[~2010-02-16 0:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 18:16 [PATCH 00/13] OMAP: clock: cleanup series for 2.6.34 Paul Walmsley
2010-02-11 18:16 ` Paul Walmsley
2010-02-11 18:16 ` [PATCH 01/13] OMAP2/3/4 clock: fix DPLL multiplier value errors; also copyrights, includes, documentation Paul Walmsley
2010-02-11 18:16 ` Paul Walmsley
2010-02-11 18:16 ` [PATCH 02/13] OMAP4 clock: drop the CLOCK_IN_OMAP4430 clock flag Paul Walmsley
2010-02-11 18:16 ` Paul Walmsley
2010-02-11 18:16 ` [PATCH 03/13] OMAP2xxx clock: GFX functional clock rates are not independently changeable Paul Walmsley
2010-02-11 18:16 ` Paul Walmsley
2010-02-11 18:16 ` [PATCH 04/13] OMAP2xxx clock: drop DELAYED_APP flag from non-clksel clocks Paul Walmsley
2010-02-11 18:16 ` Paul Walmsley
2010-02-11 18:17 ` [PATCH 05/13] OMAP2 clock: drop CONFIG_PARTICIPANT clock flag Paul Walmsley
2010-02-11 18:17 ` Paul Walmsley
2010-02-11 18:17 ` [PATCH 06/13] OMAP clock: compress clock flags down to a u8 Paul Walmsley
2010-02-11 18:17 ` Paul Walmsley
2010-02-11 18:17 ` [PATCH 07/13] OMAP clock: drop .id field; ensure each clock has a unique name Paul Walmsley
2010-02-11 18:17 ` Paul Walmsley
2010-02-11 18:17 ` [PATCH 08/13] OMAP3/4 clock: split into per-chip family files Paul Walmsley
2010-02-11 18:17 ` Paul Walmsley
2010-02-16 0:58 ` [PATCH v2 " Paul Walmsley
2010-02-16 0:58 ` Paul Walmsley
2010-02-16 19:23 ` Tony Lindgren
2010-02-16 19:23 ` Tony Lindgren
2010-02-16 21:54 ` Paul Walmsley
2010-02-16 21:54 ` Paul Walmsley
2010-02-16 23:11 ` Russell King - ARM Linux
2010-02-16 23:11 ` Russell King - ARM Linux
2010-02-16 23:47 ` Tony Lindgren
2010-02-16 23:47 ` Tony Lindgren
2010-02-16 23:48 ` Paul Walmsley
2010-02-16 23:48 ` Paul Walmsley
2010-02-11 18:17 ` [PATCH 09/13] OMAP2 clock: split OMAP2420, OMAP2430 clock data into their own files Paul Walmsley
2010-02-11 18:17 ` Paul Walmsley
2010-02-11 18:18 ` [PATCH 10/13] OMAP2430 clock: make func_96m_ck parent-selectable Paul Walmsley
2010-02-11 18:18 ` Paul Walmsley
2010-02-11 18:18 ` [PATCH 11/13] OMAP2 clock: drop DELAYED_APP clock flag Paul Walmsley
2010-02-11 18:18 ` Paul Walmsley
2010-02-11 18:18 ` [PATCH 12/13] OMAP clock: drop RATE_FIXED " Paul Walmsley
2010-02-11 18:18 ` Paul Walmsley
2010-02-16 1:02 ` [PATCH v2 " Paul Walmsley
2010-02-16 1:02 ` Paul Walmsley
2010-02-11 18:18 ` [PATCH 13/13] OMAP4 clock: drop the ALWAYS_ENABLED " Paul Walmsley
2010-02-11 18:18 ` Paul Walmsley
2010-02-16 0:55 ` Paul Walmsley [this message]
2010-02-16 0:55 ` [PATCH 00/13] OMAP: clock: cleanup series for 2.6.34 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=alpine.DEB.2.00.1002151754570.28188@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.