On Mon, Mar 14, 2016 at 12:46:41PM +0100, Maxime Ripard wrote: > On Fri, Mar 11, 2016 at 04:48:26PM +0530, Vinod Koul wrote: > > > > But this nees to be property for clients and not driver. Client can then > > > > program these > > > > > > Yes, totally. The question here is how the clients give that > > > information to the driver. > > > > For this part am not worried. If we can generalize this then we add to > > dma_slave_config. Otherwise an exported symbol from driver should be fine. > > It's actually what we would like to avoid. > > We have two potential provider driver that would need such an > interface, and we have customer drivers that would be able to use any > of these two, depending on which SoCs we're talking about. > > Maintaining some logic in each and every driver in that case to know > which one of this symbol is to be called seems counterproductive and > painful. You didn't specify which one you want to avoid, and my guess is latter choice and not former :) As I said, if it's something we can use in few examples and describe generically I do not mind adding to dma_slave_config -- ~Vinod
Attachment:
signature.asc
Description: Digital signature
