[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160316032213.GP13211@localhost>
Date: Wed, 16 Mar 2016 08:52:13 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Boris Brezillon <boris.brezillon@...e-electrons.com>,
Dan Williams <dan.j.williams@...el.com>,
dmaengine@...r.kernel.org, Chen-Yu Tsai <wens@...e.org>,
linux-sunxi@...glegroups.com,
Emilio López <emilio@...pez.com.ar>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dma: sun4i: expose block size and wait cycle
configuration to DMA users
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
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists