From: Rob Herring <robh@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: dmaengine: Document qcom,gpi dma binding
Date: Mon, 12 Oct 2020 13:57:37 -0500 [thread overview]
Message-ID: <20201012185737.GA1905980@bogus> (raw)
In-Reply-To: <20201008123151.764238-2-vkoul@kernel.org>
On Thu, Oct 08, 2020 at 06:01:49PM +0530, Vinod Koul wrote:
> Add devicetree binding documentation for GPI DMA controller
> implemented on Qualcomm SoCs
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
> .../devicetree/bindings/dma/qcom,gpi.yaml | 86 +++++++++++++++++++
> include/dt-bindings/dma/qcom-gpi.h | 11 +++
> 2 files changed, 97 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/qcom,gpi.yaml
> create mode 100644 include/dt-bindings/dma/qcom-gpi.h
>
> diff --git a/Documentation/devicetree/bindings/dma/qcom,gpi.yaml b/Documentation/devicetree/bindings/dma/qcom,gpi.yaml
> new file mode 100644
> index 000000000000..4470c1b2fd6c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/qcom,gpi.yaml
> @@ -0,0 +1,86 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/dma/qcom,gpi.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies Inc GPI DMA controller
> +
> +maintainers:
> + - Vinod Koul <vkoul@kernel.org>
> +
> +description: |
> + QCOM GPI DMA controller provides DMA capabilities for
> + peripheral buses such as I2C, UART, and SPI.
> +
> +allOf:
> + - $ref: "dma-controller.yaml#"
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,sdm845-gpi-dma
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + description:
> + Interrupt lines for each GPI instance
> + maxItems: 13
> +
> + "#dma-cells":
> + const: 3
> + description: >
> + DMA clients must use the format described in dma.txt, giving a phandle
> + to the DMA controller plus the following 3 integer cells:
> + - channel: if set to 0xffffffff, any available channel will be allocated
> + for the client. Otherwise, the exact channel specified will be used.
> + - seid: serial id of the client as defined in the SoC documentation.
> + - client: type of the client as defined in dt-bindings/dma/qcom-gpi.h
> +
> + iommus:
> + maxItems: 1
> +
> + dma-channels:
> + maximum: 31
> +
> + dma-channel-mask:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - "#dma-cells"
> + - iommus
> + - dma-channels
> + - dma-channel-mask
additionalProperties: false
With that,
Reviewed-by: Rob Herring <robh@kernel.org>
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/dma/qcom-gpi.h>
> + gpi_dma0: dma-controller@800000 {
> + compatible = "qcom,gpi-dma";
> + #dma-cells = <3>;
> + reg = <0x00800000 0x60000>;
> + iommus = <&apps_smmu 0x0016 0x0>;
> + dma-channels = <13>;
> + dma-channel-mask = <0xfa>;
> + interrupts = <GIC_SPI 244 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 245 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 246 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 247 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 248 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 249 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 250 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 251 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 252 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 253 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 254 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 255 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> +...
> diff --git a/include/dt-bindings/dma/qcom-gpi.h b/include/dt-bindings/dma/qcom-gpi.h
> new file mode 100644
> index 000000000000..71f79eb7614c
> --- /dev/null
> +++ b/include/dt-bindings/dma/qcom-gpi.h
> @@ -0,0 +1,11 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/* Copyright (c) 2020, Linaro Ltd. */
> +
> +#ifndef __DT_BINDINGS_DMA_QCOM_GPI_H__
> +#define __DT_BINDINGS_DMA_QCOM_GPI_H__
> +
> +#define QCOM_GPI_SPI 1
> +#define QCOM_GPI_UART 2
> +#define QCOM_GPI_I2C 3
> +
> +#endif /* __DT_BINDINGS_DMA_QCOM_GPI_H__ */
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-10-12 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 12:31 [PATCH v4 0/3] dmaengine: Add support for QCOM GSI dma controller Vinod Koul
2020-10-08 12:31 ` [PATCH v4 1/3] dt-bindings: dmaengine: Document qcom,gpi dma binding Vinod Koul
2020-10-12 18:57 ` Rob Herring [this message]
2020-10-13 7:02 ` Vinod Koul
2020-10-08 12:31 ` [PATCH v4 2/3] dmaengine: add peripheral configuration Vinod Koul
2020-10-09 9:04 ` Peter Ujfalusi
2020-10-09 10:30 ` Vinod Koul
2020-10-09 10:45 ` Peter Ujfalusi
2020-10-09 11:15 ` Vinod Koul
2020-10-09 11:29 ` Peter Ujfalusi
2020-10-12 6:09 ` Vinod Koul
2020-10-12 12:05 ` Peter Ujfalusi
2020-10-08 12:31 ` [PATCH v4 3/3] dmaengine: qcom: Add GPI dma driver Vinod Koul
2020-10-09 9:00 ` Peter Ujfalusi
2020-10-09 10:31 ` 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=20201012185737.GA1905980@bogus \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=vkoul@kernel.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).