[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z9cxeSm3sLTi2R-P@shell.armlinux.org.uk>
Date: Sun, 16 Mar 2025 20:15:53 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: "Lucien.Jheng" <lucienx123@...il.com>
Cc: andrew@...n.ch, hkallweit1@...il.com, kuba@...nel.org,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
daniel@...rotopia.org, ericwouds@...il.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, joseph.lin@...oha.com,
wenshin.chung@...oha.com
Subject: Re: [PATCH v3 net-next PATCH 1/1] net: phy: air_en8811h: Add clk
provider for CKO pin
On Sun, Mar 16, 2025 at 10:19:00PM +0800, Lucien.Jheng wrote:
> +#define to_en8811h_priv(_hw) \
> + container_of(_hw, struct en8811h_priv, hw)
Maybe better to call this "clk_hw_to_en8811h_priv()" ?
> +static int en8811h_clk_provider_setup(struct device *dev, struct clk_hw *hw)
> +{
> + struct clk_init_data init;
> + int ret;
> +
> + if (!IS_ENABLED(CONFIG_COMMON_CLK))
> + return 0;
> +
> + init.name = devm_kasprintf(dev, GFP_KERNEL, "%s-clk",
> + fwnode_get_name(dev_fwnode(dev)));
Given that this is the clk API, naming a clock with a "-clk" suffix
is redundant. Instead, consider something more descriptive. You say
this is the "CKO" output, so maybe "%s-cko" so that hardware reference
is included in the name.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists