From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
Yang Yingliang <yangyingliang@huawei.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org, wens@csie.org
Subject: Re: [PATCH -next 1/3] clk: sunxi-ng: sun8i-de2: Use dev_err_probe() helper
Date: Sat, 27 Aug 2022 13:07:17 +0200 [thread overview]
Message-ID: <5859328.lOV4Wx5bFT@jernej-laptop> (raw)
In-Reply-To: <20220827094151.3323450-1-yangyingliang@huawei.com>
Dne sobota, 27. avgust 2022 ob 11:41:49 CEST je Yang Yingliang napisal(a):
> dev_err() can be replace with dev_err_probe() which will check if error
> code is -EPROBE_DEFER.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> ---
> drivers/clk/sunxi-ng/ccu-sun8i-de2.c | 28 +++++++++-------------------
> 1 file changed, 9 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> b/drivers/clk/sunxi-ng/ccu-sun8i-de2.c index 2f6f02f00be2..b70b312e7483
> 100644
> --- a/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> +++ b/drivers/clk/sunxi-ng/ccu-sun8i-de2.c
> @@ -256,29 +256,19 @@ static int sunxi_de2_clk_probe(struct platform_device
> *pdev) return PTR_ERR(reg);
>
> bus_clk = devm_clk_get(&pdev->dev, "bus");
> - if (IS_ERR(bus_clk)) {
> - ret = PTR_ERR(bus_clk);
> - if (ret != -EPROBE_DEFER)
> - dev_err(&pdev->dev, "Couldn't get bus clk:
%d\n", ret);
> - return ret;
> - }
> + if (IS_ERR(bus_clk))
> + return dev_err_probe(&pdev->dev, PTR_ERR(bus_clk),
> + "Couldn't get bus clk\n");
>
> mod_clk = devm_clk_get(&pdev->dev, "mod");
> - if (IS_ERR(mod_clk)) {
> - ret = PTR_ERR(mod_clk);
> - if (ret != -EPROBE_DEFER)
> - dev_err(&pdev->dev, "Couldn't get mod clk:
%d\n", ret);
> - return ret;
> - }
> + if (IS_ERR(mod_clk))
> + return dev_err_probe(&pdev->dev, PTR_ERR(mod_clk),
> + "Couldn't get mod clk\n");
>
> rstc = devm_reset_control_get_exclusive(&pdev->dev, NULL);
> - if (IS_ERR(rstc)) {
> - ret = PTR_ERR(rstc);
> - if (ret != -EPROBE_DEFER)
> - dev_err(&pdev->dev,
> - "Couldn't get reset control:
%d\n", ret);
> - return ret;
> - }
> + if (IS_ERR(rstc))
> + return dev_err_probe(&pdev->dev, PTR_ERR(rstc),
> + "Couldn't get reset
control\n");
>
> /* The clocks need to be enabled for us to access the registers */
> ret = clk_prepare_enable(bus_clk);
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-27 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 9:41 [PATCH -next 1/3] clk: sunxi-ng: sun8i-de2: Use dev_err_probe() helper Yang Yingliang
2022-08-27 9:41 ` [PATCH -next 2/3] clk: sunxi-ng: ccu-sun9i-a80-de: " Yang Yingliang
2022-08-27 11:07 ` Jernej Škrabec
2022-08-27 9:41 ` [PATCH -next 3/3] clk: sunxi-ng: ccu-sun9i-a80-usb: " Yang Yingliang
2022-08-27 11:07 ` Jernej Škrabec
2022-08-27 11:07 ` Jernej Škrabec [this message]
2022-09-08 19:55 ` [PATCH -next 1/3] clk: sunxi-ng: sun8i-de2: " Jernej Škrabec
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=5859328.lOV4Wx5bFT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wens@csie.org \
--cc=yangyingliang@huawei.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