From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Anand Moon <linux.amoon@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] PM / devfreq: exynos: Use Use devm_clk_get_enabled() helpers
Date: Thu, 9 May 2024 22:04:57 +0200 [thread overview]
Message-ID: <d2943958-ac80-4158-8e7c-b5493ab713f8@wanadoo.fr> (raw)
In-Reply-To: <20240509064754.10082-1-linux.amoon@gmail.com>
Le 09/05/2024 à 08:47, Anand Moon a écrit :
> The devm_clk_get_enabled() helpers:
> - call devm_clk_get()
> - call clk_prepare_enable() and register what is needed in order to
> call clk_disable_unprepare() when needed, as a managed resource.
>
> This simplifies the code and avoids the calls to clk_disable_unprepare().
>
> While at it, use dev_err_probe consistently, and use its return value
> to return the error code.
>
> Signed-off-by: Anand Moon <linux.amoon@gmail.com>
> ---
> V4 - wrap up the error messagee within 80 char
> v3 - No change
> v2 - No change
> ---
> drivers/devfreq/exynos-bus.c | 22 +++++-----------------
> 1 file changed, 5 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/devfreq/exynos-bus.c b/drivers/devfreq/exynos-bus.c
> index 00118580905a..7d06c476d8e9 100644
> --- a/drivers/devfreq/exynos-bus.c
> +++ b/drivers/devfreq/exynos-bus.c
> @@ -160,7 +160,6 @@ static void exynos_bus_exit(struct device *dev)
> platform_device_unregister(bus->icc_pdev);
>
> dev_pm_opp_of_remove_table(dev);
> - clk_disable_unprepare(bus->clk);
> dev_pm_opp_put_regulators(bus->opp_token);
> }
>
> @@ -171,7 +170,6 @@ static void exynos_bus_passive_exit(struct device *dev)
> platform_device_unregister(bus->icc_pdev);
>
> dev_pm_opp_of_remove_table(dev);
> - clk_disable_unprepare(bus->clk);
> }
>
> static int exynos_bus_parent_parse_of(struct device_node *np,
> @@ -247,23 +245,16 @@ static int exynos_bus_parse_of(struct device_node *np,
> int ret;
>
> /* Get the clock to provide each bus with source clock */
> - bus->clk = devm_clk_get(dev, "bus");
> - if (IS_ERR(bus->clk)) {
> - dev_err(dev, "failed to get bus clock\n");
> - return PTR_ERR(bus->clk);
> - }
> -
> - ret = clk_prepare_enable(bus->clk);
> - if (ret < 0) {
> - dev_err(dev, "failed to get enable clock\n");
> - return ret;
> - }
> + bus->clk = devm_clk_get_enabled(dev, "bus");
> + if (IS_ERR(bus->clk))
> + return dev_err_probe(dev, PTR_ERR(bus->clk),
> + "failed to get bus clock\n");
>
> /* Get the freq and voltage from OPP table to scale the bus freq */
> ret = dev_pm_opp_of_add_table(dev);
> if (ret < 0) {
> dev_err(dev, "failed to get OPP table\n");
> - goto err_clk;
> + return ret;
> }
>
> rate = clk_get_rate(bus->clk);
> @@ -281,8 +272,6 @@ static int exynos_bus_parse_of(struct device_node *np,
>
> err_opp:
> dev_pm_opp_of_remove_table(dev);
> -err_clk:
> - clk_disable_unprepare(bus->clk);
>
> return ret;
> }
> @@ -453,7 +442,6 @@ static int exynos_bus_probe(struct platform_device *pdev)
>
> err:
> dev_pm_opp_of_remove_table(dev);
> - clk_disable_unprepare(bus->clk);
> err_reg:
> dev_pm_opp_put_regulators(bus->opp_token);
>
Hi,
if the patch is correct, I think that clk in struct exynos_bus can be
easily be removed as well.
CJ
_______________________________________________
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:[~2024-05-09 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 6:47 [PATCH v4] PM / devfreq: exynos: Use Use devm_clk_get_enabled() helpers Anand Moon
2024-05-09 20:04 ` Christophe JAILLET [this message]
2024-05-10 8:39 ` Anand Moon
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=d2943958-ac80-4158-8e7c-b5493ab713f8@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=alim.akhtar@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=myungjoo.ham@samsung.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).