Currently on OMAP, it is not possible to specify a clock consumer
to any of the OMAP generated clocks using the device tree. This can pose
a problem for external devices that run off an OMAP clock as we
can't reliably provide a reference to the clock in the device tree.
This patch allows device
Hi,
On Mon, Feb 11, 2013 at 05:44:23PM +0200, Roger Quadros wrote:
@@ -36,12 +39,76 @@ static struct of_device_id omap_dt_match_table[]
__initdata = {
{ }
};
+static int __init omap_create_clk_alias(struct device_node *np)
if the rest of the folks agree with the aproach, looks
On Mon, Feb 11, 2013 at 05:44:23PM +0200, Roger Quadros wrote:
Currently on OMAP, it is not possible to specify a clock consumer
to any of the OMAP generated clocks using the device tree. This can pose
a problem for external devices that run off an OMAP clock as we
can't reliably provide a
On 02/11/2013 06:07 PM, Sascha Hauer wrote:
On Mon, Feb 11, 2013 at 05:44:23PM +0200, Roger Quadros wrote:
Currently on OMAP, it is not possible to specify a clock consumer
to any of the OMAP generated clocks using the device tree. This can pose
a problem for external devices that run off an
