From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1EC4BCA9EA3 for ; Fri, 18 Oct 2019 06:45:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E1F7D20820 for ; Fri, 18 Oct 2019 06:45:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20150623.gappssmtp.com header.i=@baylibre-com.20150623.gappssmtp.com header.b="fdz+n06H" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2504474AbfJRGpL (ORCPT ); Fri, 18 Oct 2019 02:45:11 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:42218 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729119AbfJRGpL (ORCPT ); Fri, 18 Oct 2019 02:45:11 -0400 Received: by mail-ot1-f67.google.com with SMTP id c10so4063345otd.9 for ; Thu, 17 Oct 2019 23:45:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=1lF1MIdaENKkNdKHx3QF8806cfpyw2N47Ri2S6zNu+A=; b=fdz+n06HECsJp9I5yC12MLoPyso3cVdDWSygC4Y7XVo2s+raIUe7Kh+aLwemhLMU5k i7dVQR2xfPsax9aa+5VJyUvt0/X84pN8bZr2I1IqodPrl3WJd8v/DQvU0Mn7HPDL3F9G p2zjMx/ktE9PQCFIGtVBeHWjl+r/xzysY7yUr0+lRii3jz18vN6MqHlkSU45xQ55o05m G1FSO9291SHGdzv4XiuXv+oNdb3MCs2XWDCdELcJYSDl+uaG/muocWgujsYLr1TZ5iXU 5ElzuYwPbcYqYAwmJUKvQibj3nrYv8cN7CxOJQhhzGPFEDhOSpyWjgAwj+3CpwrqQEHf a/Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=1lF1MIdaENKkNdKHx3QF8806cfpyw2N47Ri2S6zNu+A=; b=TSNgqqRW2vcuRhR6sjLWI1SXbvaHWPrWfxKmQm3PtjPZyxTzt5yUWGPbrCrDsh2MGj huG7pkZUBhxKbtYQ+5uJjTHhguVNNjWfnszX2+RS5vZd5yQACFz2kx1UV85gfQ+I49Uk 8JasUmvCmlc6W4n0wajb4ke2zftUoRZsI1aSCjk5sko+/lrfzbdULa2KuMbHVvKIF85/ YC5FN+TXO5XMWiuwWbKB8kTXBHEsjC9RHEln4X8prlraitf9Gh/NwaePI+vtQYCi3HIz 0hZaE3vgudwRqDZP9HL6jyJDtZAkHV/7iVGGntsippjhrTvuPsNWWSYNmJZ0EaeMNnt/ a80g== X-Gm-Message-State: APjAAAWAsJ/J3LsIgKIGsiJxYph7xtisrSglT713MiDp6G2lauGCuY8f v/AO2U+sjz5I527HZbKUr8jod044Dj8UyTH4x0rc0A== X-Google-Smtp-Source: APXvYqxyM+v+SYTdyxQ4dtigF5DDcYtT8ndNrsXVrCyXLrBJJzjjCW0hbJvIcRwuifhyrCsk7IlYvVPciQR043PPUQs= X-Received: by 2002:a9d:7d09:: with SMTP id v9mr6404595otn.292.1571381108752; Thu, 17 Oct 2019 23:45:08 -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: <20191017183543.GA28403@bogus> From: Bartosz Golaszewski Date: Fri, 18 Oct 2019 08:44:57 +0200 Message-ID: Subject: Re: [PATCH v3 3/6] dt-bindings: regulator: max77650: convert the binding document to yaml To: Rob Herring 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-leds-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-leds@vger.kernel.org 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/max7765= 0-regulator.txt > > create mode 100644 Documentation/devicetree/bindings/regulator/max7765= 0-regulator.yaml > > > > diff --git a/Documentation/devicetree/bindings/regulator/max77650-regul= ator.txt b/Documentation/devicetree/bindings/regulator/max77650-regulator.t= xt > > deleted file mode 100644 > > index f1cbe813c30f..000000000000 > > --- a/Documentation/devicetree/bindings/regulator/max77650-regulator.tx= t > > +++ /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 node > > -on the device tree. > > - > > -The device has a single LDO regulator and a SIMO buck-boost regulator = with > > -three independent power rails. > > - > > -Required properties: > > --------------------- > > -- compatible: Must be "maxim,max77650-regulator" > > - > > -Each rail must be instantiated under the regulators subnode of the top= PMIC > > -node. Up to four regulators can be defined. For standard regulator pro= perties > > -refer to Documentation/devicetree/bindings/regulator/regulator.txt. > > - > > -Available regulator compatible strings are: "ldo", "sbb0", "sbb1", "sb= b2". > > - > > -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-regul= ator.yaml b/Documentation/devicetree/bindings/regulator/max77650-regulator.= yaml > > new file mode 100644 > > index 000000000000..a8770742836d > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/regulator/max77650-regulator.ya= ml > > @@ -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? Bart > > + > > + 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. > > + > > +properties: > > + compatible: > > + const: maxim,max77650-regulator > > + > > +patternProperties: > > + "^regulator@[0-3]$": > > + $ref: "regulator.yaml#" > > + > > +required: > > + - compatible > > -- > > 2.23.0 > >