linux-kernel - Re: [PATCH v4 1/4] dt-bindings: clock: google,gs101-clock: add samsung,sysreg property as required

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CADrjBPr1ny7u7jFHdB5dbAytx2C_MsR7gPL9m-=0BiZZzPEhiA@mail.gmail.com>
Date: Fri, 14 Nov 2025 14:15:48 +0000
From: Peter Griffin <peter.griffin@...aro.org>
To: André Draszik <andre.draszik@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>, 
	Tudor Ambarus <tudor.ambarus@...aro.org>, Michael Turquette <mturquette@...libre.com>, 
	Stephen Boyd <sboyd@...nel.org>, Sam Protsenko <semen.protsenko@...aro.org>, 
	Sylwester Nawrocki <s.nawrocki@...sung.com>, Chanwoo Choi <cw00.choi@...sung.com>, 
	Will McVicker <willmcvicker@...gle.com>, Krzysztof Kozlowski <krzk@...nel.org>, devicetree@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, 
	kernel-team@...roid.com
Subject: Re: [PATCH v4 1/4] dt-bindings: clock: google,gs101-clock: add
 samsung,sysreg property as required

Hi André,

Thanks for the review feedback!

On Tue, 11 Nov 2025 at 09:57, André Draszik <andre.draszik@...aro.org> wrote:
>
> On Tue, 2025-11-11 at 09:54 +0000, André Draszik wrote:
> > Hi Peter,
> >
> > On Mon, 2025-11-10 at 14:21 +0000, Peter Griffin wrote:
> > > [...]
> > >
> > > diff --git a/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
> > > b/Documentation/devicetree/bindings/clock/google,gs101-
> > > clock.yaml
> > > index 31e106ef913dead9a038b3b6d8b43b950587f6aa..5ce5ba523110af3a2a7740b8ba28e2271c76bddb 100644
> > > --- a/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
> > > +++ b/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
> > > @@ -52,6 +52,11 @@ properties:
> > >    reg:
> > >      maxItems: 1
> > >
> > > +  samsung,sysreg:
> > > +    $ref: /schemas/types.yaml#/definitions/phandle
> > > +    description:
> > > +      Phandle to system registers interface.
> > > +
> > >  required:
> > >    - compatible
> > >    - "#clock-cells"
> > > @@ -166,6 +171,22 @@ allOf:
> > >              - const: bus
> > >              - const: ip
> > >
> > > +  - if:
> > > +      properties:
> > > +        compatible:
> > > +          contains:
> > > +            enum:
> > > +              - google,gs101-cmu-apm
> > > +              - google,gs101-cmu-misc
> > > +              - google,gs101-hsi0
> >
> > Shouldn't this be google,gs101-cmu-hsi0?
> >
> > > +              - google,gs101-cmu-hsi2
> > > +              - google,gs101-cmu-peric0
> > > +              - google,gs101-cmu-peric1
> > > +
> > > +    then:
> > > +      required:
> > > +        - samsung,sysreg
> >
> > The above still allows (but doesn't enforce) samsung,sysreg on cmu-top.
> >
> > Maybe it'd be better to invert the test, as cmu-top is the only
> > outlier, and then the binding doesn't need to be updated when more
> > CMUs are added (untested):
> >
> >   - if:
> >       properties:
> >         compatible:
> >           contains:
> >             const: google,gs101-cmu-top
> >
> >     then:
> >       required:
> >         - samsung,sysreg
> >
> >     else:
> >       properties:
> >         samsung,sysreg: false
>
> obviously then: and else: cases should be swapped.

I'll send an updated version with these suggestions integrated in a moment.

Thanks,

Peter