linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/5] dmaengine: sun6i: Add 4 as a possible burst value for the H3
Date: Tue, 29 Mar 2016 08:46:50 +0200	[thread overview]
Message-ID: <20160329064650.GG30977@lukather> (raw)
In-Reply-To: <20160321093533.c91912e9ac263d9c003355e2@free.fr>

On Mon, Mar 21, 2016 at 09:35:33AM +0100, Jean-Francois Moine wrote:
> On Mon, 21 Mar 2016 08:29:18 +0100
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> 
> > > @@ -470,6 +473,10 @@ static int set_config(struct sun6i_dma_dev *sdev,
> > >  {
> > >  	s8 src_width, dst_width, src_burst, dst_burst;
> > >  
> > > +	if (!sdev->cfg->burst_4 &&
> > > +	    (sconfig->src_maxburst == 4 || sconfig->dst_maxburst == 4))
> > > +		return -EINVAL;
> > > +
> > 
> > I still believe this should be dealt with at the framework level.
> 
> What do you mean? In the DMA clients?

No, in the dmaengine framework.

A driver should register the burst size they support, and
dmaengine_slave_config would reject any invalid burst size based on
that.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160329/3d482454/attachment-0001.sig>

  reply	other threads:[~2016-03-29  6:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 14:32 [PATCH v3 0/5] dmaengine: sun6i: Upgrade for audio transfers Jean-Francois Moine
2016-03-18 11:50 ` [PATCH v3 1/5] dmaengine: sun6i: Simplify and fix lli setting Jean-Francois Moine
2016-03-21  7:27   ` Maxime Ripard
2016-03-18 14:12 ` [PATCH v3 2/5] dmaengine: sun6i: Add 4 as a possible burst value for the H3 Jean-Francois Moine
2016-03-21  7:29   ` Maxime Ripard
2016-03-21  8:35     ` Jean-Francois Moine
2016-03-29  6:46       ` Maxime Ripard [this message]
2016-03-29  9:03         ` Jean-Francois Moine
2016-03-18 14:18 ` [PATCH v3 3/5] dmaengine: sun6i: Add cyclic capability Jean-Francois Moine
2016-03-21  7:33   ` Maxime Ripard
2016-03-18 14:21 ` [PATCH v3 4/5] dmaengine: sun6i: Simplify some macros Jean-Francois Moine
2016-03-21  7:48   ` Maxime Ripard
2016-03-21 14:40     ` Jean-Francois Moine
2016-03-18 14:25 ` [PATCH v3 5/5] dmaengine: sun6i: Compact a bit some config constants Jean-Francois Moine

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=20160329064650.GG30977@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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).