From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Hoan Tran <hoan@os.amperecomputing.com>,
Serge Semin <fancer.lancer@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] gpio: dwapb: Don't print error on -EPROBE_DEFER
Date: Fri, 10 Jun 2022 14:13:51 +0300 [thread overview]
Message-ID: <YqMnb9FjSuU6xd+n@smile.fi.intel.com> (raw)
In-Reply-To: <20220610104500.28774-1-Sergey.Semin@baikalelectronics.ru>
On Fri, Jun 10, 2022 at 01:45:00PM +0300, Serge Semin wrote:
> Currently if the APB or Debounce clocks aren't yet ready to be requested
> the DW GPIO driver will correctly handle that by deferring the probe
> procedure, but the error is still printed to the system log. It needlessly
> pollutes the log since there was no real error but a request to postpone
> the clock request procedure since the clocks subsystem hasn't been fully
> initialized yet. Let's fix that by using the dev_err_probe method to print
> the APB/clock request error status. It will correctly handle the deferred
> probe situation and print the error if it actually happens.
>
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
With or without below nit-pick
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> ---
>
> Link: https://lore.kernel.org/linux-gpio/20220610075152.10214-1-Sergey.Semin@baikalelectronics.ru/
> Changelog v2:
> - Use the dev_err_probe() return value as the return status of the
> corresponding method. (@Philipp Zabel)
> ---
> drivers/gpio/gpio-dwapb.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpio/gpio-dwapb.c b/drivers/gpio/gpio-dwapb.c
> index b0f3aca61974..9467d695a33e 100644
> --- a/drivers/gpio/gpio-dwapb.c
> +++ b/drivers/gpio/gpio-dwapb.c
> @@ -652,10 +652,9 @@ static int dwapb_get_clks(struct dwapb_gpio *gpio)
> gpio->clks[1].id = "db";
> err = devm_clk_bulk_get_optional(gpio->dev, DWAPB_NR_CLOCKS,
> gpio->clks);
> - if (err) {
> - dev_err(gpio->dev, "Cannot get APB/Debounce clocks\n");
> - return err;
> - }
> + if (err)
> + return dev_err_probe(gpio->dev, err,
> + "Cannot get APB/Debounce clocks\n");
I would leave it on one line, checkpatch wouldn't complain even before 100
characters era.
>
> err = clk_bulk_prepare_enable(DWAPB_NR_CLOCKS, gpio->clks);
> if (err) {
> --
> 2.35.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-10 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 7:51 [PATCH] gpio: dwapb: Don't print error on -EPROBE_DEFER Serge Semin
2022-06-10 9:53 ` Serge Semin
2022-06-10 10:45 ` [PATCH v2] " Serge Semin
2022-06-10 11:13 ` Andy Shevchenko [this message]
2022-06-10 20:54 ` Serge Semin
2022-06-10 12:26 ` Bartosz Golaszewski
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=YqMnb9FjSuU6xd+n@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Pavel.Parkhomenko@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=brgl@bgdev.pl \
--cc=fancer.lancer@gmail.com \
--cc=hoan@os.amperecomputing.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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