netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, ramon.nordin.rodriguez@ferroamp.se,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	UNGLinuxDriver@microchip.com, Thorsten.Kummermehr@microchip.com
Subject: Re: [PATCH net-next v2 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1
Date: Tue, 3 Sep 2024 08:30:54 +0100	[thread overview]
Message-ID: <20240903073054.GO23170@kernel.org> (raw)
In-Reply-To: <20240902143458.601578-6-Parthiban.Veerasooran@microchip.com>

On Mon, Sep 02, 2024 at 08:04:56PM +0530, Parthiban Veerasooran wrote:
> This patch adds support for LAN8670/1/2 Rev.C1 as per the latest
> configuration note AN1699 released (Revision E (DS60001699F - June 2024))
> https://www.microchip.com/en-us/application-notes/an1699
> 
> Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>

...

> diff --git a/drivers/net/phy/microchip_t1s.c b/drivers/net/phy/microchip_t1s.c

...

> @@ -290,6 +291,58 @@ static int lan867x_check_reset_complete(struct phy_device *phydev)
>  	return 0;
>  }
>  
> +static int lan867x_revc1_config_init(struct phy_device *phydev)
> +{
> +	s8 offsets[2];
> +	int ret;
> +
> +	ret = lan867x_check_reset_complete(phydev);
> +	if (ret)
> +		return ret;
> +
> +	ret = lan865x_generate_cfg_offsets(phydev, offsets);
> +	if (ret)
> +		return ret;
> +
> +	/* LAN867x Rev.C1 configuration settings are equal to the first 9
> +	 * configuration settings and all the sqi fixup settings from LAN865x
> +	 * Rev.B0/B1. So the same fixup registers and values from LAN865x
> +	 * Rev.B0/B1 are used for LAN867x Rev.C1 to avoid duplication.
> +	 * Refer the below links for the comparision.

nit: comparison

     Flagged by checkpatch.pl --codespell

> +	 * https://www.microchip.com/en-us/application-notes/an1760
> +	 * Revision F (DS60001760G - June 2024)
> +	 * https://www.microchip.com/en-us/application-notes/an1699
> +	 * Revision E (DS60001699F - June 2024)
> +	 */

  reply	other threads:[~2024-09-03  7:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 14:34 [PATCH net-next v2 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 1/7] net: phy: microchip_t1s: restructure cfg read/write functions arguments Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 2/7] net: phy: microchip_t1s: update new initial settings for LAN865X Rev.B0 Parthiban Veerasooran
2024-09-03  6:33   ` Horatiu Vultur
2024-09-04 10:20     ` Parthiban.Veerasooran
2024-09-06  6:37       ` Horatiu Vultur - M31836
2024-09-09  8:36         ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 3/7] net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1 Parthiban Veerasooran
2024-09-03  6:36   ` Horatiu Vultur
2024-09-04 10:30     ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 4/7] net: phy: microchip_t1s: move LAN867X reset handling to a new function Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1 Parthiban Veerasooran
2024-09-03  7:30   ` Simon Horman [this message]
2024-09-04 11:25     ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 6/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2 Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 7/7] net: phy: microchip_t1s: configure collision detection based on PLCA mode Parthiban Veerasooran
2024-09-03  6:43   ` Horatiu Vultur
2024-09-04 11:46     ` Parthiban.Veerasooran
2024-09-06  6:43       ` Horatiu Vultur - M31836
2024-09-09  9:30         ` Parthiban.Veerasooran
2024-09-03  6:24 ` [PATCH net-next v2 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Horatiu Vultur
2024-09-04 11:28   ` Parthiban.Veerasooran

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=20240903073054.GO23170@kernel.org \
    --to=horms@kernel.org \
    --cc=Parthiban.Veerasooran@microchip.com \
    --cc=Thorsten.Kummermehr@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@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=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ramon.nordin.rodriguez@ferroamp.se \
    /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;
as well as URLs for NNTP newsgroup(s).