[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aefe5080-475b-946e-d6c7-1c39dc90da1c@linaro.org>
Date: Mon, 11 Apr 2022 13:34:15 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [RFC PATCH 1/2] regulator: dt-bindings: qcom,rpmh: document
supplies per variant
On 11/04/2022 13:03, Krzysztof Kozlowski wrote:
> The RPMH regulator binding covers several devices with different
> regulator supplies, so it uses patterns matching broad range of these
> supplies. This works fine but is not specific and might miss actual
> mistakes when a wrong supply property is used for given variant.
>
> Add separate child schema which describes the supplies depending on the
> compatible.
(...)
> -additionalProperties: false
> -
> required:
> - compatible
> - qcom,pmic-id
>
> +allOf:
> + - $ref: qcom,rpmh-regulator-supplies.yaml#
> +
> +additionalProperties: false
This should be unevaluatedProperties:false, although this makes schema
matching any property. :(
Best regards,
Krzysztof
Powered by blists - more mailing lists