linux-kernel - Re: [PATCH 1/6] dt-bindings: ti,edma: Add 66AK2G specific information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170810000034.vvcdvdez3og6lhux@rob-hp-laptop>
Date:   Wed, 9 Aug 2017 19:00:34 -0500
From:   Rob Herring <robh@...nel.org>
To:     Lokesh Vutla <lokeshvutla@...com>
Cc:     Santosh Shilimkar <ssantosh@...nel.org>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        linux-kernel@...r.kernel.org,
        Device Tree Mailing List <devicetree@...r.kernel.org>,
        Tero Kristo <t-kristo@...com>, Sekhar Nori <nsekhar@...com>,
        Peter Ujfalusi <peter.ujfalusi@...com>,
        Keerthy <j-keerthy@...com>
Subject: Re: [PATCH 1/6] dt-bindings: ti,edma: Add 66AK2G specific information

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@...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?