From: Lokesh Vutla <lokeshvutla@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH 1/6] dt-bindings: ti,edma: Add 66AK2G specific information
Date: Sat, 12 Aug 2017 11:13:24 +0530 [thread overview]
Message-ID: <9a2a0a3d-cc6a-d672-ed38-bef406635d3c@ti.com> (raw)
In-Reply-To: <20170810000034.vvcdvdez3og6lhux@rob-hp-laptop>
On Thursday 10 August 2017 05:30 AM, Rob Herring wrote:
> On Tue, Aug 01, 2017 at 10:11:14AM +0530, Lokesh Vutla wrote:
>> Update ti,edma binding documentation to reflect 66AK2G specific
>> properties.
>>
>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>> ---
>> Documentation/devicetree/bindings/dma/ti-edma.txt | 95 +++++++++++++++++++++--
>> 1 file changed, 90 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/dma/ti-edma.txt b/Documentation/devicetree/bindings/dma/ti-edma.txt
>> index 18090e7226b4..05fe2931d025 100644
>> --- a/Documentation/devicetree/bindings/dma/ti-edma.txt
>> +++ b/Documentation/devicetree/bindings/dma/ti-edma.txt
>> @@ -9,7 +9,12 @@ execute the actual DMA tansfer.
>> eDMA3 Channel Controller
>>
>> Required properties:
>> -- compatible: "ti,edma3-tpcc" for the channel controller(s)
>> +--------------------
>> +- compatible: Should be:
>> + - "ti,edma3-tpcc" for the channel controller(s) on OMAP,
>> + AM33xx and AM43xx SoCs.
>> + - "ti,k2g-edma3-tpcc", "ti,edma3-tpcc" for the
>
> If power-domains is mandatory, I don't think the fallback is
> appropriate. Or do you expect it to work if the driver ignores the power
> domain?
power-domains is required for pm_runtime_*() apis to work on 66AK2G.
Driver doesn't handle this property separately. Driver still works with
"ti,edma3-tpcc" compatible.
Thanks and regards,
Lokesh
next prev parent reply other threads:[~2017-08-12 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 4:41 [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC Lokesh Vutla
2017-08-01 4:41 ` [PATCH 1/6] dt-bindings: ti,edma: Add 66AK2G specific information Lokesh Vutla
2017-08-01 12:50 ` Peter Ujfalusi
2017-08-02 17:03 ` Lokesh Vutla
2017-08-03 5:34 ` Sekhar Nori
2017-08-09 23:57 ` Rob Herring
2017-08-10 0:00 ` Rob Herring
2017-08-12 5:43 ` Lokesh Vutla [this message]
2017-08-01 4:41 ` [PATCH 2/6] dt-bindings: ti,omap-hsmmc: Add 66AK2G mmc controller Lokesh Vutla
2017-08-10 0:03 ` Rob Herring
2017-08-01 4:41 ` [PATCH 3/6] ARM: dts: keystone-k2g: Add eDMA nodes Lokesh Vutla
2017-08-01 4:41 ` [PATCH 4/6] ARM: dts: keystone-k2g: add MMC0 and MMC1 nodes Lokesh Vutla
2017-08-01 4:41 ` [PATCH 5/6] ARM: dts: keystone-k2g-evm: Enable MMC0 and MMC1 Lokesh Vutla
2017-08-01 4:41 ` [PATCH 6/6] ARM: configs: keystone: Enable MMC and regulators Lokesh Vutla
2017-08-01 18:10 ` [PATCH 0/6] ARM: dts: keystone-k2g: Add support for eDMA and MMC Santosh Shilimkar
2017-08-02 3:52 ` Keerthy
2017-08-07 13:38 ` santosh.shilimkar
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=9a2a0a3d-cc6a-d672-ed38-bef406635d3c@ti.com \
--to=lokeshvutla@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@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).