Dear Santosh Shilimkar, On Mon, 21 Apr 2014 09:35:25 -0400, Santosh Shilimkar wrote: > > In mach-mvebu, what we do is that we register a bus notifier on the > > platform bus, so that we can set our custom DMA operations for all > > platform devices in the system. Should this be done in a different way > > after your series? > > > Nope. Since you have a very custom SOC specific case, you can continue > what you are doing. True, but as you said, the goal is to remove machine code. So instead of having just a 'dma-coherent' property, shouldn't we have a dma-method property, which could be dma-method = "coherent" or dma-method = "marvell,io-coherent" and therefore allow the DT binding to cover more use cases than just the default non-coherent and coherent DMA operations? Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
