From: Mark Rutland <mark.rutland@arm.com>
To: Alexander Popov <a13xp0p0v88@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Arnd Bergmann <arnd@arndb.de>, Vinod Koul <vinod.koul@intel.com>,
Gerhard Sittig <gsi@denx.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Anatolij Gustschin <agust@denx.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 1/3] dmaengine: mpc512x: add device tree binding document
Date: Fri, 4 Jul 2014 18:04:44 +0100 [thread overview]
Message-ID: <20140704170444.GE7106@leverpostej> (raw)
In-Reply-To: <CAF0T0X5LPRtm6_Q5i0ncpA3NTWckYUwqXgBxGn5ydPMq40VHBQ@mail.gmail.com>
Hi Alexander,
Apologies for the late reply. DT-related email is somewhat a firehose
and unfortunately I lose track of things.
On Thu, Jun 19, 2014 at 02:59:19PM +0100, Alexander Popov wrote:
> 2014-06-18 18:56 GMT+04:00 Alexander Popov <a13xp0p0v88@gmail.com>:
> > 2014-06-18 17:37 GMT+04:00 Mark Rutland <mark.rutland@arm.com>:
> >> On Wed, Jun 18, 2014 at 11:48:10AM +0100, Alexander Popov wrote:
> >>> Introduce a device tree binding document for the MPC512x DMA controller
> >>> +Optional properties:
> >>> +- #dma-cells: the length of the DMA specifier, must be <1>.
> >>> + Each channel of this DMA controller has a peripheral request line,
> >>> + the assignment is fixed in hardware. This one cell
> >>> + in dmas property of a client device represents the channel number.
> >>
> >> Surely this is required to be able to refer to DMA channels on the
> >> device?
> >
> > Excuse me, I didn't understand your question.
> > Do you inquire about the reason of making #dma-cells an optional property?
> > It's optional because device tree based lookup support is made
> > optional (part 3/3).
>
> Mark, did I answer your question?
> Should I fix anything in this patch series?
I would move it under required properties even if we happen to not use
it in certain edge cases.
Moving forwards everything should be DT-driven, so it'll be necessary.
Thanks,
Mark.
next prev parent reply other threads:[~2014-07-04 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 10:48 [PATCH v2 0/3] dmaengine: mpc512x: add device tree binding document and DMA channel lookup Alexander Popov
2014-06-18 10:48 ` [PATCH v2 1/3] dmaengine: mpc512x: add device tree binding document Alexander Popov
2014-06-18 13:37 ` Mark Rutland
2014-06-18 14:56 ` Alexander Popov
2014-06-19 13:59 ` Alexander Popov
2014-07-04 17:04 ` Mark Rutland [this message]
2014-06-18 10:48 ` [PATCH v2 2/3] dmaengine: of: add common xlate function for matching by channel id Alexander Popov
2014-06-18 10:48 ` [PATCH v2 3/3] dmaengine: mpc512x: register for device tree channel lookup 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=20140704170444.GE7106@leverpostej \
--to=mark.rutland@arm.com \
--cc=a13xp0p0v88@gmail.com \
--cc=agust@denx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gsi@denx.de \
--cc=lars@metafoo.de \
--cc=linuxppc-dev@lists.ozlabs.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).