From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: phy: add core phylib sfp support
Date: Mon, 11 Nov 2019 14:01:15 +0000 [thread overview]
Message-ID: <20191111140114.GH25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191110170040.GG25889@lunn.ch>
On Sun, Nov 10, 2019 at 06:00:40PM +0100, Andrew Lunn wrote:
> On Sun, Nov 10, 2019 at 04:40:07PM +0000, Russell King - ARM Linux admin wrote:
> > On Sun, Nov 10, 2019 at 05:13:07PM +0100, Andrew Lunn wrote:
> > > On Sun, Nov 10, 2019 at 02:23:05PM +0000, Russell King wrote:
> > > > Add core phylib help for supporting SFP sockets on PHYs. This provides
> > > > a mechanism to inform the SFP layer about PHY up/down events, and also
> > > > unregister the SFP bus when the PHY is going away.
> > >
> > > Hi Russell
> > >
> > > What does the device tree binding look like? I think you have SFP
> > > proprieties in the PHYs node?
> >
> > Correct, just the same as network devices. Hmm, however, neither are
> > documented... oh dear, it looks like I need to figure out how this
> > yaml stuff works. :(
>
> Yes, that would be good. I also assume you have at least one DT patch
> for one of the Marvell boards? Seeing that would also help.
So, how does one make sure that the .yaml files are correct?
The obvious thing is to use the "dtbs_check" target, described by
Documentation/devicetree/writing-schema.md, but that's far from
trivial.
First it complained about lack of libyaml development, which is easy
to solve. Having given it that, "dtbs_check" now complains:
/bin/sh: 1: dt-doc-validate: not found
/bin/sh: 1: dt-mk-schema: not foundmake[2]: ***
[...Documentation/devicetree/bindings/Makefile:12:
Documentation/devicetree/bindings/arm/stm32/stm32.example.dts] Error 127
(spot the lack of newline character - which is obviously an entirely
different problem...)
# apt search dt-doc-validate
Sorting... Done
Full Text Search... Done
# apt search dt-mk-schema
Sorting... Done
Full Text Search... Done
Searching google, it appears it needs another git repository
(https://github.com/robherring/dt-schema/) from Rob Herring to use
this stuff, which is totally undocumented in the kernel tree.
Rob, can we have some _decent_ documentation on how to use this stuff
please, particularly something that describes what the external
dependencies are and where to get the necessary code from - it's
rather unfair to make documentation of DT properties a requirement
for integration into the kernel, convert the documentation to .yaml
format, and not tell people how they can sensibly validate it. Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-11-11 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 14:22 [PATCH net-next 0/2] Add support for SFPs behind PHYs Russell King - ARM Linux admin
2019-11-10 14:23 ` [PATCH net-next 1/2] net: phy: add core phylib sfp support Russell King
2019-11-10 16:13 ` Andrew Lunn
2019-11-10 16:40 ` Russell King - ARM Linux admin
2019-11-10 17:00 ` Andrew Lunn
2019-11-10 17:08 ` Russell King - ARM Linux admin
2019-11-10 17:22 ` Andrew Lunn
2019-11-11 14:01 ` Russell King - ARM Linux admin [this message]
2019-11-11 14:54 ` Russell King - ARM Linux admin
2019-11-11 15:01 ` Rob Herring
2019-11-11 15:07 ` Russell King - ARM Linux admin
2019-11-11 15:44 ` Rob Herring
2019-11-11 15:52 ` Russell King - ARM Linux admin
2019-11-10 14:23 ` [PATCH net-next 2/2] net: phy: marvell10g: add SFP+ support Russell King
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=20191111140114.GH25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).