On Tue, Aug 23, 2011 at 9:48 AM, Rajendra Nayak <rna...@ti.com> wrote: > On 8/23/2011 5:28 AM, Kevin Hilman wrote: >> >> Rajendra Nayak<rna...@ti.com> writes: >> >> [...] >> >>> FWIK, its a one time requirement to set the clock rate to the >>> right rate the device can operate in based on what a platform >>> supports. >> >> Except $SUBJECT patch hard-codes the clock rate for all platforms in the >> driver. > > The device has a requirement to operate in a 1Mhz to 2Mhz range. So the > driver is using a clk_round_rate() to get the closest rate supported and > sets it using a clk_set_rate(). > >> >> If the clock rate is to be platform-specific, it should be done in >> platform-specific code. > > I am fine if this needs to be moved to platform-specific code, but I > wasn't quite sure this needs to be done in clock framework as was > suggested.
The range can be (ex: 1MHz to 2Mhz) can be sent via pdata as max and min frequencies and the driver can round the rate to get the appropriate rate inside the specified range? Is this approach Fine? > >> >> Kevin > > -- Regards and Thanks, Keerthy -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
