On 28/06/2022 03:58, Anjelique Melendez wrote: > From: David Collins <quic_collinsd@xxxxxxxxxxx> > > Update the description of "reg" property to add the PON_PBS base > address along with PON_HLOS base address. Also add "reg-names" > property description. > > Signed-off-by: David Collins <quic_collinsd@xxxxxxxxxxx> > Signed-off-by: Anjelique Melendez <quic_amelende@xxxxxxxxxxx> > --- > > New patch series to sperate this patch from applied patches. > Last comments from original patch series can be found > https://lore.kernel.org/linux-arm-msm/27515993-18f3-8891-4835-9b6a8d7f86b0@xxxxxxxxxxx/ > > changes since v1: > - Updated path which was missing Documention/devicetree prefix > - Updated CC list > > ../bindings/power/reset/qcom,pon.yaml | 20 +++++++++++++++++++- > 1 file changed, 19 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml > index 353f155d..1d8cf900 100644 > --- a/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml > +++ b/Documentation/devicetree/bindings/power/reset/qcom,pon.yaml > @@ -26,8 +26,26 @@ properties: > - qcom,pm8998-pon > > reg: > - maxItems: 1 > + description: | > + Specifies the SPMI base address for the PON (power-on) peripheral. For > + PMICs that have the PON peripheral (GEN3) split into PON_HLOS and PON_PBS > + (e.g. PMK8350), this can hold addresses of both PON_HLOS and PON_PBS > + peripherals. In that case, the PON_PBS address needs to be specified to > + facilitate software debouncing on some PMICs. You need separate compatibles for that and constraints (allOf:if:then) for each variant. > + minItems: 1 > + maxItems: 2 > > + reg-names: > + description: | > + For PON GEN1 and GEN2, it should be "pon". For PON GEN3 it should include > + "pon_hlos" and optionally "pon_pbs". > + minItems: 1 > + maxItems: 2 > + items: > + anyOf: > + - const: pon_hlos > + - const: pon_pbs > + - const: pon First, you missed Rob's comment, that names should be without "pon" prefix. Second, uUnfortunately this cannot be such flexible. Items have to be strictly ordered. You mentioned in description something about gen1/2/3, so probably what you want per-variant, specific list. Best regards, Krzysztof
