Quoting Afzal Mohammed (2013-01-23 03:38:52) > Some of clocks can have a limit on minimum divider value that can be > programmed, prepare for such a support. > > Add a new field min_div for the basic divider clock and a new dynamic > clock divider registration function where minimum divider value can > be specified. Keep behaviour of existing divider clock registration > functions, static initialization helpers as was earlier. > > Signed-off-by: Afzal Mohammed <afzal@xxxxxx> Hi Afzal, I'd like to understand this a bit better. At first the need for a minimum divider makes a lot of sense, but I want to make sure it gets designed correctly. My first question is whether the minimum divider you plan to use is an actual constraint of the hardware (e.g. the clock controller ip only lets program two bits which divide by 4, 5, 6 or 7, where 4 is the minimum divider) or if this is a functional constraint (e.g. the clock hardware can divide by a lower value, but you never want that since it results in non-functional video/audio/whatever). If this is more of a functional constraint then perhaps a new api like clk_set_min_rate makes more sense. Secondly, have you looked into using the rate-table option provided by the basic divider clock? Can you explain how this is not a good fit for your needs? Perhaps there are too many divisor values so the table would be large? Thanks, Mike -- 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
