On Tue, Feb 02, 2016 at 09:47:12AM +0100, Maxime Ripard wrote: > The current clock registration and protection code has a few drawbacks, the > two main ones being that we create a lot of orphans clock in the > registration phase, which will be troublesome when we will start being less > relaxed about them. > > The protection code also relies on clkdev, which we don't really use but > for this particular case. > > Fix both at the same time by moving everyone to the CLK_OF_DECLARE that > will probe our clock tree in the right and thus avoid orphans, and by > protecting directly the clock returned by our registration function. > > Signed-off-by: Maxime Ripard Fixed the issue reported by Andre, and applied. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com