From: pgaikwad@nvidia.com (Prashant G)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: tegra: Port tegra to generic clock framework
Date: Thu, 28 Jun 2012 22:59:49 +0530 [thread overview]
Message-ID: <4FEC948D.9080606@nvidia.com> (raw)
In-Reply-To: <1340879846-12900-6-git-send-email-pgaikwad@nvidia.com>
This patch is not delivered to all mailing lists reason being the
message body too big.
It can be viewed at https://lkml.org/lkml/2012/6/28/158
Thanks & Regards,
Prashant G
On Thursday 28 June 2012 04:07 PM, Prashant Gaikwad wrote:
> This patch converts tegra clock code to generic clock framework in following way:
> - Implement clk_ops as required by generic clk framework. (tegraXX_clocks.c)
> - Use platform specific struct clk_tegra in clk_ops implementation instead of struct clk.
> - Initialize all clock data statically. (tegraXX_clocks_data.c)
>
> Legacy framework did not have recalc_rate and is_enabled functions. Implemented these functions.
> Removed init function. It's functionality is splitted into recalc_rate and is_enabled.
>
> Static initialization is used since slab is not up in .init_early and clock
> is needed to be initialized before clockevent/clocksource initialization.
> Macros redefined for clk_tegra.
>
> Also, single struct clk_tegra is used for all type of clocks (PLL, peripheral etc.). This
> is to move quickly to generic common clock framework so that other dependent features will
> not be blocked (such as DT binding).
>
> Enabling COMMON_CLOCK config moved to ARCH_TEGRA since it is enabled for both Tegra20
> and Tegra30.
>
> Signed-off-by: Prashant Gaikwad<pgaikwad@nvidia.com>
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/mach-tegra/clock.h | 1 +
> arch/arm/mach-tegra/tegra20_clocks.c | 986 +++++++++--------
> arch/arm/mach-tegra/tegra20_clocks.h | 4 +
> arch/arm/mach-tegra/tegra20_clocks_data.c | 1318 +++++++++++++----------
> arch/arm/mach-tegra/tegra30_clocks.c | 1331 +++++++++++++----------
> arch/arm/mach-tegra/tegra30_clocks.h | 14 +-
> arch/arm/mach-tegra/tegra30_clocks_data.c | 1688 ++++++++++++++++-------------
> 8 files changed, 3029 insertions(+), 2314 deletions(-)
>
>
next prev parent reply other threads:[~2012-06-28 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 10:37 [PATCH 0/6] Port Tegra to generic clk framework Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 1/6] ARM: tegra30: Separate out clk ops and clk data Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 2/6] ARM: tegra20: " Prashant Gaikwad
2012-06-28 17:37 ` Stephen Warren
2012-06-29 2:06 ` Prashant G
2012-06-28 10:37 ` [PATCH 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 4/6] ARM: tegra: Add clk_tegra structure and helper functions Prashant Gaikwad
2012-06-28 18:28 ` Mike Turquette
2012-06-29 8:34 ` Prashant Gaikwad
2012-07-03 0:09 ` Turquette, Mike
2012-07-03 1:31 ` Stephen Warren
2012-07-03 1:49 ` Turquette, Mike
2012-06-28 10:37 ` [PATCH 5/6] ARM: tegra: Port tegra to generic clock framework Prashant Gaikwad
2012-06-28 17:29 ` Prashant G [this message]
2012-06-28 10:37 ` [PATCH 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-06-28 17:39 ` [PATCH 0/6] Port Tegra to generic clk framework Stephen Warren
2012-06-29 17:24 ` Stephen Warren
2012-07-02 18:12 ` Stephen Warren
2012-07-03 11:29 ` Prashant Gaikwad
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=4FEC948D.9080606@nvidia.com \
--to=pgaikwad@nvidia.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).