[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130424162847.8998.73264@quantum>
Date: Wed, 24 Apr 2013 09:28:47 -0700
From: Mike Turquette <mturquette@...aro.org>
To: Nishanth Menon <nm@...com>, Tony Lindgren <tony@...mide.com>
Cc: <linux-omap@...r.kernel.org>,
<devicetree-discuss@...ts.ozlabs.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
BenoƮt Cousson <b-cousson@...com>,
Paul Walmsley <paul@...an.com>,
Kevin Hilman <khilman@...prootsystems.com>
Subject: Re: [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock
data
Quoting Nishanth Menon (2013-04-14 14:19:17)
> Overall strategy introduced here is simple: a clock node described in
> device tree blob is used to identify the exact clock provided in the
> SoC specific data. This is then linked back using of_clk_add_provider
> to the device node to be accessible by of_clk_get.
>
> Based on discussion contributions from Roger Quadros, Grygorii Strashko
> and others.
>
> Cc: Kevin Hilman <khilman@...prootsystems.com>
> Cc: Mike Turquette <mturquette@...aro.org>
> Cc: Paul Walmsley <paul@...an.com>
> [tony@...mide.com: co-developed]
> Signed-off-by: Tony Lindgren <tony@...mide.com>
> Signed-off-by: Nishanth Menon <nm@...com>
I can take this into clk-next after the merge window. Please refresh it
for -rc1 as we discussed on irc.
As an aside, will Tero's series for migrating to drivers/clk/omap[1] and
Rajendra's patch for registering clocks late[2] be refreshed after the
merge window? It would be nice to combine these efforts.
Thanks,
Mike
[1] http://article.gmane.org/gmane.linux.ports.arm.omap/95948
[2] http://www.spinics.net/lists/arm-kernel/msg231288.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists