From: Grant Likely <grant.likely@secretlab.ca>
To: Vinod Koul <vinod.koul@intel.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Andy Gross <agross@codeaurora.org>
Subject: Re: [PATCH 2/2] dmaengine: msm_bam_dma: Add device tree binding
Date: Sat, 26 Oct 2013 00:20:15 +0100 [thread overview]
Message-ID: <20131025232015.9082FC403B6@trevor.secretlab.ca> (raw)
In-Reply-To: <1382732643-8184-3-git-send-email-agross@codeaurora.org>
On Fri, 25 Oct 2013 15:24:03 -0500, Andy Gross <agross@codeaurora.org> wrote:
> Add device tree probe support for the MSM BAM DMA driver.
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
> ---
> .../devicetree/bindings/dma/msm_bam_dma.txt | 49 ++++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/msm_bam_dma.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/msm_bam_dma.txt b/Documentation/devicetree/bindings/dma/msm_bam_dma.txt
> new file mode 100644
> index 0000000..fe3ed8f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/msm_bam_dma.txt
> @@ -0,0 +1,49 @@
> +MSM BAM DMA controller
> +
> +Required properties:
> +- compatible: Should be "qcom,bam"
Really should be more specific than this. "qcom,bam" doesn't clarify
what SoC this hardware is implemented on.
Otherwise the binding looks fine.
g.
> +- reg: Address range for DMA registers
> +- interrupts: single interrupt for this controller
> +- #dma-cells: must be <3>
> +- clocks: required clock
> +- clock-names: name of clock
> +
> +Example:
> +
> + dma0: dma@f9984000 = {
> + compatible = "qcom,bam";
> + reg = <0xf9984000 0x15000>;
> + interrupts = <0 94 0>;
> + clocks = <&bam_dma_ahb_cxc>;
> + clock-names = "bam_clk";
> + #dma-cells = <3>;
> + };
> +
> +Client:
> +Required properties:
> +- dmas: List of dma channel requests
> +- dma-names: Names of aforementioned requested channels
> +
> +Clients must use the format described in the dma.txt file, using a four cell
> +specifier for each channel.
> +
> +The four cells in order are:
> + 1. A phandle pointing to the DMA controller
> + 2. The channel number
> + 3. The execution environment value for this channel.
> + 4. Direction of the fixed unidirectional channel
> + 0 - Memory to Device
> + 1 - Device to Memory
> +
> +Example:
> + serial@f991e000 {
> + compatible = "qcom,msm-uart";
> + reg = <0xf991e000 0x1000>
> + <0xf9944000 0x19000>;
> + interrupts = <0 108 0>;
> + clocks = <&blsp1_uart2_apps_cxc>, <&blsp1_ahb_cxc>;
> + clock-names = "gsbi_uart_clk", "gsbi_pclk";
> +
> + dmas = <&dma0 0 0 1>, <&dma0 1 0 0>;
> + dma-names = "rx", "tx";
> + };
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-10-25 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 20:24 [PATCH 0/2] add MSM BAM dmaengine driver Andy Gross
2013-10-25 20:24 ` [PATCH 1/2] dmaengine: add msm bam dma driver Andy Gross
2013-10-29 17:56 ` Stephen Boyd
2013-10-30 20:31 ` Andy Gross
2013-10-30 20:46 ` Stephen Boyd
2013-11-13 22:07 ` Tomasz Figa
2013-10-31 16:59 ` Vinod Koul
2013-10-31 21:46 ` Andy Gross
2013-11-07 23:03 ` Andy Gross
2013-11-13 13:18 ` Vinod Koul
2013-11-13 21:03 ` Andy Gross
[not found] ` <1382732643-8184-1-git-send-email-agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-10-25 20:24 ` [PATCH 2/2] dmaengine: msm_bam_dma: Add device tree binding Andy Gross
2013-10-25 21:31 ` Kumar Gala
2013-10-25 23:20 ` Grant Likely [this message]
2013-10-29 6:18 ` Stephen Boyd
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=20131025232015.9082FC403B6@trevor.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=agross@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).