From: <Claudiu.Beznea@microchip.com>
To: <Conor.Dooley@microchip.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [net-next PATCH RESEND 2/2] net: macb: add polarfire soc reset support
Date: Fri, 1 Jul 2022 07:47:34 +0000 [thread overview]
Message-ID: <25230de4-4923-94b3-dcdb-e08efb733850@microchip.com> (raw)
In-Reply-To: <20220701065831.632785-3-conor.dooley@microchip.com>
On 01.07.2022 09:58, Conor Dooley wrote:
> To date, the Microchip PolarFire SoC (MPFS) has been using the
> cdns,macb compatible, however the generic device does not have reset
> support. Add a new compatible & .data for MPFS to hook into the reset
> functionality added for zynqmp support (and make the zynqmp init
> function generic in the process).
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> drivers/net/ethernet/cadence/macb_main.c | 25 +++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c
> index d89098f4ede8..325f0463fd42 100644
> --- a/drivers/net/ethernet/cadence/macb_main.c
> +++ b/drivers/net/ethernet/cadence/macb_main.c
> @@ -4689,33 +4689,32 @@ static const struct macb_config np4_config = {
> .usrio = &macb_default_usrio,
> };
>
> -static int zynqmp_init(struct platform_device *pdev)
> +static int init_reset_optional(struct platform_device *pdev)
It doesn't sound like a good name for this function but I don't have
something better to propose.
> {
> struct net_device *dev = platform_get_drvdata(pdev);
> struct macb *bp = netdev_priv(dev);
> int ret;
>
> if (bp->phy_interface == PHY_INTERFACE_MODE_SGMII) {
> - /* Ensure PS-GTR PHY device used in SGMII mode is ready */
> + /* Ensure PHY device used in SGMII mode is ready */
> bp->sgmii_phy = devm_phy_optional_get(&pdev->dev, NULL);
>
> if (IS_ERR(bp->sgmii_phy)) {
> ret = PTR_ERR(bp->sgmii_phy);
> dev_err_probe(&pdev->dev, ret,
> - "failed to get PS-GTR PHY\n");
> + "failed to get SGMII PHY\n");
> return ret;
> }
>
> ret = phy_init(bp->sgmii_phy);
> if (ret) {
> - dev_err(&pdev->dev, "failed to init PS-GTR PHY: %d\n",
> + dev_err(&pdev->dev, "failed to init SGMII PHY: %d\n",
> ret);
> return ret;
> }
> }
>
> - /* Fully reset GEM controller at hardware level using zynqmp-reset driver,
> - * if mapped in device tree.
> + /* Fully reset controller at hardware level if mapped in device tree
> */
The new comment can fit on a single line.
> ret = device_reset_optional(&pdev->dev);
> if (ret) {
> @@ -4737,7 +4736,7 @@ static const struct macb_config zynqmp_config = {
> MACB_CAPS_GEM_HAS_PTP | MACB_CAPS_BD_RD_PREFETCH,
> .dma_burst_length = 16,
> .clk_init = macb_clk_init,
> - .init = zynqmp_init,
> + .init = init_reset_optional,
> .jumbo_max_len = 10240,
> .usrio = &macb_default_usrio,
> };
> @@ -4751,6 +4750,17 @@ static const struct macb_config zynq_config = {
> .usrio = &macb_default_usrio,
> };
>
> +static const struct macb_config mpfs_config = {
> + .caps = MACB_CAPS_GIGABIT_MODE_AVAILABLE |
> + MACB_CAPS_JUMBO |
> + MACB_CAPS_GEM_HAS_PTP,
Except for zynqmp and default_gem_config the rest of the capabilities for
other SoCs are aligned something like this:
+ .caps = MACB_CAPS_GIGABIT_MODE_AVAILABLE |
+ MACB_CAPS_JUMBO |
+ MACB_CAPS_GEM_HAS_PTP,
To me it looks better to have you caps aligned this way.
Thank you,
Claudiu Beznea
> + .dma_burst_length = 16,
> + .clk_init = macb_clk_init,
> + .init = init_reset_optional,
> + .usrio = &macb_default_usrio,
> + .jumbo_max_len = 10240,
> +};
> +
> static const struct macb_config sama7g5_gem_config = {
> .caps = MACB_CAPS_GIGABIT_MODE_AVAILABLE | MACB_CAPS_CLK_HW_CHG |
> MACB_CAPS_MIIONRGMII,
> @@ -4787,6 +4797,7 @@ static const struct of_device_id macb_dt_ids[] = {
> { .compatible = "cdns,zynqmp-gem", .data = &zynqmp_config},
> { .compatible = "cdns,zynq-gem", .data = &zynq_config },
> { .compatible = "sifive,fu540-c000-gem", .data = &fu540_c000_config },
> + { .compatible = "microchip,mpfs-macb", .data = &mpfs_config },
> { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config },
> { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config },
> { /* sentinel */ }
next prev parent reply other threads:[~2022-07-01 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 6:58 [net-next PATCH RESEND 0/2] PolarFire SoC macb reset support Conor Dooley
2022-07-01 6:58 ` [net-next PATCH RESEND 1/2] dt-bindings: net: cdns,macb: document polarfire soc's macb Conor Dooley
2022-07-01 20:35 ` Rob Herring
2022-07-01 6:58 ` [net-next PATCH RESEND 2/2] net: macb: add polarfire soc reset support Conor Dooley
2022-07-01 7:47 ` Claudiu.Beznea [this message]
2022-07-01 7:55 ` Conor.Dooley
2022-07-01 8:06 ` Conor.Dooley
2022-07-02 15:34 ` Conor.Dooley
2022-07-04 7:07 ` Claudiu.Beznea
2022-07-04 7:31 ` Conor.Dooley
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=25230de4-4923-94b3-dcdb-e08efb733850@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--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=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).