From nobody Tue Jun 30 19:10:19 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40F9AC433F5 for ; Tue, 11 Jan 2022 17:55:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344970AbiAKRzT (ORCPT ); Tue, 11 Jan 2022 12:55:19 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:33264 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344967AbiAKRzM (ORCPT ); Tue, 11 Jan 2022 12:55:12 -0500 Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 24DCC40047 for ; Tue, 11 Jan 2022 17:55:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1641923711; bh=00nwAyyKUb1y1BKsakD4Pry2fh6sP1JvtjwifpIg4ik=; h=From:To:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=l0V0PkkQf0NjI7ZoJLZqiHGxOuFXBkJE/A+9R536bi3h5PSB07mhmTn1hsSWhsvLz IV1RYNIOCIQWudatSJX39ucznKX2yG6unXeHGSjOsETzd1BH7pUnOI5G827Hil9otx gyTQGrsE0tBwhjNs8/0E5QV9IMoXEtf2CwDIHAdAqZyR/MCNJFU1Qg8q4MgatVzroP bu9mk+hAtELhWW+ykqI4df+liqjLBj6YAJcsCLDdlyr1uX4R7wmdS3NdudubZywpBo s2Qwg4Gz274aeEEVOxDIQD6EKltXIC9jB8mFaIWfLiPh0HCjHAARck6+tuAHgLiUdB Dogqx/L+cX9eQ== Received: by mail-ed1-f71.google.com with SMTP id q15-20020a056402518f00b003f87abf9c37so13992613edd.15 for ; Tue, 11 Jan 2022 09:55:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=00nwAyyKUb1y1BKsakD4Pry2fh6sP1JvtjwifpIg4ik=; b=hAH63s1mfF80GrpuV3o7qUxNWC4AZLcMWTUrhy4as6uFtIHcUjGnNE20EDB+81YX22 F7Oq7sQKqg3XD9aZl3X59M2k5saJCq0P4Gou74h6ewzUYV7gFI8KMH8iLamk156Ef64z O9JmMx0IrD2wL4UiX9AWpi9ISrgx0tn2XA2eqtxAvaUtlvpI2nch5qbY0gdC709gf9+j jF33FM8WoeAE+QHikhPeQCRW4DGX3aQU9kcDo17acgO6mvrtu6VktYoCycZaMJXwPNj3 X7OvsUFzg8I/3MXesEmiA6VCDUlvKqyhENxNQEhgCLMj9lGeh79uNOxbWKpMgfPOFZ7j 3BMg== X-Gm-Message-State: AOAM531/FLIUFkjOPurV+IFiwjngDCBSUECrbhD4c482aJwwRGqnFd3H h8ZLCOClUDprDFUPCLTA85Gj2bb4sts31dE9sFuJ1oOhtS5SgKyzjtR0wQZOeJSK2OB82636/Rl fryQP8bpO++vg+8DmnJKHZt6EeThdkqE6d3aYluSmxg== X-Received: by 2002:a05:6402:34c6:: with SMTP id w6mr5155568edc.228.1641923709774; Tue, 11 Jan 2022 09:55:09 -0800 (PST) X-Google-Smtp-Source: ABdhPJy6iz+h/3L17VQaGmv4x06QQw3Odv8DjLRkuLfTCsHFYjFDxCI19Lcubysme4JBSoX9Cc62WA== X-Received: by 2002:a05:6402:34c6:: with SMTP id w6mr5155542edc.228.1641923709492; Tue, 11 Jan 2022 09:55:09 -0800 (PST) Received: from localhost.localdomain (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id 7sm3759949ejh.161.2022.01.11.09.55.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 09:55:08 -0800 (PST) From: Krzysztof Kozlowski To: Pavel Machek , Rob Herring , Lee Jones , Javier Martinez Canillas , Liam Girdwood , Mark Brown , Jacek Anaszewski , Krzysztof Kozlowski , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 1/3] regulator: dt-bindings: maxim,max77802: convert to dtschema Date: Tue, 11 Jan 2022 18:54:28 +0100 Message-Id: <20220111175430.224421-2-krzysztof.kozlowski@canonical.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> References: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" Convert the regulators of Maxim MAX77802 PMIC to DT schema format. Signed-off-by: Krzysztof Kozlowski Acked-by: Mark Brown Reviewed-by: Javier Martinez Canillas Reviewed-by: Rob Herring --- .../bindings/regulator/max77802.txt | 111 ------------------ .../bindings/regulator/maxim,max77802.yaml | 97 +++++++++++++++ 2 files changed, 97 insertions(+), 111 deletions(-) delete mode 100644 Documentation/devicetree/bindings/regulator/max77802.txt create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77= 802.yaml diff --git a/Documentation/devicetree/bindings/regulator/max77802.txt b/Doc= umentation/devicetree/bindings/regulator/max77802.txt deleted file mode 100644 index b82943d83677..000000000000 --- a/Documentation/devicetree/bindings/regulator/max77802.txt +++ /dev/null @@ -1,111 +0,0 @@ -Binding for Maxim MAX77802 regulators - -This is a part of device tree bindings of MAX77802 multi-function device. -More information can be found in bindings/mfd/max77802.txt file. - -The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO) -regulators that can be controlled over I2C. - -Following properties should be present in main device node of the MFD chip. - -Optional properties: -- inb1-supply: The input supply for BUCK1 -- inb2-supply: The input supply for BUCK2 -- inb3-supply: The input supply for BUCK3 -- inb4-supply: The input supply for BUCK4 -- inb5-supply: The input supply for BUCK5 -- inb6-supply: The input supply for BUCK6 -- inb7-supply: The input supply for BUCK7 -- inb8-supply: The input supply for BUCK8 -- inb9-supply: The input supply for BUCK9 -- inb10-supply: The input supply for BUCK10 -- inl1-supply: The input supply for LDO8 and LDO15 -- inl2-supply: The input supply for LDO17, LDO27, LDO30 and LDO35 -- inl3-supply: The input supply for LDO3, LDO5, LDO6 and LDO7 -- inl4-supply: The input supply for LDO10, LDO11, LDO13 and LDO14 -- inl5-supply: The input supply for LDO9 and LDO19 -- inl6-supply: The input supply for LDO4, LDO21, LDO24 and LDO33 -- inl7-supply: The input supply for LDO18, LDO20, LDO28 and LDO29 -- inl9-supply: The input supply for LDO12, LDO23, LDO25, LDO26, LDO32 and= LDO34 -- inl10-supply: The input supply for LDO1 and LDO2 - -Optional nodes: -- regulators : The regulators of max77802 have to be instantiated - under subnode named "regulators" using the following format. - - regulator-name { - standard regulator constraints.... - }; - refer Documentation/devicetree/bindings/regulator/regulator.txt - -The regulator node name should be initialized with a string to get matched -with their hardware counterparts as follow. The valid names are: - - -LDOn : for LDOs, where n can lie in ranges 1-15, 17-21, 23-30 - and 32-35. - example: LDO1, LDO2, LDO35. - -BUCKn : for BUCKs, where n can lie in range 1 to 10. - example: BUCK1, BUCK5, BUCK10. - -The max77802 regulator supports two different operating modes: Normal and = Low -Power Mode. Some regulators support the modes to be changed at startup or = by -the consumers during normal operation while others only support to change = the -mode during system suspend. The standard regulator suspend states binding = can -be used to configure the regulator operating mode. - -The regulators that support the standard "regulator-initial-mode" property, -changing their mode during normal operation are: LDOs 1, 3, 20 and 21. - -The possible values for "regulator-initial-mode" and "regulator-mode" are: - 1: Normal regulator voltage output mode. - 3: Low Power which reduces the quiescent current down to only 1uA - -The valid modes list is defined in the dt-bindings/regulator/maxim,max7780= 2.h -header and can be included by device tree source files. - -The standard "regulator-mode" property can only be used for regulators that -support changing their mode to Low Power Mode during suspend. These regula= tors -are: BUCKs 2-4 and LDOs 1-35. Also, it only takes effect if the regulator = has -been enabled for the given suspend state using "regulator-on-in-suspend" a= nd -has not been disabled for that state using "regulator-off-in-suspend". - -Example: - - max77802@9 { - compatible =3D "maxim,max77802"; - interrupt-parent =3D <&wakeup_eint>; - interrupts =3D <26 0>; - reg =3D <0x09>; - #address-cells =3D <1>; - #size-cells =3D <0>; - - inb1-supply =3D <&parent_reg>; - - regulators { - ldo1_reg: LDO1 { - regulator-name =3D "vdd_1v0"; - regulator-min-microvolt =3D <1000000>; - regulator-max-microvolt =3D <1000000>; - regulator-always-on; - regulator-initial-mode =3D ; - }; - - ldo11_reg: LDO11 { - regulator-name =3D "vdd_ldo11"; - regulator-min-microvolt =3D <1900000>; - regulator-max-microvolt =3D <1900000>; - regulator-always-on; - regulator-state-mem { - regulator-on-in-suspend; - regulator-mode =3D ; - }; - }; - - buck1_reg: BUCK1 { - regulator-name =3D "vdd_mif"; - regulator-min-microvolt =3D <950000>; - regulator-max-microvolt =3D <1300000>; - regulator-always-on; - regulator-boot-on; - }; - }; diff --git a/Documentation/devicetree/bindings/regulator/maxim,max77802.yam= l b/Documentation/devicetree/bindings/regulator/maxim,max77802.yaml new file mode 100644 index 000000000000..a40c93259a13 --- /dev/null +++ b/Documentation/devicetree/bindings/regulator/maxim,max77802.yaml @@ -0,0 +1,97 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/regulator/maxim,max77802.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Maxim MAX77802 Power Management IC regulators + +maintainers: + - Javier Martinez Canillas + - Krzysztof Kozlowski + +description: | + This is a part of device tree bindings for Maxim MAX77802 Power Manageme= nt + Integrated Circuit (PMIC). + + The Maxim MAX77686 provides 10 high-efficiency Buck and 32 Low-DropOut (= LDO) + regulators. + + See also Documentation/devicetree/bindings/mfd/maxim,max77802.yaml for + additional information and example. + + Certain regulators support "regulator-initial-mode" and "regulator-mode". + The valid modes list is defined in the dt-bindings/regulator/maxim,max77= 802.h + and their meaning is: + 1 - Normal regulator voltage output mode. + 3 - Low Power which reduces the quiescent current down to only 1uA + + The standard "regulator-mode" property can only be used for regulators t= hat + support changing their mode to Low Power Mode during suspend. These + regulators are: bucks 2-4 and LDOs 1-35. Also, it only takes effect if t= he + regulator has been enabled for the given suspend state using + "regulator-on-in-suspend" and has not been disabled for that state using + "regulator-off-in-suspend". + +patternProperties: + # LDO1, LDO3, LDO20, LDO21 + "^LDO([13]|2[01])$": + type: object + $ref: regulator.yaml# + unevaluatedProperties: false + description: + LDOs supporting the regulator-initial-mode property and changing the= ir + mode during normal operation. + + required: + - regulator-name + + # LDO2, LDO4-15, LDO17-19, LDO23-30, LDO32-35 + "^LDO([24-9]|1[0-5789]|2[3-9]|3[02345])$": + type: object + $ref: regulator.yaml# + unevaluatedProperties: false + description: + LDOs supporting the regulator-mode property (changing mode to Low Po= wer + Mode during suspend). + + properties: + regulator-initial-mode: false + + required: + - regulator-name + + # buck2-4 + "^BUCK[2-4]$": + type: object + $ref: regulator.yaml# + unevaluatedProperties: false + description: + bucks supporting the regulator-mode property (changing mode to Low P= ower + Mode during suspend). + + properties: + regulator-initial-mode: false + + required: + - regulator-name + + # buck1, buck5-10 + "^BUCK([15-9]|10)$": + type: object + $ref: regulator.yaml# + unevaluatedProperties: false + + properties: + regulator-initial-mode: false + + patternProperties: + regulator-state-(standby|mem|disk): + type: object + properties: + regulator-mode: false + + required: + - regulator-name + +additionalProperties: false --=20 2.32.0 From nobody Tue Jun 30 19:10:19 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F738C433EF for ; Tue, 11 Jan 2022 17:55:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345142AbiAKRzv (ORCPT ); Tue, 11 Jan 2022 12:55:51 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:54364 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344974AbiAKRzP (ORCPT ); Tue, 11 Jan 2022 12:55:15 -0500 Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 7A8A84005A for ; Tue, 11 Jan 2022 17:55:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1641923714; bh=yLkZ3N1YGlON76aOjFtdwlmbLegMSMiHS0/fbiZm/ts=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=stt4OaoWJqhH2ysWs7A04TO8qJFiteD5Gm5AFyF/vq/C80hr3wEntDCINeTa6NbW1 zYR09kmYR0kOmNCfidH3n14OkJ+BX5cgwMlaGObbWbeBWsFbnr+fmlJ1CwbrEudfbN taYznT2ryeHp4pd3TeKamQ2ys+WF7FUzO7g4+p/hHhg4f9ApLAjN8YbPjNa4aGxjAx diy9VzRQf0907/A/7IS2EsuyzQZKJ1cr9PrPEtXWkOPQSl/eimO18xZmzB1oK3kxns gvpGuuhluGRY60sbfBVvdEusWOa6k6q0mWFh8k1oJNmkH79m/OD7U00YKILaJsNQMV USCV43TcGFw/A== Received: by mail-ed1-f70.google.com with SMTP id eg24-20020a056402289800b003fe7f91df01so5013836edb.6 for ; Tue, 11 Jan 2022 09:55:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=yLkZ3N1YGlON76aOjFtdwlmbLegMSMiHS0/fbiZm/ts=; b=2Y8sSrvRm6+xmvqGRBUykmcW8DT/5D0LqTvl5S4UZLdSpM+z+WgpNn6C4oWpQYMBoZ QAbwOtr3/XpA2ciUod59yCaG2mgTk9d3U066Uqp+tLrVU9E986Jol6qLg/3W0B9uIrOg EhGbEAZHF9KLho5UD1kZxKYcE1QossdYOx6eftxjcRnqUgiGePVnwW8jXVTr4YolMs4k +kSqPBMY7ynnFqsARX+FG1VWnPpFu7+naK5r8OMnYx2kNOq6YhTJM2QmlphkBHrNJXtA 1Xa6pneNIvx10RcSkaZIGcsBm3p2Pxi24nogXuTh/div+QyLw/Nl/F286sRbNuXKrWZh q22g== X-Gm-Message-State: AOAM532ro4gjWI9N8CkdWl93VVXqO7jTlTtwHJLTWLmeOXXihZnKdx9q qjZZf1oxq3LCKtVR01Yrjroese/IFdDaMAGzMLj1J9Srs1wBCmMgcuNdNeGdS2vaEepdsRWMH3O yNuP3lRLxZHcGn7oHuEpIrMm4aPDSXQ/YSFoUhGtc8A== X-Received: by 2002:a17:907:8694:: with SMTP id qa20mr4701275ejc.378.1641923713209; Tue, 11 Jan 2022 09:55:13 -0800 (PST) X-Google-Smtp-Source: ABdhPJwGwSaoF6MY7oHvtxLZ7PMNUOIa6JgigH0+R24JIzl2v20ITlookaN2yzo30wfbhgVnIsnf5w== X-Received: by 2002:a17:907:8694:: with SMTP id qa20mr4701258ejc.378.1641923712931; Tue, 11 Jan 2022 09:55:12 -0800 (PST) Received: from localhost.localdomain (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id 7sm3759949ejh.161.2022.01.11.09.55.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 09:55:10 -0800 (PST) From: Krzysztof Kozlowski To: Pavel Machek , Rob Herring , Lee Jones , Javier Martinez Canillas , Liam Girdwood , Mark Brown , Jacek Anaszewski , Krzysztof Kozlowski , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Rob Herring Subject: [PATCH v2 2/3] dt-bindings: mfd: maxim,max77802: convert to dtschema Date: Tue, 11 Jan 2022 18:54:29 +0100 Message-Id: <20220111175430.224421-3-krzysztof.kozlowski@canonical.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> References: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" Convert the MFD part of Maxim MAX77802 PMIC to DT schema format. The example DTS was copied from existing DTS (exynos5800-peach-pi.dts), so keep the license as GPL-2.0-only. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Rob Herring Reviewed-by: Javier Martinez Canillas --- .../devicetree/bindings/mfd/max77802.txt | 25 --- .../bindings/mfd/maxim,max77802.yaml | 194 ++++++++++++++++++ MAINTAINERS | 2 +- 3 files changed, 195 insertions(+), 26 deletions(-) delete mode 100644 Documentation/devicetree/bindings/mfd/max77802.txt create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77802.ya= ml diff --git a/Documentation/devicetree/bindings/mfd/max77802.txt b/Documenta= tion/devicetree/bindings/mfd/max77802.txt deleted file mode 100644 index 09decac20d91..000000000000 --- a/Documentation/devicetree/bindings/mfd/max77802.txt +++ /dev/null @@ -1,25 +0,0 @@ -Maxim MAX77802 multi-function device - -The Maxim MAX77802 is a Power Management IC (PMIC) that contains 10 high -efficiency Buck regulators, 32 Low-DropOut (LDO) regulators used to power -up application processors and peripherals, a 2-channel 32kHz clock outputs, -a Real-Time-Clock (RTC) and a I2C interface to program the individual -regulators, clocks outputs and the RTC. - -Bindings for the built-in 32k clock generator block and -regulators are defined in ../clk/maxim,max77802.txt and -../regulator/max77802.txt respectively. - -Required properties: -- compatible : Must be "maxim,max77802" -- reg : Specifies the I2C slave address of PMIC block. -- interrupts : I2C device IRQ line connected to the main SoC. - -Example: - - max77802: pmic@9 { - compatible =3D "maxim,max77802"; - interrupt-parent =3D <&intc>; - interrupts =3D <26 IRQ_TYPE_NONE>; - reg =3D <0x09>; - }; diff --git a/Documentation/devicetree/bindings/mfd/maxim,max77802.yaml b/Do= cumentation/devicetree/bindings/mfd/maxim,max77802.yaml new file mode 100644 index 000000000000..baa1346ac5d5 --- /dev/null +++ b/Documentation/devicetree/bindings/mfd/maxim,max77802.yaml @@ -0,0 +1,194 @@ +# SPDX-License-Identifier: GPL-2.0-only +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/mfd/maxim,max77802.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Maxim MAX77802 Power Management IC + +maintainers: + - Javier Martinez Canillas + - Krzysztof Kozlowski + +description: | + This is a part of device tree bindings for Maxim MAX77802 Power Manageme= nt + Integrated Circuit (PMIC). + + The Maxim MAX77802 is a Power Management IC which includes voltage and + current regulators (10 high efficiency Buck regulators and 32 Low-DropOut + (LDO)), RTC and clock outputs. + + The MAX77802 provides two 32.768khz clock outputs that can be controlled + (gated/ungated) over I2C. The clock IDs are defined as preprocessor mac= ros + in dt-bindings/clock/maxim,max77802.h. + +properties: + compatible: + const: maxim,max77802 + + '#clock-cells': + const: 1 + + interrupts: + maxItems: 1 + + reg: + maxItems: 1 + + regulators: + $ref: /schemas/regulator/maxim,max77802.yaml + description: + List of child nodes that specify the regulators. + + inb1-supply: + description: Power supply for buck1 + inb2-supply: + description: Power supply for buck2 + inb3-supply: + description: Power supply for buck3 + inb4-supply: + description: Power supply for buck4 + inb5-supply: + description: Power supply for buck5 + inb6-supply: + description: Power supply for buck6 + inb7-supply: + description: Power supply for buck7 + inb8-supply: + description: Power supply for buck8 + inb9-supply: + description: Power supply for buck9 + inb10-supply: + description: Power supply for buck10 + + inl1-supply: + description: Power supply for LDO8, LDO15 + inl2-supply: + description: Power supply for LDO17, LDO27, LDO30, LDO35 + inl3-supply: + description: Power supply for LDO3, LDO5, LDO7, LDO7 + inl4-supply: + description: Power supply for LDO10, LDO11, LDO13, LDO14 + inl5-supply: + description: Power supply for LDO9, LDO19 + inl6-supply: + description: Power supply for LDO4, LDO21, LDO24, LDO33 + inl7-supply: + description: Power supply for LDO18, LDO20, LDO28, LDO29 + inl9-supply: + description: Power supply for LDO12, LDO23, LDO25, LDO26, LDO32, LDO34 + inl10-supply: + description: Power supply for LDO1, LDO2 + + wakeup-source: true + +required: + - compatible + - '#clock-cells' + - reg + +additionalProperties: false + +examples: + - | + #include + #include + + i2c { + #address-cells =3D <1>; + #size-cells =3D <0>; + + pmic@9 { + compatible =3D "maxim,max77802"; + interrupt-parent =3D <&gpx3>; + interrupts =3D <1 IRQ_TYPE_NONE>; + pinctrl-names =3D "default"; + pinctrl-0 =3D <&max77802_irq>, <&pmic_selb>, + <&pmic_dvs_1>, <&pmic_dvs_2>, <&pmic_dvs_3>; + wakeup-source; + reg =3D <0x9>; + #clock-cells =3D <1>; + + inb1-supply =3D <&tps65090_dcdc2>; + inb2-supply =3D <&tps65090_dcdc1>; + inb3-supply =3D <&tps65090_dcdc2>; + inb4-supply =3D <&tps65090_dcdc2>; + inb5-supply =3D <&tps65090_dcdc1>; + inb6-supply =3D <&tps65090_dcdc2>; + inb7-supply =3D <&tps65090_dcdc1>; + inb8-supply =3D <&tps65090_dcdc1>; + inb9-supply =3D <&tps65090_dcdc1>; + inb10-supply =3D <&tps65090_dcdc1>; + + inl1-supply =3D <&buck5_reg>; + inl2-supply =3D <&buck7_reg>; + inl3-supply =3D <&buck9_reg>; + inl4-supply =3D <&buck9_reg>; + inl5-supply =3D <&buck9_reg>; + inl6-supply =3D <&tps65090_dcdc2>; + inl7-supply =3D <&buck9_reg>; + inl9-supply =3D <&tps65090_dcdc2>; + inl10-supply =3D <&buck7_reg>; + + regulators { + BUCK1 { + regulator-name =3D "vdd_mif"; + regulator-min-microvolt =3D <800000>; + regulator-max-microvolt =3D <1300000>; + regulator-always-on; + regulator-boot-on; + regulator-ramp-delay =3D <12500>; + regulator-state-mem { + regulator-off-in-suspend; + }; + }; + + BUCK2 { + regulator-name =3D "vdd_arm"; + regulator-min-microvolt =3D <800000>; + regulator-max-microvolt =3D <1500000>; + regulator-always-on; + regulator-boot-on; + regulator-ramp-delay =3D <12500>; + regulator-coupled-with =3D <&buck3_reg>; + regulator-coupled-max-spread =3D <300000>; + regulator-state-mem { + regulator-off-in-suspend; + }; + }; + + // ... + + BUCK10 { + regulator-name =3D "vdd_1v8"; + regulator-min-microvolt =3D <1800000>; + regulator-max-microvolt =3D <1800000>; + regulator-always-on; + regulator-boot-on; + regulator-state-mem { + regulator-on-in-suspend; + }; + }; + + LDO1 { + regulator-name =3D "vdd_1v0"; + regulator-min-microvolt =3D <1000000>; + regulator-max-microvolt =3D <1000000>; + regulator-always-on; + regulator-initial-mode =3D ; + regulator-state-mem { + regulator-on-in-suspend; + regulator-mode =3D ; + }; + }; + + // ... + + LDO35 { + regulator-name =3D "ldo_35"; + regulator-min-microvolt =3D <1200000>; + regulator-max-microvolt =3D <1200000>; + }; + }; + }; + }; diff --git a/MAINTAINERS b/MAINTAINERS index 5ea5655a29c3..b5e4f14f6768 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -11666,7 +11666,7 @@ MAXIM MAX77802 PMIC REGULATOR DEVICE DRIVER M: Javier Martinez Canillas L: linux-kernel@vger.kernel.org S: Supported -F: Documentation/devicetree/bindings/*/*max77802.txt +F: Documentation/devicetree/bindings/*/*max77802.yaml F: drivers/regulator/max77802-regulator.c F: include/dt-bindings/*/*max77802.h =20 --=20 2.32.0 From nobody Tue Jun 30 19:10:19 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96DD1C433EF for ; Tue, 11 Jan 2022 17:56:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345180AbiAKR4A (ORCPT ); Tue, 11 Jan 2022 12:56:00 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:54378 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344990AbiAKRzQ (ORCPT ); Tue, 11 Jan 2022 12:55:16 -0500 Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 9B5803FFD9 for ; Tue, 11 Jan 2022 17:55:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1641923715; bh=BmB9cazi0hKFnRyUoCMsTBlnp9i8I7ETkGf9B7rE1rY=; h=From:To:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=S44c47PptfO81kBVgbL9cifo7+YZos/J9DLX/XHsQ6BD/C8qarPVn3EmEW0e3hibw 4K8Ts0nc1IKQtOLXrVc2aQhavQMYJ8ruAgEQqckZZ9hDvwq03tpYLqFUIpe9hWphIY RzMa/O9AqVLcCzeW9RnDrNwQrUfrY2mvy82Z8NHMAKlooP8eMEcDRI8zTSHFdRU/0P pdYidDsZQlMaIntvN5aOHw7my+CbiCj8dXsh6ve07SCVFMq+BFU/JAHEM8oWEiC6k0 bG+1owBR2g3Gaio66E/ti4xPlR5nYAIFavbWEqvy7DYHBu18HsMfybIEel2Ud/fD21 eIsy6ZEuxu6FA== Received: by mail-ed1-f71.google.com with SMTP id q15-20020a056402518f00b003f87abf9c37so13992816edd.15 for ; Tue, 11 Jan 2022 09:55:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=BmB9cazi0hKFnRyUoCMsTBlnp9i8I7ETkGf9B7rE1rY=; b=tn1qZYypjsLv3vOUhM/6ugLhosL4OhKL1A3gAYpGTJO8VgygFEroVSsOoOfzxonppE gkW1JAo+JR9Vfj6q9uhe8ndvvkS88vhMssICZFh2AT58GPerM89zvt5SmS0mnPP4SsBb ojIeiCrF20akFJJLVvHf20ZH5T3ScFwfV9spijqkFhdXxO9/mEP1JTzxvFGzbMBYnGf7 7a4XZUdVqcjTD5tORpbJ8ZTgjQBhmAc+IhKgt7gsCMRL4DxonTOyy5YIo4eiujFtmqnX ArlIp3jExM9TxVKl4emYJZaNcT4CturjTTzdj63e7dQCus9ghIPn2Yk3dn31REsZ6iZx bfbA== X-Gm-Message-State: AOAM532GFKMhDziuYAIbnkcvL5Sk+XGY08sEcECQveou9S5otXfUDc3F 64rL6336vaNzEe2ov3UHKS0S8pIGux797i2OdnCG/tWNi6h0y+fB3xATVuA71t4GaJ/MP09qu5J mjWo7gzUuWzb5HYWXES1g1zu8yJ577r13lQgZIJblPw== X-Received: by 2002:a17:907:7f05:: with SMTP id qf5mr4531075ejc.597.1641923715344; Tue, 11 Jan 2022 09:55:15 -0800 (PST) X-Google-Smtp-Source: ABdhPJxJCLUIrpEiP8qBwAD5GuOZRfnAaOXhGkc/rX1rQBiOtBHZz62WPoiPD24pySPPRqGLiXonwQ== X-Received: by 2002:a17:907:7f05:: with SMTP id qf5mr4531069ejc.597.1641923715169; Tue, 11 Jan 2022 09:55:15 -0800 (PST) Received: from localhost.localdomain (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id 7sm3759949ejh.161.2022.01.11.09.55.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 09:55:13 -0800 (PST) From: Krzysztof Kozlowski To: Pavel Machek , Rob Herring , Lee Jones , Javier Martinez Canillas , Liam Girdwood , Mark Brown , Jacek Anaszewski , Krzysztof Kozlowski , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 3/3] dt-bindings: leds: common: fix unit address in max77693 example Date: Tue, 11 Jan 2022 18:54:30 +0100 Message-Id: <20220111175430.224421-4-krzysztof.kozlowski@canonical.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> References: <20220111175430.224421-1-krzysztof.kozlowski@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" The max77693 LED device node should not take an unit address, because it is instantiated from a max77693 I2C parent device node. This also splits all examples to separate DTS examples because they are actually independent. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Javier Martinez Canillas Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/leds/common.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documenta= tion/devicetree/bindings/leds/common.yaml index 697102707703..328952d7acbb 100644 --- a/Documentation/devicetree/bindings/leds/common.yaml +++ b/Documentation/devicetree/bindings/leds/common.yaml @@ -185,9 +185,11 @@ examples: }; }; =20 - led-controller@0 { + - | + #include + + led-controller { compatible =3D "maxim,max77693-led"; - reg =3D <0 0x100>; =20 led { function =3D LED_FUNCTION_FLASH; @@ -199,6 +201,9 @@ examples: }; }; =20 + - | + #include + i2c { #address-cells =3D <1>; #size-cells =3D <0>; --=20 2.32.0