The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Minda Chen <minda.chen@starfivetech.com>,
	Frank <Frank.Sae@motor-comm.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [net-next v3 3/3] net: phy: motorcomm: Add YT8522 100M RMII PHY support
Date: Tue, 12 May 2026 11:16:16 +0200	[thread overview]
Message-ID: <ebabbd70-b406-4aa0-b468-9a71cd7daa0a@redhat.com> (raw)
In-Reply-To: <20260508094522.3952-4-minda.chen@starfivetech.com>

On 5/8/26 11:45 AM, Minda Chen wrote:
> Add YT8522 100M RMII ethernet PHY base driver support, including
> PHY ID and base config init function.
> 
> Signed-off-by: Minda Chen <minda.chen@starfivetech.com>
> ---
>  drivers/net/phy/motorcomm.c | 49 ++++++++++++++++++++++++++++++++++++-
>  1 file changed, 48 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/phy/motorcomm.c b/drivers/net/phy/motorcomm.c
> index ebc24f51e626..13d57aba5487 100644
> --- a/drivers/net/phy/motorcomm.c
> +++ b/drivers/net/phy/motorcomm.c
> @@ -1,6 +1,6 @@
>  // SPDX-License-Identifier: GPL-2.0+
>  /*
> - * Motorcomm 8511/8521/8531/8531S/8821 PHY driver.
> + * Motorcomm 8511/8521/8522/8531/8531S/8821 PHY driver.
>   *
>   * Author: Peter Geis <pgwipeout@gmail.com>
>   * Author: Frank <Frank.Sae@motor-comm.com>
> @@ -14,6 +14,7 @@
>  
>  #define PHY_ID_YT8511		0x0000010a
>  #define PHY_ID_YT8521		0x0000011a
> +#define PHY_ID_YT8522		0x4f51e928
>  #define PHY_ID_YT8531		0x4f51e91b
>  #define PHY_ID_YT8531S		0x4f51e91a
>  #define PHY_ID_YT8821		0x4f51ea19
> @@ -227,6 +228,13 @@
>  #define YT8521_LED_100_ON_EN			BIT(5)
>  #define YT8521_LED_10_ON_EN			BIT(4)
>  
> +#define YT8522_EXTREG_SLEEP_CONTROL		0x2027
> +#define YT8522_EN_SLEEP_SW			15

Sashiko noted that the above value looks unusual/inconsistent with other
register dedinition. Should it be:
						BIT(15)
instead?

Otherwise using GENMASK() would possibly be more clear.

/P


      reply	other threads:[~2026-05-12  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  9:45 [net-next v3 0/3] Add motorcomm 8531s set ds func and 8522 driver Minda Chen
2026-05-08  9:45 ` [net-next v3 1/3] net: phy: motorcomm: move mdio lock out from yt8531_set_ds() Minda Chen
2026-05-12 13:17   ` Maxime Chevallier
2026-05-08  9:45 ` [net-next v3 2/3] net: motorcomm: phy: set drive strength in YT8531s RGMII Minda Chen
2026-05-12 13:32   ` Maxime Chevallier
2026-05-08  9:45 ` [net-next v3 3/3] net: phy: motorcomm: Add YT8522 100M RMII PHY support Minda Chen
2026-05-12  9:16   ` Paolo Abeni [this message]

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=ebabbd70-b406-4aa0-b468-9a71cd7daa0a@redhat.com \
    --to=pabeni@redhat.com \
    --cc=Frank.Sae@motor-comm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minda.chen@starfivetech.com \
    --cc=netdev@vger.kernel.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