From: Chanwoo Choi <chanwoo@kernel.org>
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: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
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 v5 1/2] PM / devfreq: exynos: Use Use devm_clk_get_enabled() helpers
Date: Wed, 26 Jun 2024 23:30:32 +0900 [thread overview]
Message-ID: <15b164aa-601f-4dad-8115-14a715608319@kernel.org> (raw)
In-Reply-To: <CANAwSgTRfEChziyys251-FezSevSq9pxHLJixVCAybJhq5YAqw@mail.gmail.com>
24. 6. 17. 17:24에 Anand Moon 이(가) 쓴 글:
> Hi All,
>
> On Fri, 10 May 2024 at 15:10, Anand Moon <linux.amoon@gmail.com> wrote:
>>
>> 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>
>
> Gentle ping?
>
> Thanks
> -Anand
>
Applied it. Thanks.
I'm sorry for late reply.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
next prev parent reply other threads:[~2024-06-26 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 9:40 Anand Moon
2024-05-10 9:40 ` [PATCH v5 2/2] PM / devfreq: exynos: Use local clk variable instead of exynos_bus member Anand Moon
2024-06-29 13:52 ` Anand Moon
2024-06-17 8:24 ` [PATCH v5 1/2] PM / devfreq: exynos: Use Use devm_clk_get_enabled() helpers Anand Moon
2024-06-26 14:30 ` Chanwoo Choi [this message]
2024-06-29 4:25 ` 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=15b164aa-601f-4dad-8115-14a715608319@kernel.org \
--to=chanwoo@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=christophe.jaillet@wanadoo.fr \
--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
all inboxes | Powered by JetHome®