From: Conor Dooley <conor@kernel.org>
To: Ante Knezic <ante.knezic@helmholz.de>
Cc: olteanv@gmail.com, andrew@lunn.ch, conor+dt@kernel.org,
davem@davemloft.net, devicetree@vger.kernel.org,
edumazet@google.com, f.fainelli@gmail.com,
krzysztof.kozlowski+dt@linaro.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, marex@denx.de,
netdev@vger.kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
woojung.huh@microchip.com
Subject: Re: [PATCH net-next v2 2/2] dt-bindings: net: microchip,ksz: document microchip,rmii-clk-internal
Date: Tue, 17 Oct 2023 08:48:27 +0100 [thread overview]
Message-ID: <20231017-fading-retrial-7faebda79ebb@spud> (raw)
In-Reply-To: <20231017073548.15050-1-ante.knezic@helmholz.de>
[-- Attachment #1: Type: text/plain, Size: 3787 bytes --]
On Tue, Oct 17, 2023 at 09:35:48AM +0200, Ante Knezic wrote:
> > > + microchip,rmii-clk-internal:
> > > + $ref: /schemas/types.yaml#/definitions/flag
> > > + description:
> > > + Set if the RMII reference clock is provided internally. Otherwise
> > > + reference clock should be provided externally.
> > > +
> > > +if:
> > > + not:
> > > + properties:
> > > + compatible:
> > > + enum:
> > > + - microchip,ksz8863
> > > + - microchip,ksz8873
> > > +then:
> > > + not:
> > > + required:
> > > + - microchip,rmii-clk-internal
I think this bit can become the slightly simpler
then:
properties:
microchip,rmii-clk-internal: false
> > I think that what you want to express is that microchip,rmii-clk-internal
> > is only defined for microchip,ksz8863 and microchip,ksz8873.
> > Can't you describe that as "if: properties: compatible: (...) then:
> > properties: microchip,rmii-clk-internal"?
>
> If I understood you correctly you are refering to a solution like
> if:
> properties:
> compatible:
> enum:
> - microchip,ksz8863
> - microchip,ksz8873
> then:
> properties:
> microchip,rmii-clk-internal:
> $ref: /schemas/types.yaml#/definitions/flag
> description:
> Set if the RMII reference clock is provided internally. Otherwise
> reference clock should be provided externally.
>
> This was already suggested in v1, but was not a satisfactory solution
> according to Mr. Conor Dooley:
Yeah, we prefer not to have the property definitions inside the
conditionals, but rather constrain or allow/disallow them there.
Cheers,
Conor.
>
> >> On Tue, 10 Oct 2023 16:25:55 +0100, Conor Dooley wrote:
> >> > On Tue, Oct 10, 2023 at 03:18:54PM +0200, Ante Knezic wrote:
> >> > > Add documentation for selecting reference rmii clock on KSZ88X3 devices
> >> > >
> >> > > Signed-off-by: Ante Knezic <ante.knezic@helmholz.de>
> >> > > ---
> >> > > Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml | 6 ++++++
> >> > > 1 file changed, 6 insertions(+)
> >> > >
> >> > > diff --git a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> >> > > index e51be1ac0362..3df5d2e72dba 100644
> >> > > --- a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> >> > > +++ b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml
> >> > > @@ -49,6 +49,12 @@ properties:
> >> > > Set if the output SYNCLKO clock should be disabled. Do not mix with
> >> > > microchip,synclko-125.
> >> > >
> >> > > + microchip,rmii-clk-internal:
> >> > > + $ref: /schemas/types.yaml#/definitions/flag
> >> > > + description:
> >> > > + Set if the RMII reference clock should be provided internally.
> >> >
> >> > > Applies only
> >> > > + to KSZ88X3 devices.
> >> >
> >> > This should be enforced by the schema, the example schema in the docs
> >> > should show you how to do this.
> >>
> >> I am guessing you are refering to limiting the property to ksz88x3 devices?
> >> Something like:
> >>
> >> if:
> >> properties:
> >> compatible:
> >> enum:
> >> - microchip,ksz8863
> >> - microchip,ksz8873
> >> then:
> >> properties:
> >> microchip,rmii-clk-internal:
> >> $ref: /schemas/types.yaml#/definitions/flag
> >> description:
> >> Set if the RMII reference clock is provided internally. Otherwise
> >> reference clock should be provided externally.
> >
> >Not quite. The definition of the property should be outside the if/then,
> >but one should be used to allow/disallow the property.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-17 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 10:55 [PATCH net-next v2 0/2] net: dsa: microchip: enable setting rmii Ante Knezic
2023-10-12 10:55 ` [PATCH net-next v2 1/2] net:dsa:microchip: add property to select internal RMII reference clock Ante Knezic
2023-10-16 10:37 ` Vladimir Oltean
2023-10-17 7:27 ` Ante Knezic
2023-10-17 7:35 ` [PATCH net-next v2 2/2] dt-bindings: net: microchip,ksz: document microchip,rmii-clk-internal Ante Knezic
2023-10-17 7:48 ` Conor Dooley [this message]
2023-10-17 9:31 ` Vladimir Oltean
2023-10-12 10:55 ` Ante Knezic
2023-10-12 15:18 ` Conor Dooley
2023-10-16 7:53 ` [PATCH net-next " Ante Knezic
2023-10-17 8:00 ` Conor Dooley
2023-10-17 9:04 ` [PATCH net-next v2 " Ante Knezic
2023-10-17 12:59 ` [PATCH net-next " Andrew Lunn
2023-10-17 13:39 ` Conor Dooley
2023-10-16 10:32 ` [PATCH net-next v2 " Vladimir Oltean
2023-10-16 10:55 ` [PATCH net-next v2 0/2] net: dsa: microchip: enable setting rmii Vladimir Oltean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231017-fading-retrial-7faebda79ebb@spud \
--to=conor@kernel.org \
--cc=andrew@lunn.ch \
--cc=ante.knezic@helmholz.de \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=woojung.huh@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).