From: Alexander Popov <alex.popov@linux.com>
To: Timur Tabi <timur@tabi.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Anatolij Gustschin <agust@denx.de>, Gerhard Sittig <gsi@denx.de>,
Rob Herring <robh@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Dan Williams <dan.j.williams@intel.com>,
Vinod Koul <vinod.koul@intel.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linuxppc-dev@lists.ozlabs.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] powerpc/512x: add a device tree binding for LocalPlus Bus FIFO
Date: Mon, 28 Sep 2015 16:24:25 +0300 [thread overview]
Message-ID: <56093F89.1020004@linux.com> (raw)
In-Reply-To: <560492C1.307@tabi.org>
On 25.09.2015 03:18, Timur Tabi wrote:
> Alexander Popov wrote:
>> +- dma-names: should be "rx-tx";
>
> Why bother, if it can only be one value?
I've just followed devicetree/bindings/dma/dma.txt...
This "rx-tx" doesn't mean much but it could show that LocalPlus Bus FIFO
uses a single DMA read-write channel. Should I really drop it?
Best regards,
Alexander
next prev parent reply other threads:[~2015-09-28 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 17:28 [PATCH v3 0/3] powerpc/512x: add LocalPlus Bus FIFO device driver Alexander Popov
2015-09-24 17:28 ` [PATCH v3 1/3] " Alexander Popov
[not found] ` <1443115737-3948-2-git-send-email-alex.popov-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2015-09-25 1:01 ` Timur Tabi
[not found] ` <56049CD0.7080104-N01EOCouUvQ@public.gmane.org>
2015-09-28 13:13 ` Alexander Popov
[not found] ` <56093CE5.5070301-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2015-09-28 13:18 ` Timur Tabi
[not found] ` <56093E1D.4080008-N01EOCouUvQ@public.gmane.org>
2015-09-29 6:34 ` Alexander Popov
2015-09-30 21:24 ` Alexander Popov
[not found] ` <560C5325.6070406-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2015-10-01 17:11 ` Timur Tabi
2015-10-05 22:22 ` Alexander Popov
2015-09-24 17:28 ` [PATCH v3 2/3] powerpc/512x: add a device tree binding for LocalPlus Bus FIFO Alexander Popov
2015-09-25 0:18 ` Timur Tabi
2015-09-28 13:24 ` Alexander Popov [this message]
[not found] ` <56093F89.1020004-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2015-09-28 13:26 ` Timur Tabi
[not found] ` <5609401F.3010603-N01EOCouUvQ@public.gmane.org>
2015-09-29 6:35 ` Alexander Popov
2015-09-24 17:28 ` [PATCH v3 3/3] dmaengine: mpc512x: initialize with subsys_initcall() Alexander Popov
2015-09-25 0:16 ` Timur Tabi
2015-09-28 13:15 ` Alexander Popov
[not found] ` <1443115737-3948-4-git-send-email-alex.popov-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2015-10-07 14:17 ` Vinod Koul
2015-10-07 21:31 ` Alexander Popov
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=56093F89.1020004@linux.com \
--to=alex.popov@linux.com \
--cc=agust@denx.de \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gsi@denx.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.org \
--cc=timur@tabi.org \
--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 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).