From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@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: Mon, 14 Mar 2016 23:58:50 -0300 [thread overview]
Message-ID: <56E77A6A.2090604@osg.samsung.com> (raw)
In-Reply-To: <56E772F2.2030507@samsung.com>
Hello Krzysztof,
On 03/14/2016 11:26 PM, Krzysztof Kozlowski wrote:
> On 15.03.2016 10:59, Javier Martinez Canillas wrote:
>>>>
>>>> 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...
>>>
>>
>> Yeah, I don't think we can get rid of the 4 indentation levels since
>> the function already has 3 and a check for the errno code is needed.
>
> Probably handling of the clocks in the driver could be simplified a
> little bit (the if(needs_src_clk) appears in few places)... but this is
> out of scope for this patch.
>
Agreed, I meant without introducing an unrelated change.
>>
>>> 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.
>>>
>>
>> But yes, we can at least get rid of the else statement. I don't have a
>> strong opinion about the debug information, I left it to avoid someone
>> to tell me that I was removing a useful log.
>
> Although dev_dbg doesn't harm... but isn't driver core printing debug
> message already?
>
I don't think it does or at least I didn't find it when looking
at the devm_clk_get() call chain.
> BR,
> Krzysztof
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-03-15 2:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 1:38 [PATCH v3] rtc: s3c: Don't print an error on probe deferral Javier Martinez Canillas
2016-03-15 1:50 ` Krzysztof Kozlowski
2016-03-15 1:59 ` Javier Martinez Canillas
2016-03-15 2:26 ` Krzysztof Kozlowski
2016-03-15 2:58 ` Javier Martinez Canillas [this message]
2016-03-18 11:57 ` Javier Martinez Canillas
2016-03-18 12:07 ` Alexandre Belloni
2016-03-18 12:20 ` [rtc-linux] " Krzysztof Kozlowski
2016-03-18 13:56 ` Javier Martinez Canillas
2016-03-18 13:03 ` Alexandre Belloni
2016-03-18 13:44 ` Javier Martinez Canillas
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=56E77A6A.2090604@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=joe@perches.com \
--cc=k.kozlowski@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox