Re: [PATCH 2/7] clk: tegra: Use common of_clk_init() function

From: Stephen Warren <swarren@wwwdotorg.org>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: mturquette@linaro.org, swarren@nvidia.com,
	grant.likely@secretlab.ca, linus.walleij@linaro.org,
	rob.herring@calxeda.com, maxime.ripard@free-electrons.com,
	linux@prisktech.co.nz, josh.cartwright@ni.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/7] clk: tegra: Use common of_clk_init() function
Date: Fri, 04 Jan 2013 09:30:32 -0700	[thread overview]
Message-ID: <50E703A8.1080808@wwwdotorg.org> (raw)
In-Reply-To: <1357282858-2112-2-git-send-email-pgaikwad@nvidia.com>

On 01/04/2013 12:00 AM, Prashant Gaikwad wrote:
> Use common of_clk_init() function for clocks initialization.

>  drivers/clk/tegra/clk-tegra20.c |    3 ++-
>  drivers/clk/tegra/clk-tegra30.c |    3 ++-

Oh, so this series is written assuming that the Tegra CCF rework is
already applied then? That makes the dependencies quite painful, since I
think we'll end up with the following order being needed:

1) clk: Add composite clock type
   -> This would usually go through the clk tree.
2) The Tegra CCF rework series
   -> This must go through the Tegra tree due to lots of dependencies
   and merge conflicts with other Tegra patches.
3) This series
   -> This would usually go through the clk tree.

Is it possible to re-order the dependencies as (1) (3) (2), so that Mike
can apply (1) and (3) to the clock tree, then I can use the clk tree as
the basis for a branch in the Tegra tree to apply (2) and all the other
Tegra patches that will conflict with (2)?