public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Ray <ian.ray@gehealthcare.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ARM: dts: imx: bx50v3: Configure phy-mode
Date: Tue, 17 Feb 2026 17:15:09 +0200	[thread overview]
Message-ID: <aZSF_VIBRPodKCD6@zeus> (raw)
In-Reply-To: <fa3805bd-d242-4399-8175-4b8dcd0f84b6@lunn.ch>

On Tue, Feb 17, 2026 at 03:58:42PM +0100, Andrew Lunn wrote:
> CAUTION: This email originated from outside of GE HealthCare. Only open links or attachments if you trust the sender. Report suspicious emails using Outlook’s “Report” button.
> 
> On Tue, Feb 17, 2026 at 02:59:49PM +0200, Ian Ray wrote:
> > Set `phy-mode' on network switch CPU ports to eliminate a warning.
> >
> > Signed-off-by: Ian Ray <ian.ray@gehealthcare.com>
> > ---
> >  arch/arm/boot/dts/nxp/imx/imx6q-b450v3.dts | 1 +
> >  arch/arm/boot/dts/nxp/imx/imx6q-b650v3.dts | 1 +
> >  arch/arm/boot/dts/nxp/imx/imx6q-b850v3.dts | 1 +
> >  3 files changed, 3 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/nxp/imx/imx6q-b450v3.dts b/arch/arm/boot/dts/nxp/imx/imx6q-b450v3.dts
> > index d994b32ad825..7326b8ad08cb 100644
> > --- a/arch/arm/boot/dts/nxp/imx/imx6q-b450v3.dts
> > +++ b/arch/arm/boot/dts/nxp/imx/imx6q-b450v3.dts
> > @@ -140,6 +140,7 @@ port@3 {
> >       port@4 {
> >               reg = <4>;
> >               label = "cpu";
> > +             phy-mode = "gmii";
> 
> Are the PHYs external to the switch?

Yes, port 4 is connected to an I210.

> 
> >       port@4 {
> >               reg = <4>;
> >               label = "cpu";
> > +             phy-mode = "gmii";
> >               ethernet = <&switch_nic>;
> >               phy-handle = <&switchphy4>;
> 
> You have back to back PHYs on the CPU port? This is not wrong, but
> unusual.

No, the patch sets `phy-mode' on three different boards.  (If I
understand your question correctly.)

Thanks,
Ian

> 
>         Andrew

  reply	other threads:[~2026-02-17 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 12:59 [PATCH 0/4] ARM: dts: imx: {bx50v3,b850v3}: Update device trees Ian Ray
2026-02-17 12:59 ` [PATCH 1/4] ARM: dts: imx: bx50v3: Configure switch PHY max-speed Ian Ray
2026-02-17 14:53   ` Andrew Lunn
2026-02-17 15:07     ` Ian Ray
2026-02-17 12:59 ` [PATCH 2/4] ARM: dts: imx: bx50v3: Configure phy-mode Ian Ray
2026-02-17 13:08   ` Daniel Baluta
2026-02-17 13:15     ` Ian Ray
2026-02-17 14:58   ` Andrew Lunn
2026-02-17 15:15     ` Ian Ray [this message]
2026-02-17 12:59 ` [PATCH 3/4] ARM: dts: imx: b850v3: Define GPIO line names Ian Ray
2026-02-17 13:23   ` Daniel Baluta
2026-02-17 13:21     ` Ian Ray
2026-02-17 12:59 ` [PATCH 4/4] ARM: dts: imx: b850v3: Disable usdhc4 Ian Ray

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=aZSF_VIBRPodKCD6@zeus \
    --to=ian.ray@gehealthcare.com \
    --cc=Frank.Li@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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