From: Sricharan R <r.sricharan@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-doc@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Benoit Cousson <bcousson@baylibre.com>
Subject: Re: [PATCH 2/2] ARM: dts: doc: Document missing binding for ti-sdma controller
Date: Mon, 11 Nov 2013 21:28:03 +0530 [thread overview]
Message-ID: <5280FE8B.7060804@ti.com> (raw)
In-Reply-To: <CAL_JsqKfHPcycgH7oZeGYpnuEV-PBH1q_11O8=gC_50X_vWJsA@mail.gmail.com>
On Monday 11 November 2013 09:26 PM, Rob Herring wrote:
> On Sat, Nov 9, 2013 at 5:53 AM, Sricharan R <r.sricharan@ti.com> wrote:
>> Hi Rob,
>>
>> On Saturday 09 November 2013 03:24 AM, Rob Herring wrote:
>>> On Fri, Nov 8, 2013 at 4:38 AM, Sricharan R <r.sricharan@ti.com> wrote:
>>>> The binding and support for system DMA module present in OMAP2+ Socs
>>>> and DRA7 with dma-engine is already present. So adding the missing
>>>> documentation for the same.
>>>>
>>>> Cc: Benoit Cousson <bcousson@baylibre.com>
>>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>>> ---
>>>> Documentation/devicetree/bindings/dma/ti-sdma.txt | 28 +++++++++++++++++++++
>>>> 1 file changed, 28 insertions(+)
>>>> create mode 100644 Documentation/devicetree/bindings/dma/ti-sdma.txt
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/dma/ti-sdma.txt b/Documentation/devicetree/bindings/dma/ti-sdma.txt
>>>> new file mode 100644
>>>> index 0000000..7fb2342
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/dma/ti-sdma.txt
>>>> @@ -0,0 +1,28 @@
>>>> +TI SDMA
>>>> +
>>>> +Required Properties:
>>>> +- compatible : Should be "ti,omap2420-sdma", "ti,omap2430-sdma" for OMAP2
>>>> + Should be "ti,omap3430-sdma", "ti,omap3630-sdma" for OMAP3
>>>> + Should be "ti,omap4430-sdma" for OMAP4, OMAP5 and DRA7
>>>> +- reg: Memory map for accessing module
>>>> +- interrupts: Interrupt request number from the dma controller to
>>> s/dma/DMA/
>>>
>>>> + interrupt controller
>>>> +- dma-cells: Should be set to <1>
>>>> +- dma-channels: Total number of logical DMA channels supported by the
>>>> + controller
>>>> +- dma-requests: Total number of dma request signals supported by the
>>> s/dma/DMA/
>> Ok, will correct case.
>>>> + controller
>>> These should have the # included.
>> Sorry, i do not follow this ?
> You are missing the # in the property names as the example has:
>
> + #dma-cells = <1>;
> + #dma-channels = <32>;
> + #dma-requests = <64>;
>
> Rob
Oh, ok, Will add this.
Regards,
Sricharan
next prev parent reply other threads:[~2013-11-11 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 10:38 [PATCH 1/2] ARM: dts: doc: Document missing binding for omap5-mpu Sricharan R
2013-11-08 10:38 ` [PATCH 2/2] ARM: dts: doc: Document missing binding for ti-sdma controller Sricharan R
2013-11-08 21:54 ` Rob Herring
2013-11-09 11:53 ` Sricharan R
2013-11-11 15:56 ` Rob Herring
2013-11-11 15:58 ` Sricharan R [this message]
2013-12-03 5:44 ` [PATCH 1/2] ARM: dts: doc: Document missing binding for omap5-mpu Rob Herring
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=5280FE8B.7060804@ti.com \
--to=r.sricharan@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.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).