From: Rob Herring <robh@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Mark Rutland <mark.rutland@arm.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: dmaengine: Add UniPhier external DMA controller bindings
Date: Tue, 7 Jan 2020 21:55:37 -0600 [thread overview]
Message-ID: <20200108035537.GA7843@bogus> (raw)
In-Reply-To: <1576630620-1977-2-git-send-email-hayashi.kunihiko@socionext.com>
On Wed, Dec 18, 2019 at 09:56:59AM +0900, Kunihiko Hayashi wrote:
> Add external DMA controller bindings implemented in Socionext UniPhier
> SoCs.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
> .../devicetree/bindings/dma/uniphier-xdmac.txt | 86 ++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/uniphier-xdmac.txt
Please make this a DT schema. See
Documentation/devicetree/writing-schema.rst.
>
> diff --git a/Documentation/devicetree/bindings/dma/uniphier-xdmac.txt b/Documentation/devicetree/bindings/dma/uniphier-xdmac.txt
> new file mode 100644
> index 00000000..4e3927f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/uniphier-xdmac.txt
> @@ -0,0 +1,86 @@
> +Socionext UniPhier external DMA controller bindings
> +
> +This describes the devicetree bindings for an external DMA engine to perform
> +memory-to-memory or peripheral-to-memory data transfer, implemented in
> +Socionext UniPhier SoCs.
> +
> +* DMA controller
> +
> +Required properties:
> +- compatible: Should be "socionext,uniphier-xdmac".
> +- reg: Specifies offset and length of the register set for the device.
> +- interrupts: An interrupt specifier associated with the DMA controller.
> +- #dma-cells: Must be <2>. The first cell represents the channel index.
> + The second cell represents the factor for transfer request.
> + This is mentioned in DMA client section.
> +- dma-channels : Number of DMA channels supported. Should be 16.
If always 16, then why do you need this?
> +
> +Example:
> + xdmac: dma-controller@5fc10000 {
> + compatible = "socionext,uniphier-xdmac";
> + reg = <0x5fc10000 0x1000>, <0x5fc20000 0x800>;
> + interrupts = <0 188 4>;
> + #dma-cells = <2>;
> + dma-channels = <16>;
> + };
> +
> +* DMA client
> +
> +Required properties:
> +- dmas: A list of DMA channel requests.
> +- dma-names: Names of the requested channels corresponding to dmas.
> +
> +DMA clients must use the format described in the dma.txt file, using a two cell
> +specifier for each channel.
No need to redefine the client binding here. Just need the cell format
as below.
> +
> +Each DMA request consists of 3 cells:
> + 1. A phandle pointing to the DMA controller
> + 2. Channel index
> + 3. Transfer request factor number, If no transfer factor, use 0.
> + The number is SoC-specific, and this should be specified with relation
> + to the device to use the DMA controller. The list of the factor number
> + can be found below.
> +
> + 0x0 none
> + 0x8 UART ch0 Rx
> + 0x9 UART ch0 Tx
> + 0xa UART ch1 Rx
> + 0xb UART ch1 Tx
> + 0xc UART ch2 Rx
> + 0xd UART ch2 Tx
> + 0xe UART ch3 Rx
> + 0xf UART ch3 Tx
> + 0x14 SCSSI ch1 Rx
> + 0x15 SCSSI ch1 Tx
> + 0x16 SCSSI ch0 Rx
> + 0x17 SCSSI ch0 Tx
> + 0x18 SCSSI ch2 Rx
> + 0x19 SCSSI ch2 Tx
> + 0x1a SCSSI ch3 Rx
> + 0x1b SCSSI ch3 Tx
> + 0x21 I2C ch0 Rx
> + 0x22 I2C ch0 Tx
> + 0x23 I2C ch1 Rx
> + 0x24 I2C ch1 Tx
> + 0x25 I2C ch2 Rx
> + 0x26 I2C ch2 Tx
> + 0x27 I2C ch3 Rx
> + 0x28 I2C ch3 Tx
> + 0x29 I2C ch4 Rx
> + 0x2a I2C ch4 Tx
> + 0x2b I2C ch5 Rx
> + 0x2c I2C ch5 Tx
> + 0x2d I2C ch6 Rx
> + 0x2e I2C ch6 Tx
> +
> +Example:
> + spi3: spi@54006300 {
> + compatible = "socionext,uniphier-scssi";
> + reg = <0x54006300 0x100>;
> + interrupts = <0 39 4>;
> + clocks = <&peri_clk 14>;
> + resets = <&peri_rst 14>;
> +
> + dmas = <&xdmac 0 0x1a>, <&xdmac 1 0x1b>;
> + dma-names = "rx", "tx";
> + };
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-01-08 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 0:56 [PATCH 0/2] dmaengine: Add UniPhier XDMAC driver Kunihiko Hayashi
2019-12-18 0:56 ` [PATCH 1/2] dt-bindings: dmaengine: Add UniPhier external DMA controller bindings Kunihiko Hayashi
2020-01-08 3:55 ` Rob Herring [this message]
2020-01-09 12:20 ` Kunihiko Hayashi
2019-12-18 0:57 ` [PATCH 2/2] dmaengine: uniphier-xdmac: Add UniPhier external DMA controller driver Kunihiko Hayashi
2019-12-27 6:34 ` Vinod Koul
2020-01-09 12:12 ` Kunihiko Hayashi
2020-01-10 8:01 ` Vinod Koul
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=20200108035537.GA7843@bogus \
--to=robh@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=vkoul@kernel.org \
--cc=yamada.masahiro@socionext.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).