On Thu, Nov 19, 2009 at 08:26:34PM +0900, jassi brar wrote: > The case here is that UART controller can source from various platform clocks > to generate the UART clocks. The drivers/serial/samsung.c chooses a source > clock that can result in closest match to the requested rate. > How could we do that from machine code(except for writing callbacks for each > machine using the SoC)? > Or maybe i cud understand better looking at some example. > Cud u suggest some please? I can't think off the top of my head of anything which does this dynamically (rather than just choosing a clock at startup time). OMAP might have something since they seem to have the most advanced of the current implementations. Off the top of my head it sounds like the muxing ought to be pushed into the clock API completely - the problem of picking the best match for the current use case isn't unique to the serial driver by any stretch of the imagination. The serial driver would then end up just seeing the output of the mux it uses, with the clock API dealing with working out which of the sources can deliver the best match. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |