Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp7539854ybp; Wed, 16 Oct 2019 10:09:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqwNmI8iVu3cMc99YJw/TFck8EyIxHdKeKvroYG/dkyRWGZjM9Q4qiSrg72ZybWncxO3dnWA X-Received: by 2002:a17:907:365:: with SMTP id rs5mr41638122ejb.121.1571245748000; Wed, 16 Oct 2019 10:09:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571245747; cv=none; d=google.com; s=arc-20160816; b=qHc7za1gTtRP22ZOQmlbMT/IFpimBRhjA6PMcKmRj4OWBwxz4PkvFklBmRPRoBnwwc cthkPIc7pJGeoxUryS4b1tyqmNchoWufwGiYN76oDZw9hr+zdKkkp66lMzPQCSBaU20J dasAabGewG2nJO74BznRv8K7l6ykw88olsSijNbUX4xmvuP0AaRaknyv5C+RJKyjZ65n L2RwzptPFM0jrJBNjDWCtfiIl5aeSYRTciUaCrVQt69Rps84KZtdN75kvlgzbsmJsb+B HC42CAcBOZTJiF8oLVNP9DAGkFHuwCEv2Q9pBtxL6twUVpLyR2OUFh2qEIbDSaGOquL0 Fqbg== 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=V9VEJ6qCsL2ywbrpNNXgyPcRNbaXwu3Y4oOlJhBpLzQ=; b=uYUul1cKtqN6N4J8LpfAsrkvQxAuBw+Mx/DBlneTo/HGD6TTQnLjd5cu3RVPhR8eh9 EHCDoMaeDemh2IvBjYt0Ty7dLBr4rd6Y7Wet3k2SKomrzfIfNH23p59O2C2g5td+BVIG fchIVrRNqG2EZkGQrwJgnyuEv55g1+vhwOwmfbIBpft+fBalytHwISCmsB+XttNC8Y6t b1ZDLA1vNZExFTRPazk9lmFUV+kXT+0b7OXO7/EgdaSaAG0OZk+Jb6b0eYq/s/vpDl+d /pxpVt4lKMPVVaJw7tPcaxXvjF6H/L3vh/hc1PaK2UiqVSzaaBCsVw+F+Wq/Gojwjq/i sSZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=cDMLHUXZ; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y2si15661147eds.98.2019.10.16.10.08.45; Wed, 16 Oct 2019 10:09:07 -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=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=cDMLHUXZ; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2394138AbfJPP3E (ORCPT + 99 others); Wed, 16 Oct 2019 11:29:04 -0400 Received: from mail-ot1-f66.google.com ([209.85.210.66]:46709 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392991AbfJPP3E (ORCPT ); Wed, 16 Oct 2019 11:29:04 -0400 Received: by mail-ot1-f66.google.com with SMTP id 89so20486989oth.13 for ; Wed, 16 Oct 2019 08:29:03 -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=V9VEJ6qCsL2ywbrpNNXgyPcRNbaXwu3Y4oOlJhBpLzQ=; b=cDMLHUXZK9cMI2/GCB64rQqpH3gxjuGZNiLW7PVaJUUcrSTGnUd89F+fe1nuIvO0Fa dUVOOVGMVkibaDN2U3QOAKuVrnTDKzqEFFR4aRPZ+x4DUecvR60CxRXNHTaYUIryLWlY GP0IdCOYERcI8Sv+trmIiCysCspwk3tTYzMpuyqF8ghLI/dVaDkab1XBRbwsBWkiF7ri tlOtabO/vY2XtZYqGhMjmjj9D9JbBqqFeLrO5JRvnUjYRWlm+2w3z57IanSq6eVS05QI N9/5GCdaCrwm7FkqeDEFdHd+D4o4aPwI4+EQ5AGN/AEpcAyOr6hbMepo9So70Ps3W8/Q dWqQ== 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=V9VEJ6qCsL2ywbrpNNXgyPcRNbaXwu3Y4oOlJhBpLzQ=; b=P1YPJ/+tuaS2Mc/r8DPI9EO9hWTf7WkhPr+g3kPhEy8Tp4mKX9M1rrAeeI9V+3kQ+M R/TwGI86GxIRg3Nuv0//mu2R16tnDLOZqdONQh3/kFwmdcIekFNIIQVHPN5BfhUWSig6 fkI3KNgjDZNjQQcUEIyDee0qXe5KcKl4DNLZD0Figk0cIgVnBK0I+dlgTCLH79NoCpKo YaWJtA49Gwh+Mm/qwvx74UtUkOMgBT4CLQRc6bDafuZYrXl7DgGOrLxZFskT7OdQX9OM tVdoeNM3YW4DMRY33dcTyhePoKg8RW4srX/N0pyAEdLcGjXjwBBXW3HZHN+eukC/JDj5 esBQ== X-Gm-Message-State: APjAAAU7gFA0s9VFgHvGo18Xbo4MkKLMnFBzDaaN7Zlf9e3IBzyLFZEo xFb7u0HH52Vu1bmxK4BgIqcL35D10NikYlHJOAiStw== X-Received: by 2002:a9d:6c96:: with SMTP id c22mr3645106otr.194.1571239742813; Wed, 16 Oct 2019 08:29:02 -0700 (PDT) MIME-Version: 1.0 References: <20191015162300.22024-1-brgl@bgdev.pl> <20191015162300.22024-2-brgl@bgdev.pl> In-Reply-To: From: Bartosz Golaszewski Date: Wed, 16 Oct 2019 17:28:51 +0200 Message-ID: Subject: Re: [PATCH v2 1/6] dt-bindings: mfd: 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 , devicetree , "linux-kernel@vger.kernel.org" , Linux LED Subsystem , "open list:THERMAL" 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 =C5=9Br., 16 pa=C5=BA 2019 o 15:51 Rob Herring napisa= =C5=82(a): > > On Wed, Oct 16, 2019 at 7:55 AM Bartosz Golaszewski wrote= : > > > > wt., 15 pa=C5=BA 2019 o 23:17 Rob Herring napisa= =C5=82(a): > > > > > > On Tue, Oct 15, 2019 at 11:23 AM Bartosz Golaszewski = wrote: > > > > > > > > From: Bartosz Golaszewski > > > > > > > > Convert the binding document for MAX77650 core MFD module to YAML. > > > > > > > > Signed-off-by: Bartosz Golaszewski > > > > --- > > > > .../devicetree/bindings/mfd/max77650.txt | 47 +---------- > > > > .../devicetree/bindings/mfd/max77650.yaml | 83 +++++++++++++++= ++++ > > > > 2 files changed, 84 insertions(+), 46 deletions(-) > > > > create mode 100644 Documentation/devicetree/bindings/mfd/max77650.= yaml > > > > > > > > diff --git a/Documentation/devicetree/bindings/mfd/max77650.txt b/D= ocumentation/devicetree/bindings/mfd/max77650.txt > > > > index b529d8d19335..080871686b3b 100644 > > > > --- a/Documentation/devicetree/bindings/mfd/max77650.txt > > > > +++ b/Documentation/devicetree/bindings/mfd/max77650.txt > > > > @@ -1,46 +1 @@ > > > > -MAX77650 ultra low-power PMIC from Maxim Integrated. > > > > - > > > > -Required properties: > > > > -------------------- > > > > -- compatible: Must be "maxim,max77650" > > > > -- reg: I2C device address. > > > > -- interrupts: The interrupt on the parent the controller = is > > > > - connected to. > > > > -- interrupt-controller: Marks the device node as an interrupt cont= roller. > > > > -- #interrupt-cells: Must be <2>. > > > > - > > > > -- gpio-controller: Marks the device node as a gpio controller. > > > > -- #gpio-cells: Must be <2>. The first cell is the pin numb= er and > > > > - the second cell is used to specify the gpio= active > > > > - state. > > > > - > > > > -Optional properties: > > > > --------------------- > > > > -gpio-line-names: Single string containing the name of the GP= IO line. > > > > - > > > > -The GPIO-controller module is represented as part of the top-level= PMIC > > > > -node. The device exposes a single GPIO line. > > > > - > > > > -For device-tree bindings of other sub-modules (regulator, power su= pply, > > > > -LEDs and onkey) refer to the binding documents under the respectiv= e > > > > -sub-system directories. > > > > - > > > > -For more details on GPIO bindings, please refer to the generic GPI= O DT > > > > -binding document . > > > > - > > > > -Example: > > > > --------- > > > > - > > > > - pmic@48 { > > > > - compatible =3D "maxim,max77650"; > > > > - reg =3D <0x48>; > > > > - > > > > - interrupt-controller; > > > > - interrupt-parent =3D <&gpio2>; > > > > - #interrupt-cells =3D <2>; > > > > - interrupts =3D <3 IRQ_TYPE_LEVEL_LOW>; > > > > - > > > > - gpio-controller; > > > > - #gpio-cells =3D <2>; > > > > - gpio-line-names =3D "max77650-charger"; > > > > - }; > > > > +This file has been moved to max77650.yaml. > > > > diff --git a/Documentation/devicetree/bindings/mfd/max77650.yaml b/= Documentation/devicetree/bindings/mfd/max77650.yaml > > > > new file mode 100644 > > > > index 000000000000..5186ad287ec7 > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/mfd/max77650.yaml > > > > @@ -0,0 +1,83 @@ > > > > +# SPDX-License-Identifier: GPL-2.0 > > > > +%YAML 1.2 > > > > +--- > > > > +$id: http://devicetree.org/schemas/mfd/max77650.yaml# > > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > > + > > > > +title: MAX77650 ultra low-power PMIC from Maxim Integrated. > > > > + > > > > +maintainers: > > > > + - Bartosz Golaszewski > > > > + > > > > +description: | > > > > + This document describes the DT properties of the core MFD contro= ller. > > > > + > > > > + The GPIO-controller module is represented as part of the top-lev= el PMIC > > > > + node. The device exposes a single GPIO line. > > > > + > > > > + For device-tree bindings of other sub-modules (regulator, power = supply, > > > > + LEDs and onkey) refer to the binding documents under the respect= ive > > > > + sub-system directories. > > > > + > > > > + For more details on GPIO bindings, please refer to the generic G= PIO DT > > > > + binding document . > > > > + > > > > +properties: > > > > + compatible: > > > > + const: maxim,max77650 > > > > + > > > > + reg: > > > > + description: > > > > + I2C device address. > > > > + maxItems: 1 > > > > + > > > > + interrupts: > > > > + description: > > > > + The interrupt on the parent the controller is connected to. > > > > + maxItems: 1 > > > > + > > > > + interrupt-controller: true > > > > + > > > > + "#interrupt-cells": > > > > + const: 2 > > > > + description: > > > > + The first cell is the IRQ number, the second cell is the tri= gger type. > > > > + > > > > + gpio-controller: true > > > > + > > > > + "#gpio-cells": > > > > + const: 2 > > > > + description: > > > > + The first cell is the pin number and the second cell is used= to specify > > > > + the gpio active state. > > > > + > > > > + gpio-line-names: > > > > + $ref: '/schemas/types.yaml#/definitions/string-array' > > > > + maxItems: 1 > > > > + description: > > > > + Single string containing the name of the GPIO line. > > > > + > > > > +required: > > > > + - compatible > > > > + - reg > > > > + - interrupts > > > > + - interrupt-controller > > > > + - "#interrupt-cells" > > > > + - gpio-controller > > > > + - "#gpio-cells" > > > > + > > > > +examples: > > > > + - | > > > > + pmic@48 { > > > > + compatible =3D "maxim,max77650"; > > > > + reg =3D <0x48>; > > > > + > > > > + interrupt-controller; > > > > + interrupt-parent =3D <&gpio2>; > > > > + #interrupt-cells =3D <2>; > > > > + interrupts =3D <3 IRQ_TYPE_LEVEL_LOW>; > > > > > > Examples are built now. Run 'make dt_binding_check' on bindings befor= e > > > sending them: > > > > > > Error: Documentation/devicetree/bindings/mfd/max77650.example.dts:24.= 29-30 > > > syntax error > > > FATAL ERROR: Unable to parse input tree > > > scripts/Makefile.lib:321: recipe for target > > > 'Documentation/devicetree/bindings/mfd/max77650.example.dt.yaml' > > > failed > > > make[1]: *** [Documentation/devicetree/bindings/mfd/max77650.example.= dt.yaml] > > > Error 1 > > > > > > You need to include any includes that you use. > > > > > > Rob > > > > Hi Rob, > > > > thanks for the review. > > > > I'm on v5.4-rc3 and when running dt_binding_check, the error I'm > > getting is this: > > > > # make dt_binding_check > > DT_SCHEMA_FILES=3DDocumentation/devicetree/bindings/mfd/max77650.yaml > > SCHEMA Documentation/devicetree/bindings/processed-schema.yaml > > CHKDT Documentation/devicetree/bindings/mfd/max77650.yaml > > make[1]: *** No rule to make target > > 'Documentation/devicetree/bindings/mfd/max77650.example.dt.yaml', > > needed by '__build'. Stop. > > make: *** [Makefile:1263: dt_binding_check] Error 2 > > > > Is this caused by the same issue or am I missing something? > > I believe that's because dtc needs to be built with libyaml support. > Indeed, I didn't have the development package installed, but surprisingly I didn't get the warning from scripts/dtc/Makefile about that either. Bart > Rob