Received: by 10.223.164.202 with SMTP id h10csp672536wrb; Thu, 9 Nov 2017 12:27:27 -0800 (PST) X-Google-Smtp-Source: ABhQp+RcieE121+8srnKVJTV61NIB/zz6WkwvRyGyyeruVZ32KDnZe4LPL29PPrmf0Dsc3E0R5pC X-Received: by 10.159.207.147 with SMTP id z19mr1546320plo.441.1510259247322; Thu, 09 Nov 2017 12:27:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510259247; cv=none; d=google.com; s=arc-20160816; b=uxTLRmGtt/r01PiDZzrs6dUBYQD9e7jkdRB8wsRNyRDa6nU/+eQNlcMY4njMcN+oaZ x5yqdmLIOJ/gAa/eNkQaNmHlEjCeWI1XE6XflWfQaAIvItXOMkaFEvEeWBrOXbuSRKiv F2jCyR1Of17uD35WjV4JtiF+xL30TpWEGVvOAnTBE/T7xzX4KEQXuB5Gyj+9EOTiby60 y2UprgsrE4VyZ/FFyEp5nkuLNtr76W1/VgZL5/iqlS4vHd7BN9PlPuijPr+i66EL/t5r 877kCm+akHkX/8/r8xgRO8Eif+9TmxQOmhkBNmr5PtY3XMfjf+Vs1VV/lJQzxOHjKTBB zJaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:references:in-reply-to:mime-version :dkim-signature:arc-authentication-results; bh=bU2jx553gir1DPKKHmxTAPhU/BVfybvjj3NcXSGBcgw=; b=JHfeovFbkt8c3WZfBTkLmyAI0xiX4YrVW+0EGU7dntdPnhAA9Dm+7dSCtnNzvsqqOc wGZ7a9gT7EKlNl8AsyKsJSVbKA8Obr9YzP7jlBuPP7PIL+9FuCSdE5r38LKxCLSSDh+e f6LoBJjuw3IP33GWa/q1rtEhdvCigHt/dvv4JZ5pjkd5JFBrSOCJ/qWE+7wkKRbP8MD6 ngAZX+3/YEciCTFzzdDVHaoRh/bY28DTt+t55nJOQR5m9a6rS5Z31i1hYQlQj8PYK/h0 1ISAyK8SlCa64rU1VI/CLYtMCAZrLakQlv0W7easpdKvKjbImY2ofPFzekOk7PYYzZdW JRuw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=uaMsozbl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w6si6712879pgb.441.2017.11.09.12.27.01; Thu, 09 Nov 2017 12:27:27 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=uaMsozbl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753276AbdKIU0X (ORCPT + 83 others); Thu, 9 Nov 2017 15:26:23 -0500 Received: from mail-vk0-f67.google.com ([209.85.213.67]:48384 "EHLO mail-vk0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751225AbdKIU0V (ORCPT ); Thu, 9 Nov 2017 15:26:21 -0500 Received: by mail-vk0-f67.google.com with SMTP id y196so4807053vkc.5; Thu, 09 Nov 2017 12:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bU2jx553gir1DPKKHmxTAPhU/BVfybvjj3NcXSGBcgw=; b=uaMsozbl99iyMW2laYy4odxpk3bD6o+/DOM9X7K1lkRS/J4aBcXo4lBFtMpJK04CfD VD2eO369P145d15GkPRzQZ5QSBVeANOq4uGiTpzLWbY5U3Rc05QYu9IskcMeebqdaXq4 GUtnOU1siRt4/e9j4nWguCSruD5p8N3zSQD4/N8mYp7t1dkazZIvsn3kUm4bYq5P4CCH 4w6XztsqDaNQyRajDRVq9ZKCS2CqvfiryFEEeIXx/LniT1q5VaBTa32TNASeNZdBgTZi U+kWBrK9uFlbJopItGZInLSujpdQna91CIOr9uQCtwO2NZz+BzbQ9UE5u9KE84dnXV/r YBHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bU2jx553gir1DPKKHmxTAPhU/BVfybvjj3NcXSGBcgw=; b=YYWOo5V7mXW2ChdUow3+HWyd/+DkweF1TGl2atIvJbPnbOjpQic15YZ4qQR1fpjc8j 3lqESpfsw7WVRWwU5ixAtqvjBfbrRYTLE6TzDx8hPY8yaxj9e8ux1MvuDCrSqhTr6pis ehYmkI45rJ2ejK47OpooYvngh74jTxSLOmoA/LtEblBJrXdEH7OLO1F2bwdajN8K3v2i y14aZFQeKPLTLRRoQgflJes8n8w8xjxtmtiaE5Qf5XI27OnzG4bX+glRkrKekgKWTRQ8 m2hvsU98zCNVN9oxvoUEf1PveImW73YFkNzBdx8Ls9BhCoGS+vQPcvKFXT+jg9bjs+yd 0Y4g== X-Gm-Message-State: AJaThX4BVrV7IOdusKGvQ5Q+CV8P/W855iJ1gM1z4gXQlc8wy6k7MIiR 0AktwhkchqP2AssOGV5ddqeclrqmWwDeW6l1XOg= X-Received: by 10.31.185.198 with SMTP id j189mr1484678vkf.172.1510259180858; Thu, 09 Nov 2017 12:26:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.23.92 with HTTP; Thu, 9 Nov 2017 12:26:00 -0800 (PST) In-Reply-To: <20171108212505.28320-3-afd@ti.com> References: <20171108212505.28320-1-afd@ti.com> <20171108212505.28320-3-afd@ti.com> From: =?UTF-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?= Date: Thu, 9 Nov 2017 21:26:00 +0100 Message-ID: Subject: Re: [alsa-devel] [PATCH 2/9] ASoC: tlv320aic3x: Fix typo in DT binding documentation To: "Andrew F. Davis" Cc: Liam Girdwood , Mark Brown , Rob Herring , Mark Rutland , =?UTF-8?Q?Beno=C3=AEt_Cousson?= , Tony Lindgren , Shawn Guo , Sascha Hauer , devicetree@vger.kernel.org, Alsa-devel , linux-kernel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Andrew F. Davis, On Wed, Nov 8, 2017 at 10:24 PM, Andrew F. Davis wrote: > The property used to specify a GPIO intended for reset is "reset-gpio", > this binding uses "gpio-reset", as almost all other bindings use the > former name this use of the latter is certainly not intended and > was a typo. It is not compatible with newer methods used to fetch > GPIO pins and to prevent the spread of this error to other bindings > lets fix this here. > > We also standardize the pin as active-low, different device trees have > marked the GPIO different ways, luckily the driver currently uses the > low-level GPIO set function which does not respect the active-low flag, > but future changes may change this. This is an active-low reset, mark > it as such. > > Lastly, add an example of use for this property. > > Fixes: c24fdc886fde ("ASoC: tlv320aic3x: Add device tree bindings") > > Signed-off-by: Andrew F. Davis > --- > Documentation/devicetree/bindings/sound/tlv320aic3x.txt | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/sound/tlv320aic3x.txt b/Do= cumentation/devicetree/bindings/sound/tlv320aic3x.txt > index ba5b45c483f5..9e8eaa08ce90 100644 > --- a/Documentation/devicetree/bindings/sound/tlv320aic3x.txt > +++ b/Documentation/devicetree/bindings/sound/tlv320aic3x.txt > @@ -17,7 +17,7 @@ Required properties: > > Optional properties: > > -- gpio-reset - gpio pin number used for codec reset > +- reset-gpio - GPIO specification for the active low RESET input. > - ai3x-gpio-func - - AIC3X_GPIO1 & AIC3X_GPIO2 Function= ality > - Not supported on tlv320aic3104 > - ai3x-micbias-vg - MicBias Voltage required. > @@ -61,10 +61,14 @@ The pins can be used in referring sound node's audio-= routing property. > > Example: > > +#include > + > tlv320aic3x: tlv320aic3x@1b { > compatible =3D "ti,tlv320aic3x"; > reg =3D <0x1b>; > > + reset-gpio =3D <&gpio1 17 GPIO_ACTIVE_LOW>; > + > AVDD-supply =3D <®ulator>; > IOVDD-supply =3D <®ulator>; > DRVDD-supply =3D <®ulator>; According to Documentation/devicetree/bindings/gpio/gpio.txt: "GPIO properties should be named "[-]gpios", with being the pu= rpose of this GPIO for the device. While a non-existent is considered vali= d for compatibility reasons (resolving to the "gpios" property), it is not al= lowed for new bindings. Also, GPIO properties named "[-]gpio" are valid and= old bindings use it, but are only supported for compatibility reasons and shoul= d not be used for newer bindings since it has been deprecated." So it should be "reset-gpios" for new bindings. Also, sound/soc/codecs/tlv320aic3x.c still uses "gpio-reset", and I do not see any patch in your series changing this: ret =3D of_get_named_gpio(np, "gpio-reset", 0); Same remarks for your "[PATCH 6/9] ARM: dts: imx: Fix the audio CODEC's reset pin". I don't know if there are other DTS files using this, but they should all be updated accordingly. This would anyway break all of the out-of-tree DTS files using this, which I think is not allowed, so the driver should be changed in a way still allowing the legacy naming besides the new one. Best regards, Beno=C3=AEt From 1583534866179852401@xxx Wed Nov 08 21:28:51 +0000 2017 X-GM-THRID: 1583534866179852401 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread