From: Vinod Koul <vinod.koul@intel.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Dan Williams" <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, "Chen-Yu Tsai" <wens@csie.org>,
linux-sunxi@googlegroups.com,
"Emilio López" <emilio@elopez.com.ar>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users
Date: Wed, 16 Mar 2016 08:52:13 +0530 [thread overview]
Message-ID: <20160316032213.GP13211@localhost> (raw)
In-Reply-To: <20160314114641.GC30977@lukather>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-16 3:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 9:59 [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon
2016-03-07 14:54 ` Vinod Koul
2016-03-07 15:08 ` Boris Brezillon
2016-03-07 20:30 ` Maxime Ripard
2016-03-08 2:55 ` Vinod Koul
2016-03-08 2:59 ` Vinod Koul
2016-03-08 7:51 ` Maxime Ripard
2016-03-08 8:42 ` [linux-sunxi] " Hans de Goede
2016-03-08 10:05 ` Vinod Koul
2016-03-09 10:58 ` Maxime Ripard
2016-03-08 8:46 ` Boris Brezillon
2016-03-08 9:10 ` [linux-sunxi] " Priit Laes
2016-03-08 10:04 ` Vinod Koul
2016-03-09 10:08 ` [linux-sunxi] " LABBE Corentin
2016-03-08 9:59 ` Vinod Koul
2016-03-09 10:14 ` Boris Brezillon
2016-03-11 6:24 ` Vinod Koul
2016-03-11 9:40 ` Boris Brezillon
2016-03-11 10:06 ` Vinod Koul
2016-03-11 10:26 ` Boris Brezillon
2016-03-11 11:21 ` Vinod Koul
2016-03-09 11:06 ` Boris Brezillon
2016-03-11 6:26 ` Vinod Koul
2016-03-11 9:45 ` Boris Brezillon
2016-03-11 10:09 ` Vinod Koul
2016-03-11 10:55 ` Maxime Ripard
2016-03-11 11:18 ` Vinod Koul
2016-03-14 11:46 ` Maxime Ripard
2016-03-16 3:22 ` Vinod Koul [this message]
2016-03-07 15:30 ` [linux-sunxi] " Priit Laes
2016-03-07 15:47 ` Boris Brezillon
2016-03-07 17:15 ` Emilio López
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160316032213.GP13211@localhost \
--to=vinod.koul@intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).