From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Robert Marko <robimarko@gmail.com>,
andersson@kernel.org, konrad.dybcio@linaro.org,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: qca807x: move interface mode check to .config_init_once
Date: Tue, 13 Feb 2024 14:27:32 +0100 [thread overview]
Message-ID: <4210645b-4e03-4147-aa03-6fa55786f690@lunn.ch> (raw)
In-Reply-To: <65cb6864.5d0a0220.9cdaa.2449@mx.google.com>
> > Yes, that is correct and when SFP is plugged in it will be reconfigured
> > by the driver into combo mode as that port can actually be used for fiber and
> > copper at the same time by changing the priority.
> >
>
> Hi Andrew, just to make sure this doesn't get confused.
>
> There is a HW limitation here and it's described in Documentation:
>
> - In QSGMII mode the SFP Cage can't be connected or mounted physically
> as in this mode only 5 copper port can be connected, it would go
> against the HW design of the chip. In this configuration the first 4
> port are qsgmii and the 5th port is sgmii. (we enforce qsgmii on all
> ports out of simplicity to make sure we have a sane configuration in
> DT)
>
> - In PSGMII mode the 5th port is always a combo port that can either be
> a copper port or a fiber port (with SFP cage). To set the 5th port to
> fiber mode, the mode has to be switched but the other 4 port are
> always copper.
> Also it's ok to set the initial PSGMII mode to 5 copper port as it
> will be changed as soon as a SFP cage is connected. (can't happen to
> have a device with both a copper port and a SFP cage connected to the
> 5th port, it's one or the other. Again it would go against the HW
> design.
>
> Hope it's clear now why the check was introduced and the HW limitation
> of it as with the previous message one might think the 5th port is
> totally separated and can go to his own mode (PSGMII or QSGMII)
Thanks for the explanation
I'm more used to it being like:
ð2 {
/* ethernet@34000 */
bm,pool-long = <3>;
bm,pool-short = <1>;
buffer-manager = <&bm>;
managed = "in-band-status";
phys = <&comphy5 1>;
phy-mode = "sgmii";
sfp = <&sfp0>;
status = "okay";
};
Here phy-mode is set to one of the modes the SFP will use, either
sgmii or 1000baseX. But i don't think it matters what value is used.
Andrew
next prev parent reply other threads:[~2024-02-13 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 11:49 Robert Marko
2024-02-12 14:51 ` Andrew Lunn
2024-02-12 18:09 ` Robert Marko
2024-02-12 19:48 ` Andrew Lunn
2024-02-13 10:16 ` Robert Marko
2024-02-13 13:02 ` Christian Marangi
2024-02-13 13:27 ` Andrew Lunn [this message]
2024-02-14 17:59 ` Andrew Lunn
2024-02-15 10:50 ` patchwork-bot+netdevbpf
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=4210645b-4e03-4147-aa03-6fa55786f690@lunn.ch \
--to=andrew@lunn.ch \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robimarko@gmail.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
all inboxes | Powered by JetHome®