On Tue, Sep 16, 2025 at 06:28:53PM +0530, Kamal Wadhwa wrote:
> The `pmic-id` property previously accepted a single lowercase alphabet
> in the range [a-n]. However, on new targets such as Glymur, the
> property uses a new format: `[A-N]_E[0-3]`, where `[A-N]` represents
> the PMIC ID and `[0-3]` represents the BUS ID.
You are sstating that the property uses a different format. Instead you
should write that on these platforms there are multiple SPMI bus in use,
so pmic-id needs to specify both PMIC 'letter' and bus ID. The proposed
format follows the cmd-db format.
>
> Update the property description to reflect this new pattern format,
> matching the updated driver implementation.
>
> Note - Old format [a-n] is still valid and will work for existing
> targets.
>
> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
> index 40e57b10ebbebeff130871b6d978df64111b6f29..40ddc64577e78b5c0dbb7b4e8893a08e8b37c92e 100644
> --- a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
> +++ b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
> @@ -108,7 +108,7 @@ properties:
> RPMh resource name suffix used for the regulators found
> on this PMIC.
> $ref: /schemas/types.yaml#/definitions/string
> - enum: [a, b, c, d, e, f, g, h, i, j, k, l, m, n]
> + pattern: "^[a-n]|[A-N]_E[0-3]+$"
>
> qcom,always-wait-for-ack:
> description: |
>
> --
> 2.25.1
>
--
With best wishes
Dmitry