From: Jerome Brunet <jbrunet@baylibre.com>
To: Chen Yufan <chenyufan@vivo.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] clk: meson: axg-audio: Use dev_err_probe() to simplfy code
Date: Fri, 30 Aug 2024 16:46:44 +0200 [thread overview]
Message-ID: <1jfrqmrru3.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20240830080103.12811-1-chenyufan@vivo.com> (Chen Yufan's message of "Fri, 30 Aug 2024 16:01:03 +0800")
On Fri 30 Aug 2024 at 16:01, Chen Yufan <chenyufan@vivo.com> wrote:
> Use dev_err_probe() can make code a bit simpler.
It surely does but ...
>
> Signed-off-by: Chen Yufan <chenyufan@vivo.com>
> ---
> drivers/clk/meson/axg-audio.c | 12 ++++--------
Why this driver alone ?
I have nothing against the change you are doing but I would not want to get a
single patch for each and every amlogic clock drivers.
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/clk/meson/axg-audio.c b/drivers/clk/meson/axg-audio.c
> index e03a5bf899c0..0637b05a4c89 100644
> --- a/drivers/clk/meson/axg-audio.c
> +++ b/drivers/clk/meson/axg-audio.c
> @@ -1761,10 +1761,8 @@ static int axg_audio_clkc_probe(struct platform_device *pdev)
> return PTR_ERR(regs);
>
> map = devm_regmap_init_mmio(dev, regs, &axg_audio_regmap_cfg);
> - if (IS_ERR(map)) {
> - dev_err(dev, "failed to init regmap: %ld\n", PTR_ERR(map));
> - return PTR_ERR(map);
> - }
> + if (IS_ERR(map))
> + return dev_err_probe(dev, PTR_ERR(map), "failed to init regmap: %ld\n");
This does not inspire a lot of confidence. Did you perfom any test
before sending this ?
I know you sent a v2 fixing this, but still ...
>
> /* Get the mandatory peripheral clock */
> clk = devm_clk_get_enabled(dev, "pclk");
> @@ -1772,10 +1770,8 @@ static int axg_audio_clkc_probe(struct platform_device *pdev)
> return PTR_ERR(clk);
>
> ret = device_reset(dev);
> - if (ret) {
> - dev_err_probe(dev, ret, "failed to reset device\n");
> - return ret;
> - }
> + if (ret)
> + return dev_err_probe(dev, ret, "failed to reset device\n");
>
> /* Populate regmap for the regmap backed clocks */
> for (i = 0; i < data->regmap_clk_num; i++)
Finally, it does not apply on my tree.
Check the PR sent to Stephen, you'll get all the details.
https://lore.kernel.org/linux-clk/1jjzfyrsbh.fsf@starbuckisacylon.baylibre.com/
--
Jerome
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-08-30 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 8:01 Chen Yufan
2024-08-30 14:46 ` Jerome Brunet [this message]
2024-08-30 17:46 ` Krzysztof Kozlowski
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=1jfrqmrru3.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=chenyufan@vivo.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=opensource.kernel@vivo.com \
--cc=sboyd@kernel.org \
/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
Powered by JetHome