From: Arnd Bergmann <arnd@arndb.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Vinod Koul <vinod.koul@intel.com>, Gerhard Sittig <gsi@denx.de>,
Alexander Popov <a13xp0p0v88@gmail.com>,
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 RFC v5 4/5] dma: mpc512x: register for device tree channel lookup
Date: Mon, 18 Nov 2013 15:31:54 +0100 [thread overview]
Message-ID: <201311181531.54818.arnd@arndb.de> (raw)
In-Reply-To: <20131118120957.GH30853@e106331-lin.cambridge.arm.com>
On Monday 18 November 2013, Mark Rutland wrote:
> > +++ b/Documentation/devicetree/bindings/dma/mpc512x-dma.txt
> > @@ -0,0 +1,55 @@
> > +* Freescale MPC512x DMA Controller
> > +
> > +The DMA controller in the Freescale MPC512x SoC can move blocks of
> > +memory contents between memory and peripherals or memory to memory.
> > +
> > +Refer to the "Generic DMA Controller and DMA request bindings" description
> > +in the dma.txt file for a more detailled discussion of the binding. The
> > +MPC512x DMA engine binding follows the common scheme, but doesn't provide
> > +support for the optional channels and requests counters (those values are
> > +derived from the detected hardware features) and has a fixed client
> > +specifier length of 1 integer cell (the value is the DMA channel, since
> > +the DMA controller uses a fixed assignment of request lines per channel).
>
> The fact that #dma-cells must be <1> isn't a difference from the
> standard binding, and needs not be described here. The meaning of the
> value should be in your description of #dma-cells below.
I think the value it has to be in there, and I have in the past asked other
people to add this. Note that in the generic binding, it says that it must
be "at least 1". You can have controllers that require a larger number, or
that can use 1 or 2 alternatively, depending on how the device is wired
up, e.g. when a dma controller has two master ports you would need a
second cell to specify the port number, but only if more than one port
is actually connected to a slave.
> I'm not sure it's worth mentioning optional channels / request counters.
> If anything, it would be better to update dma.txt to move the "Optional
> properties" to something like "Suggested properties"...
These are less clearly defined. In the generic binding, it's mostly a matter
of "if you need to pass this information, use these properties". The individual
binding can then make them mandatory if needed.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: Alexander Popov
<a13xp0p0v88-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Gerhard Sittig <gsi-ynQEQJNshbs@public.gmane.org>,
Dan Williams
<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org>,
"linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RFC v5 4/5] dma: mpc512x: register for device tree channel lookup
Date: Mon, 18 Nov 2013 15:31:54 +0100 [thread overview]
Message-ID: <201311181531.54818.arnd@arndb.de> (raw)
In-Reply-To: <20131118120957.GH30853-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
On Monday 18 November 2013, Mark Rutland wrote:
> > +++ b/Documentation/devicetree/bindings/dma/mpc512x-dma.txt
> > @@ -0,0 +1,55 @@
> > +* Freescale MPC512x DMA Controller
> > +
> > +The DMA controller in the Freescale MPC512x SoC can move blocks of
> > +memory contents between memory and peripherals or memory to memory.
> > +
> > +Refer to the "Generic DMA Controller and DMA request bindings" description
> > +in the dma.txt file for a more detailled discussion of the binding. The
> > +MPC512x DMA engine binding follows the common scheme, but doesn't provide
> > +support for the optional channels and requests counters (those values are
> > +derived from the detected hardware features) and has a fixed client
> > +specifier length of 1 integer cell (the value is the DMA channel, since
> > +the DMA controller uses a fixed assignment of request lines per channel).
>
> The fact that #dma-cells must be <1> isn't a difference from the
> standard binding, and needs not be described here. The meaning of the
> value should be in your description of #dma-cells below.
I think the value it has to be in there, and I have in the past asked other
people to add this. Note that in the generic binding, it says that it must
be "at least 1". You can have controllers that require a larger number, or
that can use 1 or 2 alternatively, depending on how the device is wired
up, e.g. when a dma controller has two master ports you would need a
second cell to specify the port number, but only if more than one port
is actually connected to a slave.
> I'm not sure it's worth mentioning optional channels / request counters.
> If anything, it would be better to update dma.txt to move the "Optional
> properties" to something like "Suggested properties"...
These are less clearly defined. In the generic binding, it's mostly a matter
of "if you need to pass this information, use these properties". The individual
binding can then make them mandatory if needed.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-18 14:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:19 [PATCH RFC v5 0/5] MPC512x DMA slave s/g support, OF DMA lookup Alexander Popov
2013-11-01 7:19 ` Alexander Popov
2013-11-01 7:19 ` [PATCH RFC v5 1/5] dma: mpc512x: reorder mpc8308 specific instructions Alexander Popov
2013-11-01 7:19 ` Alexander Popov
2013-11-01 10:04 ` Anatolij Gustschin
2013-11-01 10:04 ` Anatolij Gustschin
2013-11-11 20:01 ` Gerhard Sittig
2013-11-01 7:19 ` [PATCH RFC v5 2/5] dma: mpc512x: add support for peripheral transfers Alexander Popov
2013-11-01 7:19 ` Alexander Popov
2013-11-11 20:10 ` Gerhard Sittig
2013-11-11 20:10 ` Gerhard Sittig
2013-11-12 12:23 ` Alexander Popov
2013-11-12 12:23 ` Alexander Popov
2013-11-14 20:58 ` Gerhard Sittig
2013-11-14 20:58 ` Gerhard Sittig
2013-11-20 6:49 ` Alexander Popov
2013-11-20 6:49 ` Alexander Popov
2013-11-01 7:19 ` [PATCH RFC v5 3/5] dma: of: Add common xlate function for matching by channel id Alexander Popov
2013-11-01 7:19 ` Alexander Popov
2013-11-01 7:52 ` Arnd Bergmann
2013-11-01 7:52 ` Arnd Bergmann
2013-11-07 11:33 ` Alexander Popov
2013-11-07 11:33 ` Alexander Popov
2013-11-01 7:19 ` [PATCH RFC v5 4/5] dma: mpc512x: register for device tree channel lookup Alexander Popov
2013-11-01 7:19 ` Alexander Popov
2013-11-18 12:09 ` Mark Rutland
2013-11-18 12:09 ` Mark Rutland
2013-11-18 14:31 ` Arnd Bergmann [this message]
2013-11-18 14:31 ` Arnd Bergmann
2013-11-18 15:23 ` Mark Rutland
2013-11-18 15:23 ` Mark Rutland
2013-11-01 7:19 ` [PATCH RFC v5 5/5] HACK mmc: mxcmmc: enable clocks for the MPC512x Alexander Popov
2013-11-01 7:19 ` 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=201311181531.54818.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=a13xp0p0v88@gmail.com \
--cc=agust@denx.de \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gsi@denx.de \
--cc=lars@metafoo.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--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.