[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250412182737.GA1425287-robh@kernel.org>
Date: Sat, 12 Apr 2025 13:27:37 -0500
From: Rob Herring <robh@...nel.org>
To: Yixun Lan <dlan@...too.org>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org,
spacemit@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: spacemit: add clock support for K1 SoC
On Sat, Apr 12, 2025 at 02:58:11PM +0800, Yixun Lan wrote:
> For SpacemiT K1 SoC's pinctrl, explicitly acquiring clocks in
> the driver instead of relying on bootloader or default hardware
> settings to enable it.
>
> Signed-off-by: Yixun Lan <dlan@...too.org>
> ---
> drivers/pinctrl/spacemit/pinctrl-k1.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/pinctrl/spacemit/pinctrl-k1.c b/drivers/pinctrl/spacemit/pinctrl-k1.c
> index 67e867b04a02ea1887d93aedfdea5bda037f88b1..3805fb09c1bc3b8cf2ccfc22dd25367292b397b9 100644
> --- a/drivers/pinctrl/spacemit/pinctrl-k1.c
> +++ b/drivers/pinctrl/spacemit/pinctrl-k1.c
> @@ -2,6 +2,7 @@
> /* Copyright (c) 2024 Yixun Lan <dlan@...too.org> */
>
> #include <linux/bits.h>
> +#include <linux/clk.h>
> #include <linux/cleanup.h>
> #include <linux/io.h>
> #include <linux/of.h>
> @@ -721,6 +722,7 @@ static int spacemit_pinctrl_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> struct spacemit_pinctrl *pctrl;
> + struct clk *func_clk, *bus_clk;
> const struct spacemit_pinctrl_data *pctrl_data;
> int ret;
>
> @@ -739,6 +741,14 @@ static int spacemit_pinctrl_probe(struct platform_device *pdev)
> if (IS_ERR(pctrl->regs))
> return PTR_ERR(pctrl->regs);
>
> + func_clk = devm_clk_get_optional_enabled(dev, "func");
> + if (IS_ERR(func_clk))
> + return dev_err_probe(dev, PTR_ERR(func_clk), "failed to get func clock\n");
> +
> + bus_clk = devm_clk_get_optional_enabled(dev, "bus");
> + if (IS_ERR(bus_clk))
> + return dev_err_probe(dev, PTR_ERR(bus_clk), "failed to get bus clock\n");
Do you really need these to be optional? Yes, it maintains
compatibility, but if this platform isn't stable, then do you really
need that?
Rob
Powered by blists - more mailing lists