Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp1771614ybg; Sat, 19 Oct 2019 02:10:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvHIyx+tfVmkR4B8i42ilym0tjk1x729Oye6+aSAYjCxpRCESxGWtcNZ7UN/ptYEGYCqCl X-Received: by 2002:a50:f701:: with SMTP id g1mr14045779edn.62.1571476223286; Sat, 19 Oct 2019 02:10:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571476223; cv=none; d=google.com; s=arc-20160816; b=AOcd/BHLiu4ZBR7jzygWhk7Rq6wRRE9v1Pf5XFdRmuEo1ptUOIbhRctfjtGx9aZmDC 7XtpgVtEXITmi1plJhekd0DnS+tEHT58bB0h2efGn4o5upc607rOODKFvRQalaRkDjqk yjJGtHrs8j8OCV5Vo7nKW/k7rKaiWlDMvjUbCQsMh/SA6+02F4mBlKieFsJ0mUdjPdJQ LdYR3qROYZbcxyTBunSAijcCyQFn/yv6MhjBog8FRE1iPuGTBmpQED+51/HlR8ajA0bL LEoxg4UkC6HU4phdZH2P6sgoxDaTvuQ7reJ33WwhKjHcE0SWvsq3g3aTfdEi1cLW1kqI qXBg== 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:in-reply-to:references:mime-version :dkim-signature; bh=xDvHvj9qtzFYJJCjb0FODbVbRYKEmnABD86hWN3Plr4=; b=RLkDWBBE49qOwfUwWOYRkN4rNuQdB/os+JFGAhI5s8Y+ELjSqxCMf2QmxwdblSQvSb vC/Dh8i7HjbKXqomoAqIgNJJYhKyPWf6dT64Bc2aXyNBNbER058DPNn7J+5nYNtsGsCe PgQ8kJkx4orNn42ekymdLopvg2jAqREotyqa/smT/2cYsJEMr1kBTyVxZFWJ8vVMYEoT 254jMQyDOaNVcUzWaINHmh+4P+XJiQYqhiMOfBaOThKMSO/e/vfNU5pzjW9w1G9l7a97 1d/eiOuuTqxyRJ7UYe1GO2qfcldwF9kSe+fT/1huFarUgIUQBoDw9955zLmlvDoRsNzQ oH8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Yzkb7O7k; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u24si205679edq.79.2019.10.19.02.09.59; Sat, 19 Oct 2019 02:10:23 -0700 (PDT) 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=@kernel.org header.s=default header.b=Yzkb7O7k; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2443275AbfJRTJA (ORCPT + 99 others); Fri, 18 Oct 2019 15:09:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:59168 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2443216AbfJRTI7 (ORCPT ); Fri, 18 Oct 2019 15:08:59 -0400 Received: from mail-qk1-f182.google.com (mail-qk1-f182.google.com [209.85.222.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DD7F2222C9; Fri, 18 Oct 2019 19:08:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571425738; bh=GmnsYtHJlL/5yxZfKlw6PRpT4uy/4qUReZoxvsBsi1A=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Yzkb7O7kToMr9ftoJIsljRgPzqeY2SH+sT26HuU4kIKWFrb7ilYaeEZRB+M/FrexE MEZ21PsBxIZ12PSDEx0CTVd+lU+RIc+As8k86sYzqoxW/lMHMMx+o17Yq1/qTabGIG MPkvil9K++tYpUbqFk9N8tfSNy7Gz9RCledj00r0= Received: by mail-qk1-f182.google.com with SMTP id 71so2430896qkl.0; Fri, 18 Oct 2019 12:08:57 -0700 (PDT) X-Gm-Message-State: APjAAAWPTGVIErsQpV9L5ULLQxS7fJPsfviO5YoaqomYYv5JvXN77GKk WOZEGGhkQS0+TkwdpFWfXnD+i2N4olAwskpABg== X-Received: by 2002:a05:620a:12b4:: with SMTP id x20mr6347242qki.254.1571425736980; Fri, 18 Oct 2019 12:08:56 -0700 (PDT) MIME-Version: 1.0 References: <20191017071234.8719-1-brgl@bgdev.pl> <20191017071234.8719-4-brgl@bgdev.pl> <20191017183543.GA28403@bogus> In-Reply-To: From: Rob Herring Date: Fri, 18 Oct 2019 14:08:45 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 3/6] dt-bindings: regulator: max77650: convert the binding document to yaml To: Bartosz Golaszewski Cc: Bartosz Golaszewski , Mark Rutland , Dmitry Torokhov , Jacek Anaszewski , Pavel Machek , Dan Murphy , Lee Jones , Sebastian Reichel , Liam Girdwood , Mark Brown , Linux Input , linux-devicetree , LKML , Linux LED Subsystem , linux-pm 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 On Fri, Oct 18, 2019 at 1:45 AM Bartosz Golaszewski wrote: > > czw., 17 pa=C5=BA 2019 o 20:35 Rob Herring napisa=C5=82= (a): > > > > On Thu, Oct 17, 2019 at 09:12:31AM +0200, Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski > > > > > > Convert the binding document for MAX77650 regulator module to YAML. > > > > > > Signed-off-by: Bartosz Golaszewski > > > --- > > > .../bindings/regulator/max77650-regulator.txt | 41 -----------------= -- > > > .../regulator/max77650-regulator.yaml | 31 ++++++++++++++ > > > 2 files changed, 31 insertions(+), 41 deletions(-) > > > delete mode 100644 Documentation/devicetree/bindings/regulator/max77= 650-regulator.txt > > > create mode 100644 Documentation/devicetree/bindings/regulator/max77= 650-regulator.yaml > > > > > > diff --git a/Documentation/devicetree/bindings/regulator/max77650-reg= ulator.txt b/Documentation/devicetree/bindings/regulator/max77650-regulator= .txt > > > deleted file mode 100644 > > > index f1cbe813c30f..000000000000 > > > --- a/Documentation/devicetree/bindings/regulator/max77650-regulator.= txt > > > +++ /dev/null > > > @@ -1,41 +0,0 @@ > > > -Regulator driver for MAX77650 PMIC from Maxim Integrated. > > > - > > > -This module is part of the MAX77650 MFD device. For more details > > > -see Documentation/devicetree/bindings/mfd/max77650.txt. > > > - > > > -The regulator controller is represented as a sub-node of the PMIC no= de > > > -on the device tree. > > > - > > > -The device has a single LDO regulator and a SIMO buck-boost regulato= r with > > > -three independent power rails. > > > - > > > -Required properties: > > > --------------------- > > > -- compatible: Must be "maxim,max77650-regulator" > > > - > > > -Each rail must be instantiated under the regulators subnode of the t= op PMIC > > > -node. Up to four regulators can be defined. For standard regulator p= roperties > > > -refer to Documentation/devicetree/bindings/regulator/regulator.txt. > > > - > > > -Available regulator compatible strings are: "ldo", "sbb0", "sbb1", "= sbb2". > > > - > > > -Example: > > > --------- > > > - > > > - regulators { > > > - compatible =3D "maxim,max77650-regulator"; > > > - > > > - max77650_ldo: regulator@0 { > > > - regulator-compatible =3D "ldo"; > > > - regulator-name =3D "max77650-ldo"; > > > - regulator-min-microvolt =3D <1350000>; > > > - regulator-max-microvolt =3D <2937500>; > > > - }; > > > - > > > - max77650_sbb0: regulator@1 { > > > - regulator-compatible =3D "sbb0"; > > > - regulator-name =3D "max77650-sbb0"; > > > - regulator-min-microvolt =3D <800000>; > > > - regulator-max-microvolt =3D <1587500>; > > > - }; > > > - }; > > > diff --git a/Documentation/devicetree/bindings/regulator/max77650-reg= ulator.yaml b/Documentation/devicetree/bindings/regulator/max77650-regulato= r.yaml > > > new file mode 100644 > > > index 000000000000..a8770742836d > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/regulator/max77650-regulator.= yaml > > > @@ -0,0 +1,31 @@ > > > +# SPDX-License-Identifier: GPL-2.0 > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/regulator/max77650-regulator.yaml= # > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: Regulator driver for MAX77650 PMIC from Maxim Integrated. > > > + > > > +maintainers: > > > + - Bartosz Golaszewski > > > + > > > +description: | > > > + This module is part of the MAX77650 MFD device. For more details > > > + see Documentation/devicetree/bindings/mfd/max77650.txt. > > > > .yaml? > > > > Is there any better way of referencing the main document than > mentioning it in the description? No. Rob