clock framework: Don't disable a clock already enabled by boot loader?

Shawn Guo shawn.guo at linaro.org
Sat May 25 07:17:49 EDT 2013


On Sat, May 25, 2013 at 09:16:44AM +0200, Dirk Behme wrote:
> Yes, I know ;) But this is slightly different: In the end it
> disables the complete clk_disable_unused() call, i.e. for all unused
> clocks.
> 
> I'd like to set the flag CLK_IGNORE_UNUSED for just one clock. I.e.
> I want to set a flag for an i.MX6 clock, and I want to set it only
> for one clock.
> 
> What's the preferred way to do this?

I do not like the idea to set CLK_IGNORE_UNUSED in clock driver on clk
basis.  If the clk is needed by some driver, why cannot the driver
enable it using clk API?  Or if the clk is some fundamental one that
does not clearly belong to particular IP block and no driver wants to
manage it, we may want to not implement it in clock driver at all and
just leave it to bootloader to set it up for once.

Shawn




More information about the linux-arm-kernel mailing list