On Wed, Apr 22, 2015 at 10:18 AM, Ulf Hansson <[email protected]> wrote:
>> The MMCIF driver shouldn't need to be aware of the possible values supported
>> by the CPG driver.
>>
>> Can't you loop over all MMC dividers, and
>> 1. calculate the needed parent clock rate for that MMC divider,
>> 2. use clk_set_rate_range()[*] to find a (close) parent clock rate,
>> 3. calculate the effective clock rate based on MMC divider and parent
>> clock rate.
>> and use the best effective clock rate found?
>>
>> [*] It's a pity the clk API doesn't seem to have a function to query or check
>> clock rates without actually setting them. Or am I missing something?
>
> What about clk_round_rate(), can't that be used?
Thanks, I knew there had to be something, but couldn't find it at first sight.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
