public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "SkyLake Huang (黃啟澤)" <SkyLake.Huang@mediatek.com>
To: "daniel@makrotopia.org" <daniel@makrotopia.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>
Cc: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"Steven Liu (劉人豪)" <steven.liu@mediatek.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"horms@kernel.org" <horms@kernel.org>,
	"dqfext@gmail.com" <dqfext@gmail.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH net-next 1/3] net: phy: mediatek: Add token ring access helper functions in mtk-phy-lib
Date: Fri, 14 Feb 2025 03:35:10 +0000	[thread overview]
Message-ID: <ea348d0a4b30c4926ba16a6e79cb52196aebcf47.camel@mediatek.com> (raw)
In-Reply-To: <81234e04-f37c-4b10-81e6-d8508c9fb487@lunn.ch>

On Thu, 2025-02-13 at 16:34 +0100, Andrew Lunn wrote:
> 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> > > > Those registers with Mrvl* prefix were originally designed for
> > > > connection with certain Marvell devices. It's our DSP
> > > > parameters.
> > > 
> > > Will this code work with real Marvell devices? Is this PHY
> > > actually
> > > licensed from Marvell?
> > 
> > > From what I understood the tuning of those parameters is required
> > to connect to a Marvell PHY link partner on the other end.
> 
> If so, the naming is bad. I assume you need the same settings for
> Microchip, Atheros, Broadcom, etc. These settings just tune the
> hardware to be standards conforming?
> 
>         Andrew
> 
This part is pretty old old old design. Some compatibility issues were
firstly found on Marvell link partners, so the registers are named
accordingly. And yes, now, those Kf/Kp settings will be used for
connection with other link partners. However, if I change the register
names, it violates our hardware register map application note. If this
does bother, I can add some comments before these macros like:

/* Mrvl* prefix only means that in the very beginning we tune the
 * parameters with Marvell link partners. These settings will be used
 * for all link partners now.
 */

BRs,
Sky

  reply	other threads:[~2025-02-14  3:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  1:21 [PATCH net-next 0/3] net: phy: mediatek: Add token-ring ops Sky Huang
2025-01-16  1:21 ` [PATCH net-next 1/3] net: phy: mediatek: Add token ring access helper functions in mtk-phy-lib Sky Huang
2025-01-16 12:55   ` Krzysztof Kozlowski
2025-01-19 17:12   ` Andrew Lunn
2025-02-13  7:39     ` SkyLake Huang (黃啟澤)
2025-02-13 13:29       ` Andrew Lunn
2025-02-13 13:43         ` Daniel Golle
2025-02-13 15:34           ` Andrew Lunn
2025-02-14  3:35             ` SkyLake Huang (黃啟澤) [this message]
2025-02-16 16:39               ` Andrew Lunn
2025-01-16  1:21 ` [PATCH net-next 2/3] net: phy: mediatek: Move some macros to phy-lib for later use Sky Huang
2025-01-19 17:20   ` Andrew Lunn
2025-01-16  1:21 ` [PATCH net-next 3/3] net: phy: mediatek: add driver for built-in 2.5G ethernet PHY on MT7988 Sky Huang
2025-01-16  1:58   ` Daniel Golle
2025-01-19 17:35     ` Andrew Lunn
2025-02-14 13:13     ` SkyLake Huang (黃啟澤)
2025-01-16 12:45   ` Krzysztof Kozlowski
2025-02-14 13:23     ` SkyLake Huang (黃啟澤)
2025-02-14 15:31       ` Krzysztof Kozlowski
2025-01-16 12:51   ` Krzysztof Kozlowski
2025-01-19 17:31   ` Andrew Lunn
2025-02-14 13:25     ` SkyLake Huang (黃啟澤)

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=ea348d0a4b30c4926ba16a6e79cb52196aebcf47.camel@mediatek.com \
    --to=skylake.huang@mediatek.com \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steven.liu@mediatek.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