From: "Marek Behún" <kabel@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
arm@kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH mvebu-dt v2 4/6] ARM: dts: turris-omnia: add SFP node
Date: Sat, 14 Nov 2020 23:55:50 +0100 [thread overview]
Message-ID: <20201114235550.0ecd4a0c@kernel.org> (raw)
In-Reply-To: <20201114214204.GE1551@shell.armlinux.org.uk>
On Sat, 14 Nov 2020 21:42:04 +0000
Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> On Sat, Nov 14, 2020 at 10:36:09PM +0100, Andreas Färber wrote:
> > Hi Marek,
> >
> > On 14.11.20 19:32, Marek Behún wrote:
> > > Turris Omnia has a SFP cage that, together with WAN PHY is connected to
> >
> > "an SFP"
> > Comma missing after PHY (or drop before together).
> >
> > > eth2 SerDes via a SerDes multiplexor. Describe the SFP cage, but leave
> > > it disabled. Until phylink has support for such multiplexor we will
> > > leave it to U-Boot to enable SFP and disable WAN PHY at boot time
> > > depending on whether a SFP module is present.
> >
> > multiplexor vs. multiplexer may be a British thing? Thunderbird
> > underlines it fwiw.
>
> Why doesn't someone who has a Turris Omnia come up with the support
> needed for this board, such as sending a patch to add support for
> this multiplexer?
>
Russell, I have this planned, but it is a bit complicated.
We discussed this maybe 1 or 2 years ago.
The thing is that phylink does not support such a thing nor is there a
simple way to add such support to it.
One problem we discussed last time is the correct DT binding. Should it
be something like this?
eth2 {
phy-mode = "sgmii";
multiplexer {
gpio = <&mod_def0_gpio>;
option@0 {
reg = <0>;
phy-handle = <&phy1>;
};
option@1 {
reg = <1>;
sfp = <&sfp>;
managed = "in-band-status";
};
};
};
But who should handle this? Phylink, SFP, or maybe this should be
handled generically in OF / fwnode subsystem? I.e. a change in GPIO
value could change device's properties/children?
Also the &mod_def0_gpio is already used by the sfp node. Can this
multiplexor node also refer to it?
Marek
next prev parent reply other threads:[~2020-11-14 22:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 18:32 [PATCH mvebu-dt v2 0/6] Turris Omnia device-tree changes Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 1/6] ARM: dts: turris-omnia: enable HW buffer management Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 2/6] ARM: dts: turris-omnia: add comphy handle to eth2 Marek Behún
2020-11-14 21:25 ` Andreas Färber
2020-11-14 18:32 ` [PATCH mvebu-dt v2 3/6] ARM: dts: turris-omnia: describe switch interrupt Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 4/6] ARM: dts: turris-omnia: add SFP node Marek Behún
2020-11-14 21:36 ` Andreas Färber
2020-11-14 21:42 ` Russell King - ARM Linux admin
2020-11-14 21:46 ` Andreas Färber
2020-11-14 22:55 ` Marek Behún [this message]
2020-11-15 11:28 ` Russell King - ARM Linux admin
2020-11-14 22:57 ` Marek Behún
2020-11-14 23:16 ` Andreas Färber
2020-11-15 0:32 ` Marek Behún
2020-11-15 0:38 ` Marek Behún
2020-11-14 23:27 ` Andreas Färber
2020-11-15 0:11 ` Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 5/6] ARM: dts: turris-omnia: add LED controller node Marek Behún
2020-11-14 21:58 ` Andreas Färber
2020-11-14 23:23 ` Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 6/6] ARM: dts: turris-omnia: update ethernet-phy node and handle name Marek Behún
2020-11-14 22:04 ` Andreas Färber
2020-11-14 23:30 ` Marek Behún
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=20201114235550.0ecd4a0c@kernel.org \
--to=kabel@kernel.org \
--cc=afaerber@suse.de \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.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).