mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yongzhao Chen <yongzhao.derek@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	Christian Marangi <ansuelsmth@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Ziyang Huang <hzyitc@outlook.com>
Subject: Re: [RFC PATCH net-next v3 4/5] net: dsa: qca8k: flag QCA8337 internal CPU PHYs for SmartSpeed
Date: Sun, 27 Sep 2026 17:36:16 +0200	[thread overview]
Message-ID: <20260927153616.2317-1-yongzhao.derek@gmail.com> (raw)
In-Reply-To: <e18c66e9-7ba2-46c0-baf5-b4281a45755d@lunn.ch>

Hi Andrew,

> Also tricky. What we don't want is other developers trying to abuse
> this to turn it into a configuration option, rather than a hardware
> property. So i don't think it should be a generic property. Lets make
> it a qualcomm specific property. I would also put 'workaround' in the
> property name, again making it clear this is not intended to be used
> for configuration.

Thank you, that makes sense. I'll use a Qualcomm-specific property with
"workaround" in its name, and word the commit message around what has
been observed, as you suggested: an on-board PHY-to-PHY connection
without a cable, where SmartSpeed has been seen to downshift
incorrectly. The workaround would then apply only to boards that set
the property, rather than to every QCA8337 internal CPU PHY as in v3.

One correction to the data I sent you: as Ziyang pointed out, the
IPQ5018 short-cable DAC values were not being applied on this board,
because the driver does not shift the field value. My earlier A/B runs
were therefore done without them. I have repeated the A/B with the DAC
values corrected, and the result is the same. The details are in my
reply to Ziyang in this thread.

Before sending the next revision, I would like to check one more
thing. In these boots the QCA8337 CPU PHY is reset about 38 s before
the IPQ5018 PHY has its DAC values configured. If setting the DAC before
the switch-side PHY starts negotiating avoids the downshift, that would
suggest fixing the initialisation order rather than adding a DT
workaround. I'll report back on what I find before sending the next
revision. If the workaround is still needed, I'll propose the property
name and binding with it.

Thanks,
Yongzhao Chen

  reply	other threads:[~2026-09-27 15:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 21:58 [RFC PATCH net-next v3 0/5] net: dsa: qca8k: add a QCA8337 CPU PHY consumer Yongzhao Chen
2026-09-23 21:58 ` [RFC PATCH net-next v3 1/5] net: dsa: pass PHY flags when connecting shared ports Yongzhao Chen
2026-09-23 21:58 ` [RFC PATCH net-next v3 2/5] net: dsa: qca8k: serialize CPU MAC pause during MTU changes Yongzhao Chen
2026-09-23 21:58 ` [RFC PATCH net-next v3 3/5] net: dsa: qca8k: support QCA8337 internal PHY CPU links Yongzhao Chen
2026-09-23 21:58 ` [RFC PATCH net-next v3 4/5] net: dsa: qca8k: flag QCA8337 internal CPU PHYs for SmartSpeed Yongzhao Chen
2026-09-24  2:51   ` Andrew Lunn
2026-09-24 23:48     ` Yongzhao Chen
2026-09-25 15:17       ` Andrew Lunn
2026-09-25 21:01         ` Yongzhao Chen
2026-09-25 21:26           ` Andrew Lunn
2026-09-26  8:21             ` Yongzhao Chen
2026-09-26 13:11               ` Andrew Lunn
2026-09-26 21:51                 ` Yongzhao Chen
2026-09-27 14:48                   ` Andrew Lunn
2026-09-27 15:36                     ` Yongzhao Chen [this message]
2026-09-28  6:57                       ` Yongzhao Chen
2026-09-28 12:40                         ` Andrew Lunn
2026-09-27  8:05   ` Ziyang Huang
2026-09-27 15:35     ` Yongzhao Chen
2026-09-23 21:58 ` [RFC PATCH net-next v3 5/5] net: phy: qca83xx: disable SmartSpeed before resetting CPU PHYs Yongzhao Chen

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=20260927153616.2317-1-yongzhao.derek@gmail.com \
    --to=yongzhao.derek@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hkallweit1@gmail.com \
    --cc=hzyitc@outlook.com \
    --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=olteanv@gmail.com \
    --cc=pabeni@redhat.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®