From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Chao Fu <b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/3] Documentation:spi:fsl-dspi:add DSPI dma transfer support
Date: Tue, 25 Feb 2014 09:08:30 +0000 [thread overview]
Message-ID: <20140225090830.GO28555@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1393311258-14380-1-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Tue, Feb 25, 2014 at 06:54:16AM +0000, Chao Fu wrote:
> From: Chao Fu <B44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>
> Add bool value use-dma.
> The bool will determine whether DSPI use dma channel transfer data
> in a platform.
>
> Add dmas and dma-names for describing dma channels of DSPI.
>
> Signed-off-by: Chao Fu <b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> ---
> Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt b/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt
> index 5376de4..76a1039 100644
> --- a/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt
> +++ b/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt
> @@ -11,6 +11,11 @@ Required properties:
> - spi-num-chipselects : the number of the chipselect signals.
> - bus-num : the slave chip chipselect signal number.
> - big-endian : if DSPI modudle is big endian, the bool will be set in node.
> +- use-dma: the bool decide if use dma method in DSPI transfering.
Why can the OS not decide this based on the presence of dmas which it
can use?
Is there ever a case that there would be dmas present but it would be in
the interests of the OS to not use them?
Mark.
> +- dmas: List of DMA specifiers with the controller specific format
> + as described in the generic DMA client binding. A tx and rx
> + specifier is required for each chip select.
> +- dma-names: Should be named "tx" and "rx".
> Example:
>
> dspi0@4002c000 {
> @@ -26,6 +31,10 @@ dspi0@4002c000 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_dspi0_1>;
> big-endian;
> + use-dma;
> + dmas = <&edma0 0 12>,
> + <&edma0 0 13>;
> + dma-names = "rx", "tx";
> status = "okay";
>
> sflash: at26df081a@0 {
> --
> 1.8.4
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" 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:[~2014-02-25 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 6:54 [PATCH 1/3] Documentation:spi:fsl-dspi:add DSPI dma transfer support Chao Fu
2014-02-25 6:54 ` [PATCH 2/3] arm:dts:vf-610:add vybrid DSPI DMA " Chao Fu
[not found] ` <1393311258-14380-1-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-02-25 6:54 ` [PATCH 3/3] spi:fsl-dspi:add dspi dma " Chao Fu
[not found] ` <1393311258-14380-3-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-02-25 9:15 ` Mark Rutland
2014-02-25 9:08 ` Mark Rutland [this message]
[not found] ` <20140225090830.GO28555-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2014-02-26 14:19 ` [PATCH 1/3] Documentation:spi:fsl-dspi:add DSPI " Shawn Guo
[not found] ` <20140226141947.GE23892-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2014-02-26 15:38 ` Mark Brown
[not found] ` <20140226153822.GC2394-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-02-27 7:42 ` Shawn Guo
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=20140225090830.GO28555@e106331-lin.cambridge.arm.com \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 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).