From nobody Tue Apr 7 18:03:28 2026 Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com [209.85.128.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D6BFD30B502 for ; Mon, 6 Apr 2026 07:51:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.50 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775461891; cv=none; b=ihQE3ghis+YosIYGbRGL7PW9UcMej8544bLpeFFwaLt3RjAtPe0PdX0bG+IYVHpeINHAOGWHLVhq7N0QWWiPEYCwDWNOFQUeYdsVzsp/MkXxpmJc4bqH9XQFv8ALC5kQu8RYkBm8gJuDgVo6RLkUUXe5EkL1wip5vbDHKGic8N8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775461891; c=relaxed/simple; bh=LbDcwJqJ3hApWhOjg/1ArXaMfQa98m0EF2RkLmBRHCU=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=YvMIIlEwdQzqnLoDVcAUkUpGloOFxis1wrpVv21YPEeFwfmISgiJ9qMlZ45re7DeTP4KqumBNhovvsI/5FX+CIrcCSJyhMMPXd6Z4tZcNiEyYVS7wgIX8J+O/GvBWl5YNbT87ncW6NKrKjdFReq89tfak0ZnJPpsKz5dW1vb1hM= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=l/7oukeh; arc=none smtp.client-ip=209.85.128.50 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="l/7oukeh" Received: by mail-wm1-f50.google.com with SMTP id 5b1f17b1804b1-488971db0fdso25767225e9.0 for ; Mon, 06 Apr 2026 00:51:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1775461888; x=1776066688; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=IvnYBColS2NJ2nRJ9xcjChL7NS5bCiTG1wTopgEGQoA=; b=l/7oukehDTJtGLXljrZiNgSlZyBrjyu75VEhbW1BJcLG1XdFVicsKyQY0HIJFS/yfg TZItH8Cwv8XaeaoqtMmgL7f7BR/qFqVSXep0vG1G2Er7eYIdgsTOQqQsLwP02EbwzN30 ZZX+FatXxmsmTRuOnkv+l0e3D2sCeRDJ7GWTmEM7KPVVE9xUdoKvqMAhm6Hf0Q3z5vig EkYMlGyOqZwSFQc7Edt85q1SQRsznjLtZHe2MpXQenfHPOeLjmZCqlPlZN5s4Wznmq0a vHLgxD6KxBVWoJDPVsleblN+9hxnrozKMJEi9H2aHgusTDExCFFWU2W/rqtmFbzq9Ivz mtSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775461888; x=1776066688; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=IvnYBColS2NJ2nRJ9xcjChL7NS5bCiTG1wTopgEGQoA=; b=UKiXLgL7PCL7rApTNUzcznUKGBdV9lq0KuUcg3FpOyKl44oej6FaO1JWaivHjMLNHq wriColqLW687J1MVIJnzjXMGtOPNHV9JKmYyWE0NNYfZt/ECUjYcEq+DCqPQQbg1g5y3 Nbo+pCq5w8vD3fpajt2Dtnc8O25qO6LwMN9J6SM6sH9hPAFOcYtAbp9JlAYX8xwGMbJT BkcQK/pGgNvH2kQYp5pF+k7i87YyQgvt0fUYOyoxd/koorir6LG6Rw6wdIEcO6Sw9+44 rICVbIt9cApt0UCiI0FMUWWkaIUL1rOTLjxouohn/vFI9mdXYlfrm6BcyN1uJsw9gxUX pWKw== X-Forwarded-Encrypted: i=1; AJvYcCXcZHNJwdDcwXs44UtU57HVEs07TPnyMqMiu0WKtVLwHKtmwSA2M65T2po3QTKE+cvuan8xR3O9jASSLU8=@vger.kernel.org X-Gm-Message-State: AOJu0YybIz7LbqeAiLAZwc2l6/GbWw2VoMo3ssGnYr/d3Y8dMNoLfWaV /kXcd/LLjHoDl65O8tk7FeoszU5w2fxUdkqe8DaA717l2/9lCqA7xSlK X-Gm-Gg: AeBDieurajnfDjH+a8Z/fU4Y2LBSXwwuGizRUXIrBku2xpXr2Zfbu/LeoZN4fCWVZbw YEFXCSq3ML/ZRwJHD9yXyWhbPGyN3VQs2HxRWUwvMbduz+6fiilwvGk/yMpyJoaVLtAvrEEneBF KV07bRo0dcZfQESdMENoP0aYgnGK0d1qFVzS2U0QcHcvVJyMT/pSjmnfqI+eovzQystMwF1MfN2 I5UiQFeYeY8UkXqzFxtcn/SnfhxWHREByfTE3WfIGSOr9HiAWVEV10DpW3PWbU+1XsYtBTiMcy4 4K5CN+KG9+8BHxaeZ2AoYLbI/4G1LqgV8zP+YskxQgDe0009QIuDO91J5gPgZCGLibitFWLQnz4 aLsC0HN8xh2hJe8NmL71CofvmI/TxAyLXvC/uhY1RjLUp1gLOUpvw2nTW/OuSqSLaOd52JZ9EPI IBev8gTIMEKyt4 X-Received: by 2002:a05:600c:a414:b0:488:b2bd:bd5d with SMTP id 5b1f17b1804b1-488b2bdc0c5mr20479025e9.6.1775461887943; Mon, 06 Apr 2026 00:51:27 -0700 (PDT) Received: from xeon ([188.163.112.56]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-488b739e00bsm20393525e9.10.2026.04.06.00.51.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Apr 2026 00:51:27 -0700 (PDT) From: Svyatoslav Ryhel To: Linus Walleij , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Liam Girdwood , Mark Brown , Svyatoslav Ryhel Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v5 1/2] regulator: dt-bindings: regulator-max77620: convert to DT schema Date: Mon, 6 Apr 2026 10:51:13 +0300 Message-ID: <20260406075114.25672-2-clamor95@gmail.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260406075114.25672-1-clamor95@gmail.com> References: <20260406075114.25672-1-clamor95@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Convert regulator-max77620 devicetree bindings for the MAX77620 PMIC from TXT to YAML format. This patch does not change any functionality; the bindings remain the same. Signed-off-by: Svyatoslav Ryhel Acked-by: Mark Brown Reviewed-by: Rob Herring (Arm) --- .../regulator/maxim,max77620-regulator.yaml | 99 ++++++++ .../bindings/regulator/regulator-max77620.txt | 222 ------------------ 2 files changed, 99 insertions(+), 222 deletions(-) create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77= 620-regulator.yaml delete mode 100644 Documentation/devicetree/bindings/regulator/regulator-m= ax77620.txt diff --git a/Documentation/devicetree/bindings/regulator/maxim,max77620-reg= ulator.yaml b/Documentation/devicetree/bindings/regulator/maxim,max77620-re= gulator.yaml new file mode 100644 index 000000000000..7118c34961ba --- /dev/null +++ b/Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.= yaml @@ -0,0 +1,99 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/regulator/maxim,max77620-regulator.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Regulator for MAX77620 Power management IC from Maxim Semiconductor. + +maintainers: + - Svyatoslav Ryhel + +description: + Device has multiple DCDC(sd[0-3]) and LDOs(ldo[0-8]). The input supply + of these regulators are defined under parent device node. Details of + regulator properties are defined as child node under sub-node "regulator= s" + which is child node of device node. + +patternProperties: + "^in-(sd[0-3]|ldo(0-1|2|3-5|4-6|7-8))-supply$": + $ref: /schemas/types.yaml#/definitions/phandle + description: Input supply for DCDC or LDO + + "^(sd[0-3]|ldo[0-8])$": + type: object + $ref: /schemas/regulator/regulator.yaml# + unevaluatedProperties: false + + properties: + maxim,active-fps-source: + $ref: /schemas/types.yaml#/definitions/uint32 + description: | + FPS source for the GPIOs to get enabled/disabled when system is = in + active state. Valid values are: + - MAX77620_FPS_SRC_0: FPS source is FPS0. + - MAX77620_FPS_SRC_1: FPS source is FPS1 + - MAX77620_FPS_SRC_2: FPS source is FPS2 + - MAX77620_FPS_SRC_NONE: GPIO is not controlled by FPS events and + it gets enabled/disabled by register ac= cess. + Absence of this property will leave the FPS configuration regist= er + for that GPIO to default configuration. + + maxim,active-fps-power-up-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Sequencing event slot number on which the GPIO get enabled when + master FPS input event set to HIGH. This is applicable if FPS so= urce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,active-fps-power-down-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Sequencing event slot number on which the GPIO get disabled when + master FPS input event set to LOW. This is applicable if FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,suspend-fps-source: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-source" but value get + configured when system enters in to suspend state. + + maxim,suspend-fps-power-up-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-power-up-slot" but th= is + value get configured into FPS configuration register when system + enters into suspend. This is applicable if suspend state FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,suspend-fps-power-down-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-power-down-slot" but = this + value get configured into FPS configuration register when system + enters into suspend. This is applicable if suspend state FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,ramp-rate-setting: + $ref: /schemas/types.yaml#/definitions/uint32 + description: | + Ramp rate(uV/us) setting to be configured to the device. The pla= tform + may have different ramp rate than advertised ramp rate if it has= design + variation from Maxim's recommended. On this case, platform speci= fic + ramp rate is used for ramp time calculation and this property is= used + for device register configurations. The measured ramp rate of pl= atform + is provided by the regulator-ramp-delay. + + Maxim Max77620 supports following ramp delay: + SD: 13.75mV/us, 27.5mV/us, 55mV/us + LDOs: 5mV/us, 100mV/us + enum: [5000, 13750, 27500, 55000, 100000] + +additionalProperties: false + +# see maxim,max77620.yaml for an example diff --git a/Documentation/devicetree/bindings/regulator/regulator-max77620= .txt b/Documentation/devicetree/bindings/regulator/regulator-max77620.txt deleted file mode 100644 index bcf788897e44..000000000000 --- a/Documentation/devicetree/bindings/regulator/regulator-max77620.txt +++ /dev/null @@ -1,222 +0,0 @@ -Regulator DT binding for MAX77620 Power management IC from Maxim Semicondu= ctor. - -Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply -of these regulators are defined under parent device node. -Details of regulator properties are defined as child node under -sub-node "regulators" which is child node of device node. - -Please refer file -for common regulator bindings used by client. - -Following are properties of parent node related to regulators. - -Optional properties: -------------------- -The input supply of regulators are the optional properties on the -parent device node. The input supply of these regulators are provided -through following properties: -in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins. -in-sd1-supply: Input supply for SD1. -in-sd2-supply: Input supply for SD2. -in-sd3-supply: Input supply for SD3. -in-ldo0-1-supply: Input supply for LDO0 and LDO1. -in-ldo2-supply: Input supply for LDO2. -in-ldo3-5-supply: Input supply for LDO3 and LDO5 -in-ldo4-6-supply: Input supply for LDO4 and LDO6. -in-ldo7-8-supply: Input supply for LDO7 and LDO8. - -Optional sub nodes for regulators under "regulators" subnode: ------------------------------------------------------------- -The subnodes name is the name of regulator and it must be one of: - sd[0-3], ldo[0-8] - -Each sub-node should contain the constraints and initialization -information for that regulator. The definition for each of these -nodes is defined using the standard binding for regulators found at -. - -There are also additional properties for SD/LDOs. These additional propert= ies -are required to configure FPS configuration parameters for SDs and LDOs. -Please refer for more detail of Fle= xible -Power Sequence (FPS). -Following are additional properties: - -- maxim,active-fps-source: FPS source for the regulators to get - enabled/disabled when system is in - active state. Valid values are: - - MAX77620_FPS_SRC_0, - FPS source is FPS0. - - MAX77620_FPS_SRC_1, - FPS source is FPS1 - - MAX77620_FPS_SRC_2 and - FPS source is FPS2 - - MAX77620_FPS_SRC_NONE. - Regulator is not controlled - by FPS events and it gets - enabled/disabled by register - access. - Absence of this property will leave - the FPS configuration register for that - regulator to default configuration. - -- maxim,active-fps-power-up-slot: Sequencing event slot number on which - the regulator get enabled when - master FPS input event set to HIGH. - Valid values are 0 to 7. - This is applicable if FPS source is - selected as FPS0, FPS1 or FPS2. - =09 -- maxim,active-fps-power-down-slot: Sequencing event slot number on which - the regulator get disabled when master - FPS input event set to LOW. - Valid values are 0 to 7. - This is applicable if FPS source is - selected as FPS0, FPS1 or FPS2. - =09 -- maxim,suspend-fps-source: This is same as property - "maxim,active-fps-source" but value - get configured when system enters in - to suspend state. - -- maxim,suspend-fps-power-up-slot: This is same as property - "maxim,active-fps-power-up-slot" but - this value get configured into FPS - configuration register when system - enters into suspend. - This is applicable if suspend state - FPS source is selected as FPS0, FPS1 or - -- maxim,suspend-fps-power-down-slot: This is same as property - "maxim,active-fps-power-down-slot" but - this value get configured into FPS - configuration register when system - enters into suspend. - This is applicable if suspend state - FPS source is selected as FPS0, FPS1 or - FPS2. -- maxim,ramp-rate-setting: integer, ramp rate(uV/us) setting to be - configured to the device. - The platform may have different ramp - rate than advertised ramp rate if it has - design variation from Maxim's - recommended. On this case, platform - specific ramp rate is used for ramp time - calculation and this property is used - for device register configurations. - The measured ramp rate of platform is - provided by the regulator-ramp-delay - as described in . - Maxim Max77620 supports following ramp - delay: - SD: 13.75mV/us, 27.5mV/us, 55mV/us - LDOs: 5mV/us, 100mV/us - -Note: If the measured ramp delay is same as advertised ramp delay then it = is not -required to provide the ramp delay with property "maxim,ramp-rate-setting"= . The -ramp rate can be provided by the regulator-ramp-delay which will be used f= or -ramp time calculation for voltage change as well as for device configurati= on. - -Example: --------- -#include -... -max77620@3c { - in-ldo0-1-supply =3D <&max77620_sd2>; - in-ldo7-8-supply =3D <&max77620_sd2>; - regulators { - sd0 { - regulator-name =3D "vdd-core"; - regulator-min-microvolt =3D <600000>; - regulator-max-microvolt =3D <1400000>; - regulator-boot-on; - regulator-always-on; - maxim,active-fps-source =3D ; - }; - - sd1 { - regulator-name =3D "vddio-ddr"; - regulator-min-microvolt =3D <1200000>; - regulator-max-microvolt =3D <1200000>; - regulator-always-on; - regulator-boot-on; - maxim,active-fps-source =3D ; - }; - - sd2 { - regulator-name =3D "vdd-pre-reg"; - regulator-min-microvolt =3D <1350000>; - regulator-max-microvolt =3D <1350000>; - }; - - sd3 { - regulator-name =3D "vdd-1v8"; - regulator-min-microvolt =3D <1800000>; - regulator-max-microvolt =3D <1800000>; - regulator-always-on; - regulator-boot-on; - }; - - ldo0 { - regulator-name =3D "avdd-sys"; - regulator-min-microvolt =3D <1200000>; - regulator-max-microvolt =3D <1200000>; - regulator-always-on; - regulator-boot-on; - }; - - ldo1 { - regulator-name =3D "vdd-pex"; - regulator-min-microvolt =3D <1050000>; - regulator-max-microvolt =3D <1050000>; - }; - - ldo2 { - regulator-name =3D "vddio-sdmmc3"; - regulator-min-microvolt =3D <1800000>; - regulator-max-microvolt =3D <3300000>; - }; - - ldo3 { - regulator-name =3D "vdd-cam-hv"; - regulator-min-microvolt =3D <2800000>; - regulator-max-microvolt =3D <2800000>; - }; - - ldo4 { - regulator-name =3D "vdd-rtc"; - regulator-min-microvolt =3D <1250000>; - regulator-max-microvolt =3D <1250000>; - regulator-always-on; - regulator-boot-on; - }; - - ldo5 { - regulator-name =3D "avdd-ts-hv"; - regulator-min-microvolt =3D <3000000>; - regulator-max-microvolt =3D <3000000>; - }; - - ldo6 { - regulator-name =3D "vdd-ts"; - regulator-min-microvolt =3D <1800000>; - regulator-max-microvolt =3D <1800000>; - regulator-always-on; - regulator-boot-on; - }; - - ldo7 { - regulator-name =3D "vdd-gen-pll-edp"; - regulator-min-microvolt =3D <1050000>; - regulator-max-microvolt =3D <1050000>; - regulator-always-on; - regulator-boot-on; - }; - - ldo8 { - regulator-name =3D "vdd-hdmi-dp"; - regulator-min-microvolt =3D <1050000>; - regulator-max-microvolt =3D <1050000>; - }; - }; -}; --=20 2.51.0 From nobody Tue Apr 7 18:03:28 2026 Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 030BB366DC9 for ; Mon, 6 Apr 2026 07:51:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.41 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775461892; cv=none; b=VNFim7cDlSy9gVInO47VBiUe4MuBOE6n04CDmVS/UTibPgJ1+o/EybH+xU+uD+zrpYrKhGaut4Qc9p1AMrK3R40fs5ROn4SUQS+vhJ4uuhKtHLayV0V+hcvQtTU4PURQ4bBuTKJJkshmoSu/QsqFgb2M3ZcIi0bghidj0+wgBRI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775461892; c=relaxed/simple; bh=6QiwAReXTpBojlHHp4n5juTw3CiqRhW6QKlsg4KCdoc=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=cDBiP+5MhADK98PJ+xpmacQ3bvtwKsrOK67amQQlMTJDl+iCA7zIqLyEwrPCM7ls1Vn8uJdFOdXMTSgZjOyIWvqYKFuAPI7BaarxKuZ5PStZkh42vX43V3MoZCZv/LGca5CH2oOhxXKrZaVnh51h9proWSKDfs4P9O0bsQickko= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=d6EZuyg2; arc=none smtp.client-ip=209.85.128.41 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="d6EZuyg2" Received: by mail-wm1-f41.google.com with SMTP id 5b1f17b1804b1-488971db0fdso25767325e9.0 for ; Mon, 06 Apr 2026 00:51:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1775461889; x=1776066689; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=H1yRoOrwamurkh8iKC4rWIAOsL7TI+/4XONPPGFJ1VM=; b=d6EZuyg2H7GTsIHA+AbH5zFB9tZ/peLTW4aUKZXbem23j6Xoa+/k6DUCZfS1APvvHN 5MODVOZV8Iqz7nsFX9n/XM5xig8uL2gks3eKEd7Qb7VAmD5NtkenlvlOd9UoM3eYeYIH xsSjSE2F668w0u0P/K1+1oDzpdLTjRpPr3yPRZhBNevAF213233DfgYUr1Z/r1/W0I62 jdxHiCOyhSMjRvm1Gt2WmP72Q5Gl8scYngrLbvj7iRNVaHpFHwlKr2sjABA5btMDP136 31qWlu57Eqm9A5Z8NOD0C79BGRY2ZkLnM4CESHk07HCHWAoGkv+NPln8o19wRsVye5bU jgpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775461889; x=1776066689; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=H1yRoOrwamurkh8iKC4rWIAOsL7TI+/4XONPPGFJ1VM=; b=SZ11TatjzIjc091oMUcMFjSUAxJxwZXXJrtffxR33GHNt+CDTU+flY9HY92IU1vn0i 9u8sAO484S4K21XK3OqHz+5svLjZJOC1qonwv+a9dInJZYqDzog89SPR/bMKQLV/ONkf VRJ/r3ozWoVav5ZI2MlBVy2rrkhdlwULGGFSOEQbxRTwczQbzV6cYYhCflqyxdFlQfqV aL+7R4zv5lkUmuPewqIOVahrsRK8sQNm3hwM6+BJH2pqqRNfjVP7fDpBMvkKl6vunsyu QXQJjvVYK8fDs6nuvtvmtegPTvk3tLJP9bE9szZJF7k/VW8DvTdThYJHu3eh3EnYsgMo Q9pw== X-Forwarded-Encrypted: i=1; AJvYcCXNwX0qKudAiI1pBKwkuDmygjXBPTqibag0B5h8wbFBpjYtrpEvbDNAsD9yD+FyU6R8UXnDcjy0Oqtf0Dw=@vger.kernel.org X-Gm-Message-State: AOJu0YzIs3hHXJH2tjhDmXl8GJQcQrdhXeaf9taAk0yiPEzI0NYGJDpt /Uvb9mGEWzwHQKKmAa9SsFt68hpsJJ8tvcgYU8BOyYLYhWCBL3mJJsXP X-Gm-Gg: AeBDieuDSPGoHSsLYzUYtOkAo3mhm8TGEJacwz1PICgKIcz3dEMBd3G0YutMFjM1PI2 q/D2l+YIMOQmGxan9nxGltMXVdkhczhFkEfJxWzh7hHzk4ywKapXGE25wey7/aJZRXoJwQfrD/7 u3OR/7U4pdDsiSYQptC8dNPuG2gqd1AZ1INvelnr16KJMFNU/7R5wxI/d5bU4u362Zfa9ocwx25 UI8zWpQUYPPbBgwckhvgUDj0qyl1clFCpK0B/Zx2kMntmo30O27Qqaiya5Q1NItoFfyxKwpSY+2 eMh3MKeKQ7z1WmGYk/WMf13GNYVeqm2QLx+YiH7Sqb4lCjI8ccd5yMM5BcQufHqp7gtDtU5DU4i zInYRET/jlDb3rEqSPKorV4rzSYiIk9bEAgVb60or0vgR6jGG92/UrnuE5oAeVYZPcxfWX1RPSC uMmyDCutxvbet+ X-Received: by 2002:a05:600c:3048:b0:488:9bf8:7f17 with SMTP id 5b1f17b1804b1-4889bf8821fmr94252615e9.14.1775461889025; Mon, 06 Apr 2026 00:51:29 -0700 (PDT) Received: from xeon ([188.163.112.56]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-488b739e00bsm20393525e9.10.2026.04.06.00.51.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Apr 2026 00:51:28 -0700 (PDT) From: Svyatoslav Ryhel To: Linus Walleij , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Liam Girdwood , Mark Brown , Svyatoslav Ryhel Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v5 2/2] dt-bindings: pinctrl: pinctrl-max77620: convert to DT schema Date: Mon, 6 Apr 2026 10:51:14 +0300 Message-ID: <20260406075114.25672-3-clamor95@gmail.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260406075114.25672-1-clamor95@gmail.com> References: <20260406075114.25672-1-clamor95@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Convert pinctrl-max77620 devicetree bindings for the MAX77620 PMIC from TXT to YAML format. This patch does not change any functionality; the bindings remain the same. Signed-off-by: Svyatoslav Ryhel --- .../pinctrl/maxim,max77620-pinctrl.yaml | 98 ++++++++++++++ .../bindings/pinctrl/pinctrl-max77620.txt | 127 ------------------ 2 files changed, 98 insertions(+), 127 deletions(-) create mode 100644 Documentation/devicetree/bindings/pinctrl/maxim,max7762= 0-pinctrl.yaml delete mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-max77= 620.txt diff --git a/Documentation/devicetree/bindings/pinctrl/maxim,max77620-pinct= rl.yaml b/Documentation/devicetree/bindings/pinctrl/maxim,max77620-pinctrl.= yaml new file mode 100644 index 000000000000..b3ea36474317 --- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/maxim,max77620-pinctrl.yaml @@ -0,0 +1,98 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/pinctrl/maxim,max77620-pinctrl.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Pinmux controller function for Maxim MAX77620 Power management IC + +maintainers: + - Svyatoslav Ryhel + +description: + Device has 8 GPIO pins which can be configured as GPIO as well as the + special IO functions. + +allOf: + - $ref: /schemas/pinctrl/pincfg-node.yaml + - $ref: /schemas/pinctrl/pinmux-node.yaml + +patternProperties: + "^(pin|gpio).": + type: object + additionalProperties: false + + properties: + pins: + items: + enum: [ gpio0, gpio1, gpio2, gpio3, gpio4, gpio5, gpio6, gpio7 ] + + function: + items: + enum: [ gpio, lpm-control-in, fps-out, 32k-out1, sd0-dvs-in, sd1= -dvs-in, + reference-out ] + + drive-push-pull: true + drive-open-drain: true + bias-pull-up: true + bias-pull-down: true + + maxim,active-fps-source: + $ref: /schemas/types.yaml#/definitions/uint32 + description: | + FPS source for the GPIOs to get enabled/disabled when system is = in + active state. Valid values are: + - MAX77620_FPS_SRC_0: FPS source is FPS0. + - MAX77620_FPS_SRC_1: FPS source is FPS1 + - MAX77620_FPS_SRC_2: FPS source is FPS2 + - MAX77620_FPS_SRC_NONE: GPIO is not controlled by FPS events and + it gets enabled/disabled by register ac= cess. + Absence of this property will leave the FPS configuration regist= er + for that GPIO to default configuration. + + maxim,active-fps-power-up-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Sequencing event slot number on which the GPIO get enabled when + master FPS input event set to HIGH. This is applicable if FPS so= urce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,active-fps-power-down-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Sequencing event slot number on which the GPIO get disabled when + master FPS input event set to LOW. This is applicable if FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,suspend-fps-source: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-source" but value get + configured when system enters in to suspend state. + + maxim,suspend-fps-power-up-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-power-up-slot" but th= is + value get configured into FPS configuration register when system + enters into suspend. This is applicable if suspend state FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + maxim,suspend-fps-power-down-slot: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + This is same as property "maxim,active-fps-power-down-slot" but = this + value get configured into FPS configuration register when system + enters into suspend. This is applicable if suspend state FPS sou= rce + is selected as FPS0, FPS1 or FPS2. + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + required: + - pins + +additionalProperties: false + +# see maxim,max77620.yaml for an example diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt= b/Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt deleted file mode 100644 index 28fbca180068..000000000000 --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt +++ /dev/null @@ -1,127 +0,0 @@ -Pincontrol driver for MAX77620 Power management IC from Maxim Semiconducto= r. - -Device has 8 GPIO pins which can be configured as GPIO as well as the -special IO functions. - -Please refer file -for details of the common pinctrl bindings used by client devices, -including the meaning of the phrase "pin configuration node". - -Optional Pinmux properties: --------------------------- -Following properties are required if default setting of pins are required -at boot. -- pinctrl-names: A pinctrl state named per . -- pinctrl[0...n]: Properties to contain the phandle for pinctrl states per - . - -The pin configurations are defined as child of the pinctrl states node. Ea= ch -sub-node have following properties: - -Required properties: ------------------- -- pins: List of pins. Valid values of pins properties are: - gpio0, gpio1, gpio2, gpio3, gpio4, gpio5, gpio6, gpio7. - -Optional properties: -------------------- -Following are optional properties defined as pinmux DT binding document -. Absence of properties will leave the configuration -on default. - function, - drive-push-pull, - drive-open-drain, - bias-pull-up, - bias-pull-down. - -Valid values for function properties are: - gpio, lpm-control-in, fps-out, 32k-out, sd0-dvs-in, sd1-dvs-in, - reference-out - -There are also customised properties for the GPIO1, GPIO2 and GPIO3. These -customised properties are required to configure FPS configuration paramete= rs -of these GPIOs. Please refer for mo= re -detail of Flexible Power Sequence (FPS). - -- maxim,active-fps-source: FPS source for the GPIOs to get - enabled/disabled when system is in - active state. Valid values are: - - MAX77620_FPS_SRC_0, - FPS source is FPS0. - - MAX77620_FPS_SRC_1, - FPS source is FPS1 - - MAX77620_FPS_SRC_2 and - FPS source is FPS2 - - MAX77620_FPS_SRC_NONE. - GPIO is not controlled - by FPS events and it gets - enabled/disabled by register - access. - Absence of this property will leave - the FPS configuration register for that - GPIO to default configuration. - -- maxim,active-fps-power-up-slot: Sequencing event slot number on which - the GPIO get enabled when - master FPS input event set to HIGH. - Valid values are 0 to 7. - This is applicable if FPS source is - selected as FPS0, FPS1 or FPS2. - -- maxim,active-fps-power-down-slot: Sequencing event slot number on which - the GPIO get disabled when master - FPS input event set to LOW. - Valid values are 0 to 7. - This is applicable if FPS source is - selected as FPS0, FPS1 or FPS2. - -- maxim,suspend-fps-source: This is same as property - "maxim,active-fps-source" but value - get configured when system enters in - to suspend state. - -- maxim,suspend-fps-power-up-slot: This is same as property - "maxim,active-fps-power-up-slot" but - this value get configured into FPS - configuration register when system - enters into suspend. - This is applicable if suspend state - FPS source is selected as FPS0, FPS1 or - -- maxim,suspend-fps-power-down-slot: This is same as property - "maxim,active-fps-power-down-slot" but - this value get configured into FPS - configuration register when system - enters into suspend. - This is applicable if suspend state - FPS source is selected as FPS0, FPS1 or - FPS2. - -Example: --------- -#include -... -max77620@3c { - - pinctrl-names =3D "default"; - pinctrl-0 =3D <&spmic_default>; - - spmic_default: pinmux@0 { - pin_gpio0 { - pins =3D "gpio0"; - function =3D "gpio"; - }; - - pin_gpio1 { - pins =3D "gpio1"; - function =3D "fps-out"; - maxim,active-fps-source =3D ; - }; - - pin_gpio2 { - pins =3D "gpio2"; - function =3D "fps-out"; - maxim,active-fps-source =3D ; - }; - }; -}; --=20 2.51.0