From: Arnd Bergmann <arnd@arndb.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@codeaurora.org>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding
Date: Tue, 28 Jan 2014 13:05:10 +0100 [thread overview]
Message-ID: <4916428.f0GtxdkWKj@wuerfel> (raw)
In-Reply-To: <20140128113242.GJ10628@intel.com>
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
> On Tue, Jan 28, 2014 at 11:17:57AM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
> > > On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
> > > > Why does the direction needs to be specified in specifier? I see two
> > > > options, either the direction per is fixed in hardware. In that case the DMA
> > > > controller node should describe which channel is which direction. Or the
> > > > direction is not fixed in hardware and can be changed at runtime in which
> > > > case it should be set on a per descriptor basis.
> > >
> > > Normally the direction is implied by dmaengine_slave_config().
> >
> > No. The direction argument in there is deprecated - we've been talking
> > about removing it for some time.
> >
> > DMA engine drivers should store all parameters of the configuration, and
> > then select the appropriate ones when preparing a transfer (which itself
> > involves a direction.)
>
> Right all the prep_ calls for slave cases have explcit direction argument so
> sending it using slave config makes no sense. So will remove it after the merge
> window closes and fix
Ok, thanks for clearing up my mistake. However, the argument remains:
the direction doesn't need to be in the DT DMA descriptor since it
gets set by software anyway.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding
Date: Tue, 28 Jan 2014 13:05:10 +0100 [thread overview]
Message-ID: <4916428.f0GtxdkWKj@wuerfel> (raw)
In-Reply-To: <20140128113242.GJ10628@intel.com>
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
> On Tue, Jan 28, 2014 at 11:17:57AM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
> > > On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
> > > > Why does the direction needs to be specified in specifier? I see two
> > > > options, either the direction per is fixed in hardware. In that case the DMA
> > > > controller node should describe which channel is which direction. Or the
> > > > direction is not fixed in hardware and can be changed at runtime in which
> > > > case it should be set on a per descriptor basis.
> > >
> > > Normally the direction is implied by dmaengine_slave_config().
> >
> > No. The direction argument in there is deprecated - we've been talking
> > about removing it for some time.
> >
> > DMA engine drivers should store all parameters of the configuration, and
> > then select the appropriate ones when preparing a transfer (which itself
> > involves a direction.)
>
> Right all the prep_ calls for slave cases have explcit direction argument so
> sending it using slave config makes no sense. So will remove it after the merge
> window closes and fix
Ok, thanks for clearing up my mistake. However, the argument remains:
the direction doesn't need to be in the DT DMA descriptor since it
gets set by software anyway.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Lars-Peter Clausen <lars@metafoo.de>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Andy Gross <agross@codeaurora.org>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding
Date: Tue, 28 Jan 2014 13:05:10 +0100 [thread overview]
Message-ID: <4916428.f0GtxdkWKj@wuerfel> (raw)
In-Reply-To: <20140128113242.GJ10628@intel.com>
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
> On Tue, Jan 28, 2014 at 11:17:57AM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
> > > On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
> > > > Why does the direction needs to be specified in specifier? I see two
> > > > options, either the direction per is fixed in hardware. In that case the DMA
> > > > controller node should describe which channel is which direction. Or the
> > > > direction is not fixed in hardware and can be changed at runtime in which
> > > > case it should be set on a per descriptor basis.
> > >
> > > Normally the direction is implied by dmaengine_slave_config().
> >
> > No. The direction argument in there is deprecated - we've been talking
> > about removing it for some time.
> >
> > DMA engine drivers should store all parameters of the configuration, and
> > then select the appropriate ones when preparing a transfer (which itself
> > involves a direction.)
>
> Right all the prep_ calls for slave cases have explcit direction argument so
> sending it using slave config makes no sense. So will remove it after the merge
> window closes and fix
Ok, thanks for clearing up my mistake. However, the argument remains:
the direction doesn't need to be in the DT DMA descriptor since it
gets set by software anyway.
Arnd
next prev parent reply other threads:[~2014-01-28 12:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 6:27 [Patch v3 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
2014-01-28 6:27 ` Andy Gross
2014-01-28 6:27 ` [Patch v3 1/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-01-28 6:27 ` Andy Gross
2014-01-28 6:27 ` [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-01-28 6:27 ` Andy Gross
2014-01-28 9:05 ` Lars-Peter Clausen
2014-01-28 9:05 ` Lars-Peter Clausen
2014-01-28 9:16 ` Arnd Bergmann
2014-01-28 9:16 ` Arnd Bergmann
2014-01-28 11:17 ` Russell King - ARM Linux
2014-01-28 11:17 ` Russell King - ARM Linux
2014-01-28 11:32 ` Vinod Koul
2014-01-28 11:32 ` Vinod Koul
2014-01-28 12:05 ` Arnd Bergmann [this message]
2014-01-28 12:05 ` Arnd Bergmann
2014-01-28 12:05 ` Arnd Bergmann
2014-01-28 12:08 ` Arnd Bergmann
2014-01-28 12:08 ` Arnd Bergmann
2014-01-28 12:08 ` Arnd Bergmann
2014-01-28 12:16 ` Russell King - ARM Linux
2014-01-28 12:16 ` Russell King - ARM Linux
2014-01-29 15:05 ` Arnd Bergmann
2014-01-29 15:05 ` Arnd Bergmann
2014-01-28 13:01 ` Russell King - ARM Linux
2014-01-28 13:01 ` Russell King - ARM Linux
2014-01-28 19:50 ` Andy Gross
2014-01-28 19:50 ` Andy Gross
2014-01-28 19:50 ` Andy Gross
2014-01-30 6:23 ` Andy Gross
2014-01-30 6:23 ` Andy Gross
2014-01-28 19:47 ` Andy Gross
2014-01-28 19:47 ` Andy Gross
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=4916428.f0GtxdkWKj@wuerfel \
--to=arnd@arndb.de \
--cc=agross@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=vinod.koul@intel.com \
/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.