[Question] omap3 clock framework for clock set_rate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paul,

In linux-omap clock framework, most clocks have no
set_rate in their definition in clock34xx.h, but defined
DEFAULT_RATE in clksel_rate structures, this
Will only allow some pre-set rates for some clocks and
Can not get a more flexible rates if driver wants to
Change the clock rate usng clk_set_rate.

What is the benefit of this implementation?

We want to understand this before we made the change
In case we missed some imprtant background of
This implementation.

Thanks,
Chunqiu

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux