All of lore.kernel.org
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users
Date: Fri, 11 Mar 2016 11:56:07 +0530	[thread overview]
Message-ID: <20160311062607.GP11154@localhost> (raw)
In-Reply-To: <20160309120627.67612b1d@bbrezillon>

On Wed, Mar 09, 2016 at 12:06:27PM +0100, Boris Brezillon wrote:
> On Tue, 8 Mar 2016 08:25:47 +0530
> Vinod Koul <vinod.koul@intel.com> wrote:
> > 
> > Why does dmaengine need to wait? Can you explain that
> 
> I don't have an answer for that one, but when I set WAIT_CYCLES to 1
> for the NAND use case it does not work. So I guess it is somehow
> related to how the DRQ line is controlled on the device side...

Is the WAIT cycle different for different usages or same for all
usages/channels?

-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: "Maxime Ripard" <maxime.ripard@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: Fri, 11 Mar 2016 11:56:07 +0530	[thread overview]
Message-ID: <20160311062607.GP11154@localhost> (raw)
In-Reply-To: <20160309120627.67612b1d@bbrezillon>

On Wed, Mar 09, 2016 at 12:06:27PM +0100, Boris Brezillon wrote:
> On Tue, 8 Mar 2016 08:25:47 +0530
> Vinod Koul <vinod.koul@intel.com> wrote:
> > 
> > Why does dmaengine need to wait? Can you explain that
> 
> I don't have an answer for that one, but when I set WAIT_CYCLES to 1
> for the NAND use case it does not work. So I guess it is somehow
> related to how the DRQ line is controlled on the device side...

Is the WAIT cycle different for different usages or same for all
usages/channels?

-- 
~Vinod

  reply	other threads:[~2016-03-11  6:26 UTC|newest]

Thread overview: 64+ 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  9:59 ` Boris Brezillon
2016-03-07 14:54 ` Vinod Koul
2016-03-07 14:54   ` Vinod Koul
2016-03-07 15:08   ` Boris Brezillon
2016-03-07 15:08     ` Boris Brezillon
2016-03-07 20:30     ` Maxime Ripard
2016-03-07 20:30       ` Maxime Ripard
2016-03-08  2:55       ` Vinod Koul
2016-03-08  2:55         ` Vinod Koul
2016-03-08  2:59         ` Vinod Koul
2016-03-08  2:59           ` Vinod Koul
2016-03-08  7:51         ` Maxime Ripard
2016-03-08  7:51           ` Maxime Ripard
2016-03-08  8:42           ` [linux-sunxi] " Hans de Goede
2016-03-08  8:42             ` Hans de Goede
2016-03-08 10:05             ` Vinod Koul
2016-03-08 10:05               ` Vinod Koul
2016-03-09 10:58               ` Maxime Ripard
2016-03-09 10:58                 ` Maxime Ripard
2016-03-08  8:46           ` Boris Brezillon
2016-03-08  8:46             ` Boris Brezillon
2016-03-08  9:10             ` [linux-sunxi] " Priit Laes
2016-03-08  9:10               ` Priit Laes
2016-03-08 10:04             ` Vinod Koul
2016-03-08 10:04               ` Vinod Koul
2016-03-09 10:08             ` [linux-sunxi] " LABBE Corentin
2016-03-09 10:08               ` LABBE Corentin
2016-03-08  9:59           ` Vinod Koul
2016-03-08  9:59             ` Vinod Koul
2016-03-09 10:14         ` Boris Brezillon
2016-03-09 10:14           ` Boris Brezillon
2016-03-11  6:24           ` Vinod Koul
2016-03-11  6:24             ` Vinod Koul
2016-03-11  9:40             ` Boris Brezillon
2016-03-11  9:40               ` Boris Brezillon
2016-03-11 10:06               ` Vinod Koul
2016-03-11 10:06                 ` Vinod Koul
2016-03-11 10:26                 ` Boris Brezillon
2016-03-11 10:26                   ` Boris Brezillon
2016-03-11 11:21                   ` Vinod Koul
2016-03-11 11:21                     ` Vinod Koul
2016-03-09 11:06         ` Boris Brezillon
2016-03-09 11:06           ` Boris Brezillon
2016-03-11  6:26           ` Vinod Koul [this message]
2016-03-11  6:26             ` Vinod Koul
2016-03-11  9:45             ` Boris Brezillon
2016-03-11  9:45               ` Boris Brezillon
2016-03-11 10:09               ` Vinod Koul
2016-03-11 10:09                 ` Vinod Koul
2016-03-11 10:55                 ` Maxime Ripard
2016-03-11 10:55                   ` Maxime Ripard
2016-03-11 11:18                   ` Vinod Koul
2016-03-11 11:18                     ` Vinod Koul
2016-03-14 11:46                     ` Maxime Ripard
2016-03-14 11:46                       ` Maxime Ripard
2016-03-16  3:22                       ` Vinod Koul
2016-03-16  3:22                         ` Vinod Koul
2016-03-07 15:30 ` [linux-sunxi] " Priit Laes
2016-03-07 15:30   ` Priit Laes
2016-03-07 15:47   ` Boris Brezillon
2016-03-07 15:47     ` Boris Brezillon
2016-03-07 17:15     ` Emilio López
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=20160311062607.GP11154@localhost \
    --to=vinod.koul@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.