2023-09-28 16:55:25 +08:00
|
|
|
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
|
|
|
|
|
%YAML 1.2
|
|
|
|
|
---
|
|
|
|
|
$id: http://devicetree.org/schemas/regulator/mediatek,mt6358-regulator.yaml#
|
|
|
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
|
|
|
|
|
|
title: MediaTek MT6358 Regulator
|
|
|
|
|
|
|
|
|
|
maintainers:
|
|
|
|
|
- Zhiyong Tao <zhiyong.tao@mediatek.com>
|
|
|
|
|
|
|
|
|
|
description:
|
|
|
|
|
Regulator node of the PMIC. This node should under the PMIC's device node.
|
|
|
|
|
All voltage regulators provided by the PMIC are described as sub-nodes of
|
|
|
|
|
this node.
|
|
|
|
|
|
|
|
|
|
properties:
|
|
|
|
|
compatible:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
oneOf:
|
|
|
|
|
- const: mediatek,mt6358-regulator
|
|
|
|
|
- items:
|
|
|
|
|
- const: mediatek,mt6366-regulator
|
|
|
|
|
- const: mediatek,mt6358-regulator
|
2023-09-28 16:55:25 +08:00
|
|
|
|
2023-09-28 16:55:27 +08:00
|
|
|
vsys-ldo1-supply:
|
|
|
|
|
description: Supply for LDOs vfe28, vxo22, vcn28, vaux18, vaud28, vsim1, vusb, vbif28
|
|
|
|
|
vsys-ldo2-supply:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
description: Supply for LDOs vldo28 (MT6358 only), vio28, vmc, vmch, vsim2
|
2023-09-28 16:55:27 +08:00
|
|
|
vsys-ldo3-supply:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
description: Supply for LDOs vcn33, vcama[12] (MT6358 only), vemc, vibr
|
2023-09-28 16:55:27 +08:00
|
|
|
vsys-vcore-supply:
|
|
|
|
|
description: Supply for buck regulator vcore
|
|
|
|
|
vsys-vdram1-supply:
|
|
|
|
|
description: Supply for buck regulator vdram1
|
|
|
|
|
vsys-vgpu-supply:
|
|
|
|
|
description: Supply for buck regulator vgpu
|
|
|
|
|
vsys-vmodem-supply:
|
|
|
|
|
description: Supply for buck regulator vmodem
|
|
|
|
|
vsys-vpa-supply:
|
|
|
|
|
description: Supply for buck regulator vpa
|
|
|
|
|
vsys-vproc11-supply:
|
|
|
|
|
description: Supply for buck regulator vproc11
|
|
|
|
|
vsys-vproc12-supply:
|
|
|
|
|
description: Supply for buck regulator vproc12
|
|
|
|
|
vsys-vs1-supply:
|
|
|
|
|
description: Supply for buck regulator vs1
|
|
|
|
|
vsys-vs2-supply:
|
|
|
|
|
description: Supply for buck regulator vs2
|
|
|
|
|
vs1-ldo1-supply:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
description:
|
|
|
|
|
Supply for LDOs vrf18, vefuse, vcn18, vcamio (MT6358 only), vio18, vm18 (MT6366 only)
|
2023-09-28 16:55:27 +08:00
|
|
|
vs2-ldo1-supply:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
description: Supply for LDOs vdram2, vmddr (MT6366 only)
|
2023-09-28 16:55:27 +08:00
|
|
|
vs2-ldo2-supply:
|
|
|
|
|
description: Supply for LDOs vrf12, va12
|
|
|
|
|
vs2-ldo3-supply:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
description:
|
|
|
|
|
Supply for LDOs vsram-core (MT6366 only), vsram-gpu, vsram-others, vsram-proc11, vsram-proc12
|
2023-09-28 16:55:27 +08:00
|
|
|
vs2-ldo4-supply:
|
|
|
|
|
description: Supply for LDO vcamd
|
2023-09-28 16:55:25 +08:00
|
|
|
|
|
|
|
|
patternProperties:
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(buck_)?v(core|dram1|gpu|modem|pa|proc1[12]|s[12])$":
|
2023-09-28 16:55:25 +08:00
|
|
|
description: Buck regulators
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes:
|
|
|
|
|
description: |
|
|
|
|
|
Buck regulatpr operating modes allowed. Valid values below.
|
|
|
|
|
Users should use the macros from dt-bindings/regulator/mediatek,mt6397-regulator.h
|
|
|
|
|
0 (MT6397_BUCK_MODE_AUTO): Auto PFM/PWM mode
|
|
|
|
|
1 (MT6397_BUCK_MODE_FORCE_PWM): Forced PWM mode
|
|
|
|
|
items:
|
|
|
|
|
enum: [0, 1]
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(ldo_)?v(a|rf)12$":
|
2023-09-28 16:55:25 +08:00
|
|
|
description: LDOs with fixed 1.2V output and 0~100/10mV tuning
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(ldo_)?v((aux|cn|io|rf)18|camio)$":
|
|
|
|
|
description:
|
|
|
|
|
LDOs with fixed 1.8V output and 0~100/10mV tuning (vcn18 on MT6366 has variable output)
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
|
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
|
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
|
|
|
|
"^(ldo_)?vxo22$":
|
|
|
|
|
description: LDOs with fixed 2.2V output and 0~100/10mV tuning
|
2023-09-28 16:55:25 +08:00
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(ldo_)?v(aud|bif|cn|fe|io)28$":
|
2023-09-28 16:55:25 +08:00
|
|
|
description: LDOs with fixed 2.8V output and 0~100/10mV tuning
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(ldo_)?vusb$":
|
|
|
|
|
description: LDOs with fixed 3.0V output and 0~100/10mV tuning
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
|
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
|
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
|
|
|
|
"^(ldo_)?vsram[_-](core|gpu|others|proc1[12])$":
|
2023-09-28 16:55:25 +08:00
|
|
|
description: LDOs with variable output
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
"^(ldo_)?v(cama[12]|camd|cn33|dram2|efuse|emc|ibr|ldo28|m18|mc|mch|mddr|sim[12])$":
|
2023-09-28 16:55:25 +08:00
|
|
|
description: LDOs with variable output and 0~100/10mV tuning
|
|
|
|
|
type: object
|
|
|
|
|
$ref: regulator.yaml#
|
2023-09-28 16:55:26 +08:00
|
|
|
properties:
|
|
|
|
|
regulator-allowed-modes: false
|
2023-09-28 16:55:25 +08:00
|
|
|
unevaluatedProperties: false
|
|
|
|
|
|
|
|
|
|
required:
|
|
|
|
|
- compatible
|
|
|
|
|
|
|
|
|
|
additionalProperties: false
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
allOf:
|
|
|
|
|
- if:
|
|
|
|
|
properties:
|
|
|
|
|
compatible:
|
|
|
|
|
const: mediatek,mt6358-regulator
|
|
|
|
|
then:
|
|
|
|
|
patternProperties:
|
|
|
|
|
# Old regulator node name scheme (with prefix and underscores) only
|
|
|
|
|
# ([^y-] is used to avoid matching -supply
|
|
|
|
|
"^(?<!buck_)(?<!ldo_)v.*[^y-](?!-supply)$": false
|
|
|
|
|
"^ldo_vsram-": false
|
|
|
|
|
# vsram_core regulator doesn't exist on MT6358
|
|
|
|
|
"^ldo_vsram[-_]core$": false
|
|
|
|
|
|
|
|
|
|
properties:
|
|
|
|
|
# vm18 and vmddr regulators don't exist on MT6358
|
|
|
|
|
ldo_vm18: false
|
|
|
|
|
ldo_vmddr: false
|
|
|
|
|
|
|
|
|
|
- if:
|
|
|
|
|
properties:
|
|
|
|
|
compatible:
|
|
|
|
|
contains:
|
|
|
|
|
const: mediatek,mt6366-regulator
|
|
|
|
|
then:
|
|
|
|
|
patternProperties:
|
|
|
|
|
# Prefer cleaned up regulator node names
|
|
|
|
|
"^(buck|ldo)_": false
|
|
|
|
|
# Don't allow underscores
|
|
|
|
|
"^vsram_": false
|
|
|
|
|
# vcam* regulators don't exist on MT6366
|
|
|
|
|
"^vcam": false
|
|
|
|
|
|
|
|
|
|
properties:
|
|
|
|
|
# vldo28 regulator doesn't exist on MT6366
|
|
|
|
|
vldo28: false
|
|
|
|
|
# vs2_ldo4 supply pin doesn't exist on MT6366
|
|
|
|
|
vs2-ldo4-supply: false
|
|
|
|
|
|
2023-09-28 16:55:25 +08:00
|
|
|
examples:
|
|
|
|
|
- |
|
2023-09-28 16:55:26 +08:00
|
|
|
#include <dt-bindings/regulator/mediatek,mt6397-regulator.h>
|
|
|
|
|
|
2023-09-28 16:55:25 +08:00
|
|
|
regulator {
|
|
|
|
|
compatible = "mediatek,mt6358-regulator";
|
|
|
|
|
|
|
|
|
|
buck_vgpu {
|
|
|
|
|
regulator-name = "vgpu";
|
|
|
|
|
regulator-min-microvolt = <625000>;
|
|
|
|
|
regulator-max-microvolt = <900000>;
|
|
|
|
|
regulator-ramp-delay = <6250>;
|
|
|
|
|
regulator-enable-ramp-delay = <200>;
|
2023-09-28 16:55:26 +08:00
|
|
|
regulator-allowed-modes = <MT6397_BUCK_MODE_AUTO
|
|
|
|
|
MT6397_BUCK_MODE_FORCE_PWM>;
|
2023-09-28 16:55:25 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
ldo_vsram_gpu {
|
|
|
|
|
regulator-name = "vsram_gpu";
|
|
|
|
|
regulator-min-microvolt = <850000>;
|
|
|
|
|
regulator-max-microvolt = <1000000>;
|
|
|
|
|
regulator-ramp-delay = <6250>;
|
|
|
|
|
regulator-enable-ramp-delay = <240>;
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
regulator: dt-bindings: mt6358: Add MT6366 PMIC
The MediaTek MT6366 PMIC is similar to the MT6358 PMIC. It is designed
to be paired with the MediaTek MT8186 SoC. It has 9 buck regulators and
29 LDO regulators, not counting ones that feed internally and basically
have no controls. The regulators are named after their intended usage
for the SoC and system design, thus not named generically as ldoX or
dcdcX, but as vcn33 or vgpu.
The differences compared to the MT6358 are minimal:
- Regulators removed: VCAMA1, VCAMA2, VCAMD, VCAMIO, VLDO28
- Regulators added: VM18, VMDDR, VSRAM_CORE
Both PMIC models contain a chip ID register at the same address that
can be used to differentiate the actual model. Thus, even though the
MT6366 is not fully backward compatible with the MT6358, it still falls
back on the MT6358 compatible string. It is up to the implementation
to use the chip ID register as a probing mechanism.
Update the MT6358 regulator binding and add entries for all the MT6366's
regulators and their supplies. The regulator node names follow a cleaned
up style without type prefixes and with underscores replaced with hyphens.
Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
[wens@chromium.org: major rework and added commit message]
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230928085537.3246669-6-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-09-28 16:55:28 +08:00
|
|
|
- |
|
|
|
|
|
#include <dt-bindings/regulator/mediatek,mt6397-regulator.h>
|
|
|
|
|
|
|
|
|
|
regulator {
|
|
|
|
|
compatible = "mediatek,mt6366-regulator", "mediatek,mt6358-regulator";
|
|
|
|
|
|
|
|
|
|
vdram1 {
|
|
|
|
|
regulator-name = "pp1125_emi_vdd2";
|
|
|
|
|
regulator-min-microvolt = <1125000>;
|
|
|
|
|
regulator-max-microvolt = <1125000>;
|
|
|
|
|
regulator-ramp-delay = <12500>;
|
|
|
|
|
regulator-enable-ramp-delay = <0>;
|
|
|
|
|
regulator-allowed-modes = <MT6397_BUCK_MODE_AUTO
|
|
|
|
|
MT6397_BUCK_MODE_FORCE_PWM>;
|
|
|
|
|
regulator-always-on;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
vproc11 {
|
|
|
|
|
regulator-name = "ppvar_dvdd_proc_bc_mt6366";
|
|
|
|
|
regulator-min-microvolt = <600000>;
|
|
|
|
|
regulator-max-microvolt = <1200000>;
|
|
|
|
|
regulator-ramp-delay = <6250>;
|
|
|
|
|
regulator-enable-ramp-delay = <200>;
|
|
|
|
|
regulator-allowed-modes = <MT6397_BUCK_MODE_AUTO
|
|
|
|
|
MT6397_BUCK_MODE_FORCE_PWM>;
|
|
|
|
|
regulator-always-on;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
vmddr {
|
|
|
|
|
regulator-name = "pm0750_emi_vmddr";
|
|
|
|
|
regulator-min-microvolt = <700000>;
|
|
|
|
|
regulator-max-microvolt = <750000>;
|
|
|
|
|
regulator-enable-ramp-delay = <325>;
|
|
|
|
|
regulator-always-on;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
vsram-proc11 {
|
|
|
|
|
regulator-name = "pp0900_dvdd_sram_bc";
|
|
|
|
|
regulator-min-microvolt = <850000>;
|
|
|
|
|
regulator-max-microvolt = <1120000>;
|
|
|
|
|
regulator-ramp-delay = <6250>;
|
|
|
|
|
regulator-enable-ramp-delay = <240>;
|
|
|
|
|
regulator-always-on;
|
|
|
|
|
};
|
|
|
|
|
};
|
2023-09-28 16:55:25 +08:00
|
|
|
...
|