From: Andrew Lunn <andrew@lunn.ch>
To: nick.hawkins@hpe.com
Cc: christophe.jaillet@wanadoo.fr, simon.horman@corigine.com,
verdun@hpe.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] net: hpe: Add GXP UMAC MDIO
Date: Thu, 17 Aug 2023 03:19:33 +0200 [thread overview]
Message-ID: <16d8e283-79f7-44bb-af5f-b84cdf7c9d79@lunn.ch> (raw)
In-Reply-To: <20230816215220.114118-3-nick.hawkins@hpe.com>
On Wed, Aug 16, 2023 at 04:52:17PM -0500, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> The GXP contains two Universal Ethernet MACs that can be
> connected externally to several physical devices. From an external
> interface perspective the BMC provides two SERDES interface connections
> capable of either SGMII or 1000Base-X operation. The BMC also provides
> a RMII interface for sideband connections to external Ethernet controllers.
>
> The primary MAC (umac0) can be mapped to either SGMII/1000-BaseX
> SERDES interface. The secondary MAC (umac1) can be mapped to only
> the second SGMII/1000-Base X Serdes interface or it can be mapped for
> RMII sideband.
>
> The MDIO(mdio0) interface from the primary MAC (umac0) is used for
> external PHY status and configuration. The MDIO(mdio1) interface from
> the secondary MAC (umac1) is routed to the SGMII/100Base-X IP blocks
I think that is a typo. 100BaseX does not exist, the nearest is 100BaseFX.
> +config GXP_UMAC_MDIO
> + tristate "GXP UMAC mdio support"
> + depends on ARCH_HPE || COMPILE_TEST
> + depends on OF_MDIO && HAS_IOMEM
> + depends on MDIO_DEVRES
> + help
> + Say y here to support the GXP UMAC MDIO bus. The
> + MDIO (mdio0) interface from the primary MAC (umac0)
> + is used for external PHY status and configuration.
> + The MDIO (mdio1) interface from the secondary MAC
> + (umac1) is routed to the SGMII/100Base-X IP blocks
Same here.
> --- a/drivers/net/mdio/Makefile
> +++ b/drivers/net/mdio/Makefile
> @@ -11,6 +11,7 @@ obj-$(CONFIG_MDIO_BCM_UNIMAC) += mdio-bcm-unimac.o
> obj-$(CONFIG_MDIO_BITBANG) += mdio-bitbang.o
> obj-$(CONFIG_MDIO_CAVIUM) += mdio-cavium.o
> obj-$(CONFIG_MDIO_GPIO) += mdio-gpio.o
> +obj-$(CONFIG_GXP_UMAC_MDIO) += mdio-gxp-umac.o
> obj-$(CONFIG_MDIO_HISI_FEMAC) += mdio-hisi-femac.o
Don't you think this looks out of place. The only one not CONFIG_MDIO ?
> +static int umac_mdio_write(struct mii_bus *bus, int phy_id, int reg, u16 value)
> +{
> + struct umac_mdio_priv *umac_mdio = bus->priv;
> + unsigned int status;
> + int ret;
> +
> + writel(value, umac_mdio->base + UMAC_MII_DATA);
...
> + if (ret)
> + dev_err(bus->parent, "mdio read time out\n");
cut/paste error.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2023-08-17 1:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:52 [PATCH v3 0/5] ARM: Add GXP UMAC Support nick.hawkins
2023-08-16 21:52 ` [PATCH v3 1/5] dt-bindings: net: Add HPE GXP UMAC MDIO nick.hawkins
2023-08-17 1:10 ` Andrew Lunn
2023-08-16 21:52 ` [PATCH v3 2/5] net: hpe: Add " nick.hawkins
2023-08-17 1:19 ` Andrew Lunn [this message]
2023-08-16 21:52 ` [PATCH v3 3/5] dt-bindings: net: Add HPE GXP UMAC nick.hawkins
2023-08-17 8:53 ` Conor Dooley
2023-08-16 21:52 ` [PATCH v3 4/5] net: hpe: Add GXP UMAC Driver nick.hawkins
2023-08-17 1:46 ` Andrew Lunn
2023-08-17 19:19 ` Hawkins, Nick
2023-08-17 19:44 ` Andrew Lunn
2023-08-18 20:11 ` Hawkins, Nick
2023-08-18 21:15 ` Andrew Lunn
2023-08-22 19:00 ` Hawkins, Nick
2023-08-22 20:00 ` Andrew Lunn
2023-08-25 18:54 ` Hawkins, Nick
2023-09-04 3:58 ` Andrew Lunn
2023-09-11 21:12 ` Hawkins, Nick
2023-09-12 23:52 ` Andrew Lunn
2023-08-17 7:45 ` Simon Horman
2023-08-16 21:52 ` [PATCH v3 5/5] MAINTAINERS: HPE: Add GXP UMAC Networking Files nick.hawkins
2023-08-17 1:47 ` Andrew Lunn
2023-08-17 1:08 ` [PATCH v3 0/5] ARM: Add GXP UMAC Support Andrew Lunn
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=16d8e283-79f7-44bb-af5f-b84cdf7c9d79@lunn.ch \
--to=andrew@lunn.ch \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.hawkins@hpe.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=simon.horman@corigine.com \
--cc=verdun@hpe.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