From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Vineeth Karumanchi <vineeth.karumanchi@amd.com>, <git@amd.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <harini.katakam@amd.com>, <andrew@lunn.ch>,
<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<michal.simek@amd.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v3 2/2] net: phy: xilinx-gmii2rgmii: Adopt clock support
Date: Tue, 28 May 2024 11:33:12 +0200 [thread overview]
Message-ID: <d104a345-7df1-4fce-a9d4-05f539fc9160@intel.com> (raw)
In-Reply-To: <20240528062008.1594657-3-vineeth.karumanchi@amd.com>
On 28.05.2024 08:20, Vineeth Karumanchi wrote:
> Add clock support to the gmii_to_rgmii IP.
> Make clk optional to keep DTB backward compatibility.
>
> Signed-off-by: Vineeth Karumanchi <vineeth.karumanchi@amd.com>
> ---
Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> drivers/net/phy/xilinx_gmii2rgmii.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/phy/xilinx_gmii2rgmii.c b/drivers/net/phy/xilinx_gmii2rgmii.c
> index 7b1bc5fcef9b..7c51daecf18e 100644
> --- a/drivers/net/phy/xilinx_gmii2rgmii.c
> +++ b/drivers/net/phy/xilinx_gmii2rgmii.c
> @@ -15,6 +15,7 @@
> #include <linux/mii.h>
> #include <linux/mdio.h>
> #include <linux/phy.h>
> +#include <linux/clk.h>
> #include <linux/of_mdio.h>
>
> #define XILINX_GMII2RGMII_REG 0x10
> @@ -85,11 +86,17 @@ static int xgmiitorgmii_probe(struct mdio_device *mdiodev)
> struct device *dev = &mdiodev->dev;
> struct device_node *np = dev->of_node, *phy_node;
> struct gmii2rgmii *priv;
> + struct clk *clkin;
>
> priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> if (!priv)
> return -ENOMEM;
>
> + clkin = devm_clk_get_optional_enabled(dev, NULL);
> + if (IS_ERR(clkin))
> + return dev_err_probe(dev, PTR_ERR(clkin),
> + "Failed to get and enable clock from Device Tree\n");
> +
> phy_node = of_parse_phandle(np, "phy-handle", 0);
> if (!phy_node) {
> dev_err(dev, "Couldn't parse phy-handle\n");
next prev parent reply other threads:[~2024-05-28 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:20 [PATCH net-next v3 0/2] net: xilinx_gmii2rgmii: Add clock support Vineeth Karumanchi
2024-05-28 6:20 ` [PATCH net-next v3 1/2] dt-bindings: " Vineeth Karumanchi
2024-05-28 9:44 ` Krzysztof Kozlowski
2024-05-28 6:20 ` [PATCH net-next v3 2/2] net: phy: xilinx-gmii2rgmii: Adopt " Vineeth Karumanchi
2024-05-28 9:33 ` Wojciech Drewek [this message]
2024-05-29 12:20 ` [PATCH net-next v3 0/2] net: xilinx_gmii2rgmii: Add " patchwork-bot+netdevbpf
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=d104a345-7df1-4fce-a9d4-05f539fc9160@intel.com \
--to=wojciech.drewek@intel.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vineeth.karumanchi@amd.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