On Thu, Nov 19, 2009 at 01:09:23PM +0100, Marek Szyprowski wrote: > On Thursday, November 19, 2009 12:49 PM Mark Brown wrote: > > My suggestion was to push this logic down into the clock API so the > > serial driver just requests a rate and then clock API picks the best > > option from the mux. As well as being nicer from the clock API point of > What if a device does not operate properly when clocked from one of the > available clock sources (lets say machine specific problem)? There must > be a way of setting which clock(s) should not be considered when calculating > best choice for particular device. Have the machine driver tell the clock API about this - that's what I was suggesting originally before I realised there was the mux managment logic in there. -- 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
 |