From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Rob Herring <robh@kernel.org>
Cc: Joakim Zhang <qiangqing.zhang@nxp.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: (EXT) Re: [PATCH 1/1] dt-bindings: net: fsl, fec: Add nvmem-cells / nvmem-cell-names properties
Date: Thu, 10 Feb 2022 12:56:15 +0100 [thread overview]
Message-ID: <3585792.irdbgypaU6@steina-w> (raw)
In-Reply-To: <YgM09mGTZv3U5nBT@robh.at.kernel.org>
Hi Rob,
Am Mittwoch, 9. Februar 2022, 04:28:54 CET schrieb Rob Herring:
> On Wed, Jan 26, 2022 at 03:47:48PM +0100, Alexander Stein wrote:
> > These properties are inherited from ethernet-controller.yaml.
> > This fixes the dt_binding_check warning:
> > imx8mm-tqma8mqml-mba8mx.dt.yaml: ethernet@30be0000: 'nvmem-cell-names',
> > 'nvmem-cells' do not match any of the regexes: 'pinctrl-[0-9]+'
> >
> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> > ---
> >
> > Documentation/devicetree/bindings/net/fsl,fec.yaml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/net/fsl,fec.yaml
> > b/Documentation/devicetree/bindings/net/fsl,fec.yaml index
> > daa2f79a294f..73616924fa29 100644
> > --- a/Documentation/devicetree/bindings/net/fsl,fec.yaml
> > +++ b/Documentation/devicetree/bindings/net/fsl,fec.yaml
> >
> > @@ -121,6 +121,10 @@ properties:
> > mac-address: true
> >
> > + nvmem-cells: true
>
> Need to define how many.
>
> > +
> > + nvmem-cell-names: true
>
> And what the names are.
Thanks for the feedback. Do I really have to copy the following lines from
Documentation/devicetree/bindings/net/ethernet-controller.yaml to
fsl,fec.yaml?
> nvmem-cells:
> maxItems: 1
>
> description:
> Reference to an nvmem node for the MAC address
>
> nvmem-cell-names:
> const: mac-address
This feels wrong to me. Apparently the settings from ethernet-controller.yaml
take effect, e.g. adding a 2nd entry raises warnings. In the end I followed
the example from Documentation/devicetree/bindings/net/engleder,tsnep.yaml, so
I assumed it's okay going this way.
Best regards,
Alexander
prev parent reply other threads:[~2022-02-10 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 14:47 [PATCH 1/1] dt-bindings: net: fsl,fec: Add nvmem-cells / nvmem-cell-names properties Alexander Stein
2022-02-09 3:28 ` Rob Herring
2022-02-10 11:56 ` Alexander Stein [this message]
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=3585792.irdbgypaU6@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.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;
as well as URLs for NNTP newsgroup(s).