From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Rob Herring <robh@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 net-next 1/4] dt-bindings: net: convert sff,sfp to dtschema
Date: Thu, 7 Jul 2022 08:52:23 +0000 [thread overview]
Message-ID: <20220707084925.tdi27tvfcnvzqoii@skbuf> (raw)
In-Reply-To: <20220705212903.GA2615438-robh@kernel.org>
On Tue, Jul 05, 2022 at 03:29:03PM -0600, Rob Herring wrote:
> On Mon, Jul 04, 2022 at 04:46:01PM +0300, Ioana Ciornei wrote:
> > Convert the sff,sfp.txt bindings to the DT schema format.
> > Also add the new path to the list of maintained files.
> >
> > Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
> > ---
> > Changes in v2:
> > - used the -gpios suffix
> > - restricted the use of some gpios if the compatible is sff,sff
> >
> > .../devicetree/bindings/net/sff,sfp.txt | 85 -----------
> > .../devicetree/bindings/net/sff,sfp.yaml | 143 ++++++++++++++++++
> > MAINTAINERS | 1 +
> > 3 files changed, 144 insertions(+), 85 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/net/sff,sfp.txt
> > create mode 100644 Documentation/devicetree/bindings/net/sff,sfp.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/net/sff,sfp.txt b/Documentation/devicetree/bindings/net/sff,sfp.txt
> > deleted file mode 100644
> > index 832139919f20..000000000000
> > --- a/Documentation/devicetree/bindings/net/sff,sfp.txt
> > +++ /dev/null
> > @@ -1,85 +0,0 @@
> > -Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
> > -Transceiver
(...)
> > + maximum-power-milliwatt:
> > + maxItems: 1
> > + description:
> > + Maximum module power consumption Specifies the maximum power consumption
> > + allowable by a module in the slot, in milli-Watts. Presently, modules can
> > + be up to 1W, 1.5W or 2W.
>
> enum: [ 1000, 1500, 2000 ]
>
> Or is it not just those values? Maybe 'maximum: 2000' instead.
Keeping in mind Russell's comment, I think I will leave this just as it
is since there is no enforcing made on the value.
>
> > +
> > +patternProperties:
> > + "mod-def0-gpios":
>
> These aren't patterns. Move to 'properties'.
Yes, I forgot to move them when I removed the '(s)?'
Thanks!
Ioana
next prev parent reply other threads:[~2022-07-07 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 13:46 [PATCH v2 net-next 0/4] dt-bindings: net: convert sff,sfp to dtschema Ioana Ciornei
2022-07-04 13:46 ` [PATCH v2 net-next 1/4] " Ioana Ciornei
2022-07-05 21:29 ` Rob Herring
2022-07-05 21:34 ` Russell King (Oracle)
2022-07-07 8:52 ` Ioana Ciornei [this message]
2022-07-04 13:46 ` [PATCH v2 net-next 2/4] dt-bindings: net: sff,sfp: rename example dt nodes to be more generic Ioana Ciornei
2022-07-05 21:30 ` Rob Herring
2022-07-04 13:46 ` [PATCH v2 net-next 3/4] arch: arm64: dts: lx2160a-clearfog-itx: rename the sfp GPIO properties Ioana Ciornei
2022-07-04 13:46 ` [PATCH v2 net-next 4/4] arch: arm64: dts: marvell: " Ioana Ciornei
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=20220707084925.tdi27tvfcnvzqoii@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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