[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220519194821.GA2071376-robh@kernel.org>
Date: Thu, 19 May 2022 14:48:21 -0500
From: Rob Herring <robh@...nel.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
devicetree@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
chrome-platform@...ts.linux.dev,
Guenter Roeck <groeck@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Craig Hesling <hesling@...omium.org>,
Tom Hughes <tomhughes@...omium.org>,
Alexandru M Stan <amstan@...omium.org>,
Tzung-Bi Shih <tzungbi@...nel.org>,
Matthias Kaehlcke <mka@...omium.org>,
Benson Leung <bleung@...omium.org>,
Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH v5 3/3] dt-bindings: cros-ec: Add ChromeOS fingerprint
binding
On Wed, May 18, 2022 at 12:56:17PM -0700, Stephen Boyd wrote:
> Quoting Rob Herring (2022-05-18 09:13:48)
> > On Mon, May 16, 2022 at 12:23:03PM -0700, Stephen Boyd wrote:
> > > Quoting Rob Herring (2022-05-16 08:20:03)
> > > > On Wed, May 11, 2022 at 06:39:21PM -0700, Stephen Boyd wrote:
> > > > > diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> > > > > index 409ecef967ce..e5fe60beb9fe 100644
> > > > > --- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> > > > > +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> > > > > + - items:
> > > > > + - const: google,cros-ec-i2c
> > > > > + # For implementations of the FPMCU connected through SPI.
> > > > > + - items:
> > > > > + - const: google,cros-ec-fp
> > > > > + - const: google,cros-ec-spi
> > > > > + # For implementations of the EC is connected through SPI.
> > > > > + - items:
> > > > > + - const: google,cros-ec-spi
> > > > > + # For implementations of the EC is connected through RPMSG.
> > > > > + - items:
> > > > > + - const: google,cros-ec-rpmsg
> > > > >
> > > > > controller-data:
> > > > > description:
> > > > > @@ -176,6 +189,37 @@ allOf:
> > > > > - reg
> > > > > - interrupts
> > > > >
> > > > > + - if:
> > > > > + properties:
> > > > > + compatible:
> > > > > + contains:
> > > > > + const: google,cros-ec-fp
> > > > > + then:
> > > > > + properties:
> > > > > + '#address-cells': false
> > > > > + '#size-cells': false
> > > > > + typec: false
> > > > > + ec-pwm: false
> > > > > + keyboard-controller: false
> > > > > + proximity: false
> > > > > + codecs: false
> > > > > + cbas: false
> > > > > +
> > > > > + patternProperties:
> > > > > + "^i2c-tunnel[0-9]*$": false
> > > > > + "^regulator@[0-9]+$": false
> > > > > + "^extcon[0-9]*$": false
> > > >
> > > > Is the list of what's allowed shorter? If so, you could list those
> > > > properties and use 'additionalProperties: false'.
> > >
> > > Yes.
> > >
> > > >
> > > > Or maybe this is a sign that this should be a separate schema document.
> > >
> > > I couldn't figure that out. I tried to add new properties here but it
> > > didn't work.
> >
> > Like this?:
> >
> > then:
> > properties:
> > allowed-prop-1: true
> > allowed-prop-2: true
> > allowed-prop-3: true
> > additionalProperties: false
>
> It doesn't seem to combine constraints?
>
> I get this error:
>
> Documentation/devicetree/bindings/mfd/google,cros-ec.example.dt.yaml:
> ec@0: Additional properties are not allowed ('$nodename' was unexpected)
That would be a bug or limitation in the tools. We would need to add
all the other properties we automatically add as well... I think either
leaving it as-is or a separate file is going to be the better route
here.
Rob
Powered by blists - more mailing lists