From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <olteanv@gmail.com>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>, <robh+dt@kernel.org>,
<pabeni@redhat.com>, <o.rempel@pengutronix.de>,
<edumazet@google.com>, <f.fainelli@gmail.com>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<kuba@kernel.org>
Cc: <linux@armlinux.org.uk>, <kernel@pengutronix.de>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next v1 5/5] net: dsa: microchip: add support for side MDIO interface in LAN937x
Date: Tue, 29 Oct 2024 03:39:33 +0000 [thread overview]
Message-ID: <6eeb92d0791a1c0c77d57c74c85990d1cdeb355d.camel@microchip.com> (raw)
In-Reply-To: <20241026063538.2506143-6-o.rempel@pengutronix.de>
Hi Oleksij,
On Sat, 2024-10-26 at 08:35 +0200, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> diff --git a/drivers/net/dsa/microchip/lan937x_main.c
> b/drivers/net/dsa/microchip/lan937x_main.c
> index 824d9309a3d35..7dfd21d0d2843 100644
> --- a/drivers/net/dsa/microchip/lan937x_main.c
> +++ b/drivers/net/dsa/microchip/lan937x_main.c
> @@ -18,6 +18,47 @@
> #include "ksz9477.h"
> #include "lan937x.h"
>
> +static const u8 lan9370_phy_addr[] = {
> + [0] = 2, /* Port 1, T1 AFE0 */
> + [1] = 3, /* Port 2, T1 AFE1 */
> + [2] = 5, /* Port 3, T1 AFE3 */
> + [3] = 6, /* Port 4, T1 AFE4 */
> + [4] = U8_MAX, /* Port 5, RGMII 2 */
> +};
> +
Is it intentional to not to add support for lan9371 variant switch?
> +static const u8 lan9372_phy_addr[] = {
> + [0] = 2, /* Port 1, T1 AFE0 */
> + [1] = 3, /* Port 2, T1 AFE1 */
> + [2] = 5, /* Port 3, T1 AFE3 */
> + [3] = 8, /* Port 4, TX PHY */
> + [4] = U8_MAX, /* Port 5, RGMII 2 */
> + [5] = U8_MAX, /* Port 6, RGMII 1 */
> + [6] = 6, /* Port 7, T1 AFE4 */
> + [7] = 4, /* Port 8, T1 AFE2 */
> +};
> +
> +static const u8 lan9373_phy_addr[] = {
> + [0] = 2, /* Port 1, T1 AFE0 */
> + [1] = 3, /* Port 2, T1 AFE1 */
> + [2] = 5, /* Port 3, T1 AFE3 */
> + [3] = U8_MAX, /* Port 4, SGMII */
> + [4] = U8_MAX, /* Port 5, RGMII 2 */
> + [5] = U8_MAX, /* Port 6, RGMII 1 */
> + [6] = 6, /* Port 7, T1 AFE4 */
> + [7] = 4, /* Port 8, T1 AFE2 */
> +};
> +
> +static const u8 lan9374_phy_addr[] = {
> + [0] = 2, /* Port 1, T1 AFE0 */
> + [1] = 3, /* Port 2, T1 AFE1 */
> + [2] = 5, /* Port 3, T1 AFE3 */
> + [3] = 7, /* Port 4, T1 AFE5 */
> + [4] = U8_MAX, /* Port 5, RGMII 2 */
> + [5] = U8_MAX, /* Port 6, RGMII 1 */
> + [6] = 6, /* Port 7, T1 AFE4 */
> + [7] = 4, /* Port 8, T1 AFE2 */
> +};
> +
> static int lan937x_cfg(struct ksz_device *dev, u32 addr, u8 bits,
> bool set)
> {
> return regmap_update_bits(ksz_regmap_8(dev), addr, bits, set
> ? bits : 0);
> @@ -30,24 +71,97 @@ static int lan937x_port_cfg(struct ksz_device
> *dev, int port, int offset,
> bits, set ? bits : 0);
> }
>
>
> 2.39.5
>
next prev parent reply other threads:[~2024-10-29 3:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 6:35 [PATCH net-next v1 0/5] Side MDIO Support for LAN937x Switches Oleksij Rempel
2024-10-26 6:35 ` [PATCH net-next v1 1/5] dt-bindings: net: dsa: ksz: add internal MDIO bus description Oleksij Rempel
2024-10-27 23:04 ` Rob Herring (Arm)
2024-10-28 12:09 ` Andrew Lunn
2024-10-26 6:35 ` [PATCH net-next v1 2/5] dt-bindings: net: dsa: ksz: add mdio-parent-bus property for internal MDIO Oleksij Rempel
2024-10-27 23:06 ` Rob Herring (Arm)
2024-10-28 12:09 ` Andrew Lunn
2024-10-26 6:35 ` [PATCH net-next v1 3/5] net: dsa: microchip: Refactor MDIO handling for side MDIO access Oleksij Rempel
2024-10-28 12:08 ` Andrew Lunn
2024-10-26 6:35 ` [PATCH net-next v1 4/5] net: dsa: microchip: cleanup error handling in ksz_mdio_register Oleksij Rempel
2024-10-28 12:09 ` Andrew Lunn
2024-10-26 6:35 ` [PATCH net-next v1 5/5] net: dsa: microchip: add support for side MDIO interface in LAN937x Oleksij Rempel
2024-10-28 12:15 ` Andrew Lunn
2024-10-28 13:43 ` Oleksij Rempel
2024-10-29 3:39 ` Arun.Ramadoss [this message]
2024-10-29 5:15 ` Oleksij Rempel
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=6eeb92d0791a1c0c77d57c74c85990d1cdeb355d.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®