From nobody Thu Apr 2 18:47:38 2026 Received: from mail-wr1-f45.google.com (mail-wr1-f45.google.com [209.85.221.45]) (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 15C1838AC8F for ; Thu, 12 Mar 2026 08:53:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.45 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773305612; cv=none; b=g7VdmKraYL0DRqRC0cHliqSviH4Mg7qg7DY+KdiBIcqK6ijhNEFtTmcC55MeFqEolKIfn8WZtU5nBAa/SYMyeL7kg3UBnErOrDZ/CzHCzkaSCjmMtntnBNe4ILurUusSquDB0JdbQiCCn7PhWT5NVPZuOA0xXHQnvynbhWT+spc= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773305612; c=relaxed/simple; bh=ifTHnKwuEO3kKgeXJR7FZeO8G4oaqv1I62bN3RKV11g=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=J1dki+fsLtDbV0DZFb30sOTz+wfBcIJbf8WuoCwrHY5dr5W99aXRhN15pRRtKzjyYniFWMy4JitxmDc9cZ7IBb9a5KlCDurLXlgS5KdpZf/dYVmhemCrKtfKpV17CjSARUBgrPHyRvkw05fa/IFshScbsjiv2YJVbtlfHxgv8kk= 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=AlZRIeV4; arc=none smtp.client-ip=209.85.221.45 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="AlZRIeV4" Received: by mail-wr1-f45.google.com with SMTP id ffacd0b85a97d-439fe4985efso601685f8f.3 for ; Thu, 12 Mar 2026 01:53:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1773305609; x=1773910409; 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=kN0uhmoJw5mBiCDVED+sYPiiBYFCvTSJOtEF6kukFz4=; b=AlZRIeV4arWvZVxczAdqFKAyEN3hCWDNAYazkvaQaFir0AmcdcbDUN4TbCq9m1YBWy hbj1Xh5BduguP6omCuqKfwYJc8IScvCkdHcQfcSYft0H+1PBu4AsiKQP1wJsutgiDQiT MKKlHTx5KFClVWuBycUu2UQOruFd2G6BOPu/3vGnonDbyUbNpYNiJ1YAewQAuMii7jcg NlNRXEmwyUTJK0Fkng6MIwk7aFO7aTLiCjVtSEmZT2/5z60osCyZkF3MfUXU18F49xnl pmqAvkWhd8PJoSX8SOuHZWGCJILWY/FCA/3yOZ2Rm99n20HgcbqL19HZY6LUvNqtARMc ccvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1773305609; x=1773910409; 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=kN0uhmoJw5mBiCDVED+sYPiiBYFCvTSJOtEF6kukFz4=; b=xFX22FbMqJhZ2IW/aNtiglF8yVYu1LIPZmE5NJHpJssRxGDg4rZgfzg/RSvzj/1rCR 8zPpTt97fi5rYG8uCexq8MUrdMne0IBNnOW2vDTWhhEPP07Z3ukr0SW7Ifx6wBLUYdPQ ZXagppb+J2m6BXsiIqksTqVQzUEf6FZUOTflROuy/+BukHLoOqG0jQsx1vtz7nq3tIkV EJVT8BwmwJhVWipMlWRBeus3cm84JzzosdjHak3awET1LIrsh/DDzH4TpU9mjx61gYQG iJQQEiXBUXDen8MmAM2bLn13AzgirFsCE2sjZ2dhFdCQJvTfK4mHHcRJA7rC3swlFErP JNpg== X-Forwarded-Encrypted: i=1; AJvYcCWFzUJtzTCCz04Ezzo0ukJyVjJK38uPSu4MvnsdxIDDm4auBj6Q+f8ub++hAX0dwpmQW4Kh3xpIMQlDBns=@vger.kernel.org X-Gm-Message-State: AOJu0YzXrZ0onsoGePy7d2v8SkSSZT+s3/YgAtogvX5hVkPjPMtFuIp4 aRRz1a101qeObndTahh53BTidsX4D7R7KoAFq1jlC7p3AMhbxMjHkrID X-Gm-Gg: ATEYQzwWpvaP9LRg6RGtUHe1X/9RPloIvM178pRKbbaZrCNGySC7cF1Wdkq7EaMk+M2 KZ2cqOi616OJQojKNbGOYcx3TNDpkCJg4/bQIgx1SiNVIr1xySCQKUO0IVzgtblam+OD+LwdRwW J2vvqOazVSf9O7276lLfovq9LiGDVrpMNkGjJ4fSe+3K/YU93zPWfZnz4CCDA13Yvqz2gJwjHFJ Yq4oi16hmrlAcg0ZB2mEfYUG8RcYD6L0dqYwlOgKettIkFBV/MpMwCOgmr8V3GFSsgTLIEuZjpP 39wm8MdaWdJ0utfyYH/XGVW9Q0BQigd9nhuBF+ulmt5IPuiCu3rTyidS0EOm+ef573b7E7rlbsr FrK8LWvo0ImWhuUKKLiahf/77LbjWmmOZ21DbdoqY/eNpzvFvDyym1sY3pFeIbF6lSqPYg982sc oktapT/UWh0YUK X-Received: by 2002:a05:6000:26ca:b0:439:b486:ba71 with SMTP id ffacd0b85a97d-439f842f50bmr10561972f8f.56.1773305609210; Thu, 12 Mar 2026 01:53:29 -0700 (PDT) Received: from xeon ([188.163.112.72]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-439fe226473sm5449162f8f.32.2026.03.12.01.53.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Mar 2026 01:53:28 -0700 (PDT) From: Svyatoslav Ryhel To: Linus Walleij , Bartosz Golaszewski , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Lee Jones , Liam Girdwood , Mark Brown , "Rafael J. Wysocki" , Daniel Lezcano , Zhang Rui , Lukasz Luba , Chanwoo Choi , Alexandre Belloni , Svyatoslav Ryhel Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-rtc@vger.kernel.org Subject: [PATCH v4 1/5] regulator: dt-bindings: regulator-max77620: convert to DT schema Date: Thu, 12 Mar 2026 10:52:54 +0200 Message-ID: <20260312085258.11431-2-clamor95@gmail.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260312085258.11431-1-clamor95@gmail.com> References: <20260312085258.11431-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