From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-samsung-soc@vger.kernel.org, rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH v3] rtc: s3c: Don't print an error on probe deferral
Date: Tue, 15 Mar 2016 10:50:15 +0900 [thread overview]
Message-ID: <56E76A57.7070104@samsung.com> (raw)
In-Reply-To: <1458005918-7893-1-git-send-email-javier@osg.samsung.com>
On 15.03.2016 10:38, Javier Martinez Canillas wrote:
> The clock and source clock looked up by the driver may not be available
> just because the clock controller driver was not probed yet so printing
> an error in this case is not correct and only adds confusion to users.
>
> However, knowing that a driver's probe was deferred may be useful so it
> can be printed as a debug information.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> ---
>
> Changes in v3:
> - Change debug messages again as suggested by Joe Perches.
>
> Changes in v2:
> - Improve debug messages as suggested by Joe Perches.
>
> drivers/rtc/rtc-s3c.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c
> index ffb860d18701..d01ad7e8078e 100644
> --- a/drivers/rtc/rtc-s3c.c
> +++ b/drivers/rtc/rtc-s3c.c
> @@ -501,18 +501,27 @@ static int s3c_rtc_probe(struct platform_device *pdev)
>
> info->rtc_clk = devm_clk_get(&pdev->dev, "rtc");
> if (IS_ERR(info->rtc_clk)) {
> - dev_err(&pdev->dev, "failed to find rtc clock\n");
> - return PTR_ERR(info->rtc_clk);
> + ret = PTR_ERR(info->rtc_clk);
> + if (ret != -EPROBE_DEFER)
> + dev_err(&pdev->dev, "failed to find rtc clock\n");
> + else
> + dev_dbg(&pdev->dev, "probe deferred due to missing rtc clk\n");
> + return ret;
> }
> clk_prepare_enable(info->rtc_clk);
>
> if (info->data->needs_src_clk) {
> info->rtc_src_clk = devm_clk_get(&pdev->dev, "rtc_src");
> if (IS_ERR(info->rtc_src_clk)) {
> - dev_err(&pdev->dev,
> - "failed to find rtc source clock\n");
> + ret = PTR_ERR(info->rtc_src_clk);
> + if (ret != -EPROBE_DEFER)
> + dev_err(&pdev->dev,
> + "failed to find rtc source clock\n");
> + else
> + dev_dbg(&pdev->dev,
> + "probe deferred due to missing rtc src clk\n");
> clk_disable_unprepare(info->rtc_clk);
> - return PTR_ERR(info->rtc_src_clk);
> + return ret;
> }
> clk_prepare_enable(info->rtc_src_clk);
> }
>
The error path starts looking complicated. This has now 4 indentation
levels...
I agree for removal of error in case of probe deferral because it might
be misleading but I don't see much benefit of a debug message.
Best regards,
Krzysztof
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-samsung-soc@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH v3] rtc: s3c: Don't print an error on probe deferral
Date: Tue, 15 Mar 2016 10:50:15 +0900 [thread overview]
Message-ID: <56E76A57.7070104@samsung.com> (raw)
In-Reply-To: <1458005918-7893-1-git-send-email-javier@osg.samsung.com>
On 15.03.2016 10:38, Javier Martinez Canillas wrote:
> The clock and source clock looked up by the driver may not be available
> just because the clock controller driver was not probed yet so printing
> an error in this case is not correct and only adds confusion to users.
>
> However, knowing that a driver's probe was deferred may be useful so it
> can be printed as a debug information.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> ---
>
> Changes in v3:
> - Change debug messages again as suggested by Joe Perches.
>
> Changes in v2:
> - Improve debug messages as suggested by Joe Perches.
>
> drivers/rtc/rtc-s3c.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c
> index ffb860d18701..d01ad7e8078e 100644
> --- a/drivers/rtc/rtc-s3c.c
> +++ b/drivers/rtc/rtc-s3c.c
> @@ -501,18 +501,27 @@ static int s3c_rtc_probe(struct platform_device *pdev)
>
> info->rtc_clk = devm_clk_get(&pdev->dev, "rtc");
> if (IS_ERR(info->rtc_clk)) {
> - dev_err(&pdev->dev, "failed to find rtc clock\n");
> - return PTR_ERR(info->rtc_clk);
> + ret = PTR_ERR(info->rtc_clk);
> + if (ret != -EPROBE_DEFER)
> + dev_err(&pdev->dev, "failed to find rtc clock\n");
> + else
> + dev_dbg(&pdev->dev, "probe deferred due to missing rtc clk\n");
> + return ret;
> }
> clk_prepare_enable(info->rtc_clk);
>
> if (info->data->needs_src_clk) {
> info->rtc_src_clk = devm_clk_get(&pdev->dev, "rtc_src");
> if (IS_ERR(info->rtc_src_clk)) {
> - dev_err(&pdev->dev,
> - "failed to find rtc source clock\n");
> + ret = PTR_ERR(info->rtc_src_clk);
> + if (ret != -EPROBE_DEFER)
> + dev_err(&pdev->dev,
> + "failed to find rtc source clock\n");
> + else
> + dev_dbg(&pdev->dev,
> + "probe deferred due to missing rtc src clk\n");
> clk_disable_unprepare(info->rtc_clk);
> - return PTR_ERR(info->rtc_src_clk);
> + return ret;
> }
> clk_prepare_enable(info->rtc_src_clk);
> }
>
The error path starts looking complicated. This has now 4 indentation
levels...
I agree for removal of error in case of probe deferral because it might
be misleading but I don't see much benefit of a debug message.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-03-15 1:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 1:38 [rtc-linux] [PATCH v3] rtc: s3c: Don't print an error on probe deferral Javier Martinez Canillas
2016-03-15 1:38 ` Javier Martinez Canillas
2016-03-15 1:50 ` Krzysztof Kozlowski [this message]
2016-03-15 1:50 ` Krzysztof Kozlowski
2016-03-15 1:59 ` [rtc-linux] " Javier Martinez Canillas
2016-03-15 1:59 ` Javier Martinez Canillas
2016-03-15 2:26 ` [rtc-linux] " Krzysztof Kozlowski
2016-03-15 2:26 ` Krzysztof Kozlowski
2016-03-15 2:58 ` [rtc-linux] " Javier Martinez Canillas
2016-03-15 2:58 ` Javier Martinez Canillas
2016-03-18 11:57 ` [rtc-linux] " Javier Martinez Canillas
2016-03-18 11:57 ` Javier Martinez Canillas
2016-03-18 12:07 ` [rtc-linux] " Alexandre Belloni
2016-03-18 12:07 ` Alexandre Belloni
2016-03-18 12:20 ` [rtc-linux] " Krzysztof Kozlowski
2016-03-18 12:20 ` Krzysztof Kozlowski
2016-03-18 13:56 ` Javier Martinez Canillas
2016-03-18 13:56 ` Javier Martinez Canillas
2016-03-18 13:03 ` Alexandre Belloni
2016-03-18 13:03 ` Alexandre Belloni
2016-03-18 13:44 ` [rtc-linux] " Javier Martinez Canillas
2016-03-18 13:44 ` Javier Martinez Canillas
2016-03-18 23:08 ` [rtc-linux] " Alexandre Belloni
2016-03-18 23:08 ` Alexandre Belloni
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=56E76A57.7070104@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=javier@osg.samsung.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rtc-linux@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.