On Wed, Oct 01, 2014 at 10:27:05AM +0200, Maxime Ripard wrote: > On Sat, Sep 27, 2014 at 10:28:47AM +0100, Russell King - ARM Linux wrote: > > The only way to do this is to either have a flag day, fixing all drivers > > at once (which isn't going to happen) or leave the caps code as-is, and > > provide a library function which drivers can hook into the caps callback > > which retrieves the information from dma_device. > > > > That way, DMA engine drivers which are using the new method can just > > install the new function, and those which haven't been updated with > > capabilities can carry on as they are, and are detectable to drivers. > > Which is pretty much the current behaviour, isn't it? Yes, because the ASoC code has obviously already thought about this and solved the lack-of-caps-function problem in a way that permits existing solutions to continue working. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
