From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: dimitri.fedrau@liebherr.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: phy: dp83822: Add support for GPIO2 clock output
Date: Mon, 9 Dec 2024 14:52:05 +0100 [thread overview]
Message-ID: <20241209135205.GA2891@debian> (raw)
In-Reply-To: <bcef90db-ca9d-4c52-9dc5-2f59ae858824@lunn.ch>
Am Mon, Dec 09, 2024 at 02:17:04PM +0100 schrieb Andrew Lunn:
> > #define MII_DP83822_RCSR 0x17
> > #define MII_DP83822_RESET_CTRL 0x1f
> > #define MII_DP83822_GENCFG 0x465
> > +#define MII_DP83822_IOCTRL2 0x463
> > #define MII_DP83822_SOR1 0x467
>
> These are sorted, so the MII_DP83822_IOCTRL2 should go before
> MII_DP83822_GENCFG.
>
Will fix it.
> > + if (dp83822->set_gpio2_clk_out)
> > + phy_modify_mmd(phydev, DP83822_DEVADDR, MII_DP83822_IOCTRL2,
>
> I would of preferred MDIO_MMD_VEND2 rather than DP83822_DEVADDR, but
> having just this one instance correct would look a bit odd.
>
Is it worth fixing it in a separate patch, replacing all DP83822_DEVADDR
with MDIO_MMD_VEND2 ?
> > + ret = of_property_read_u32(dev->of_node, "ti,gpio2-clk-out",
> > + &dp83822->gpio2_clk_out);
> > + if (!ret) {
> > + dp83822->set_gpio2_clk_out = true;
> > + switch (dp83822->gpio2_clk_out) {
> > + case DP83822_CLK_SRC_MAC_IF:
> > + break;
> > + case DP83822_CLK_SRC_XI:
> > + break;
> > + case DP83822_CLK_SRC_INT_REF:
> > + break;
> > + case DP83822_CLK_SRC_RMII_MASTER_MODE_REF:
> > + break;
> > + case DP83822_CLK_SRC_FREE_RUNNING:
> > + break;
> > + case DP83822_CLK_SRC_RECOVERED:
> > + break;
>
> You can list multiple case statements together, and have one break at
> the end.
>
Will fix it.
> I would personally also only have:
>
> > + dp83822->set_gpio2_clk_out = true;
>
> if validation passes, not that it really matters because:
>
>
> > + default:
> > + phydev_err(phydev, "ti,gpio2-clk-out value %u not valid\n",
> > + dp83822->gpio2_clk_out);
> > + return -EINVAL;
> > + }
> > + }
>
Ok.
Dimitri
next prev parent reply other threads:[~2024-12-09 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 8:01 [PATCH net-next 0/2] net: phy: dp83822: Add support for GPIO2 clock output Dimitri Fedrau
2024-12-09 8:01 ` Dimitri Fedrau via B4 Relay
2024-12-09 8:01 ` [PATCH net-next 1/2] dt-bindings: net: " Dimitri Fedrau
2024-12-09 8:01 ` Dimitri Fedrau via B4 Relay
2024-12-09 8:01 ` [PATCH net-next 2/2] net: phy: " Dimitri Fedrau
2024-12-09 8:01 ` Dimitri Fedrau via B4 Relay
2024-12-09 13:17 ` Andrew Lunn
2024-12-09 13:52 ` Dimitri Fedrau [this message]
2024-12-09 14:45 ` 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=20241209135205.GA2891@debian \
--to=dima.fedrau@gmail.com \
--cc=afd@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--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=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.