From: Junyi Zhao <junyi.zhao@amlogic.com>
To: "Jerome Brunet" <jbrunet@baylibre.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Kelvin Zhang via B4 Relay
<devnull+kelvin.zhang.amlogic.com@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
kelvin.zhang@amlogic.com, linux-pwm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v8 1/2] pwm: meson: Add support for Amlogic S4 PWM
Date: Mon, 17 Jun 2024 16:44:13 +0800 [thread overview]
Message-ID: <948ba34a-1e05-45c4-8ba7-66c72bdb6fa5@amlogic.com> (raw)
In-Reply-To: <1jbk44htqr.fsf@starbuckisacylon.baylibre.com>
On 2024/6/14 15:24, Jerome Brunet wrote:
> [ EXTERNAL EMAIL ]
>
> On Thu 13 Jun 2024 at 22:46, Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
>
>> Hello,
>>
>> On Thu, Jun 13, 2024 at 05:54:31PM +0200, Jerome Brunet wrote:
>>>> + for (i = 0; i < MESON_NUM_PWMS; i++) {
>>>> + meson->channels[i].clk = of_clk_get(np, i);
>>>> + if (IS_ERR(meson->channels[i].clk))
>>>> + return dev_err_probe(dev,
>>>> + PTR_ERR(meson->channels[i].clk),
>>>> + "Failed to get clk\n");
>>>
>>> here it is ok but ..
>>>
>>>> +
>>>> + ret = devm_add_action_or_reset(dev, meson_pwm_s4_put_clk,
>>>> + meson->channels[i].clk);
>>>> + if (ret)
>>>> + return dev_err_probe(dev, ret,
>>>> + "Failed to add clk_put action\n");
>>>
>>> ... here, devm_add_action_or_reset cannot defer, so dev_err_probe is not useful.
>>> dev_err() if you must print something. Just "return ret;" would be fine
>>> by me
>>
>> I don't agree. dev_err_probe() has several purposes. Only one of them is
>> handling -EPROBE_DEFER. See also commit
>> 532888a59505da2a3fbb4abac6adad381cedb374.
>
> I was stuck on the -EPROBE_DEFER usage. Thanks for the heads up
>
>>
>> So yes, please use dev_err_probe() also to handle
>> devm_add_action_or_reset().
>
> My point here is also that devm_add_action_or_reset() can only fail on
> memory allocation, like (devm_)kzalloc. Looking around the kernel, we
> tend to not add messages for that and just return the error code,
> presumably because those same 'out of memory' messages would proliferate
> everywhere.
>
>>
>> Best regards
>> Uwe
>
> --
> Jerome
Hi Uwe, I didnt get the clear point.
So, if we need "return ret" directly? or keep "dev_err_probe()" to print?
--
Best regards
Junyi
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-06-17 8:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 11:46 [PATCH v8 0/2] Add support for Amlogic S4 PWM Kelvin Zhang via B4 Relay
2024-06-13 11:46 ` [PATCH v8 1/2] pwm: meson: " Kelvin Zhang via B4 Relay
2024-06-13 15:03 ` [DMARC error][DKIM error] " George Stark
2024-06-13 15:54 ` Jerome Brunet
2024-06-13 20:46 ` Uwe Kleine-König
2024-06-14 7:24 ` Jerome Brunet
2024-06-14 9:02 ` Uwe Kleine-König
2024-06-17 8:44 ` Junyi Zhao [this message]
2024-06-17 14:11 ` Uwe Kleine-König
2024-06-25 9:33 ` Kelvin Zhang
2024-06-25 14:50 ` Uwe Kleine-König
2024-06-27 8:16 ` Uwe Kleine-König
2024-06-13 11:46 ` [PATCH v8 2/2] arm64: dts: amlogic: Add " Kelvin Zhang via B4 Relay
2024-06-27 5:50 ` Uwe Kleine-König
2024-06-27 6:38 ` Kelvin Zhang
2024-06-27 7:52 ` Neil Armstrong
2024-06-27 7:56 ` (subset) [PATCH v8 0/2] Add support for " Neil Armstrong
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=948ba34a-1e05-45c4-8ba7-66c72bdb6fa5@amlogic.com \
--to=junyi.zhao@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+kelvin.zhang.amlogic.com@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=kelvin.zhang@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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