Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752378AbdHJAAi (ORCPT ); Wed, 9 Aug 2017 20:00:38 -0400 Received: from mail-yw0-f196.google.com ([209.85.161.196]:33141 "EHLO mail-yw0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752176AbdHJAAh (ORCPT ); Wed, 9 Aug 2017 20:00:37 -0400 Date: Wed, 9 Aug 2017 19:00:34 -0500 From: Rob Herring To: Lokesh Vutla Cc: Santosh Shilimkar , Linux ARM Mailing List , linux-kernel@vger.kernel.org, Device Tree Mailing List , Tero Kristo , Sekhar Nori , Peter Ujfalusi , Keerthy Subject: Re: [PATCH 1/6] dt-bindings: ti,edma: Add 66AK2G specific information Message-ID: <20170810000034.vvcdvdez3og6lhux@rob-hp-laptop> References: <20170801044119.16201-1-lokeshvutla@ti.com> <20170801044119.16201-2-lokeshvutla@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170801044119.16201-2-lokeshvutla@ti.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1126 Lines: 27 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 > --- > 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?