[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkXWkaVRp4I1Gj0p@lunn.ch>
Date: Thu, 31 Mar 2022 18:28:01 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Michael Walle <michael@...le.cc>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC net-next 3/3] net: phy: mscc-miim: add support to set
MDIO bus frequency
> @@ -295,21 +323,41 @@ static int mscc_miim_probe(struct platform_device *pdev)
> if (!miim->info)
> return -EINVAL;
>
> - ret = of_mdiobus_register(bus, pdev->dev.of_node);
> + miim->clk = devm_clk_get_optional(&pdev->dev, NULL);
> + if (IS_ERR(miim->clk))
> + return PTR_ERR(miim->clk);
> +
> + ret = clk_prepare_enable(miim->clk);
> + if (ret)
> + return ret;
> +
> + of_property_read_u32(np, "clock-frequency", &miim->clk_freq);
The clock is optional if there is no "clock-frequency" property. If
the property does exist, the clock should be mandatory. I don't think
it should silently fail setting the bus frequency because the clock is
missing.
Andrew
Powered by blists - more mailing lists