From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-clk <linux-clk@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: prevent __of_clk_get_hw_from_provider() from returning NULL
Date: Wed, 10 Aug 2016 17:16:29 +0900 [thread overview]
Message-ID: <CAK7LNAQL2u1YTxr_SWR6S_2aFPfXAPcaFfkWKSV_D-RU2vq7BQ@mail.gmail.com> (raw)
In-Reply-To: <20160804205734.GA15690@codeaurora.org>
2016-08-05 5:57 GMT+09:00 Stephen Boyd <sboyd@codeaurora.org>:
> On 07/19, Masahiro Yamada wrote:
>> The .get(_hw) callback of an OF clock provider can return a NULL
>> pointer in some cases.
>>
>> For example, of_clk_src_onecell_get() returns NULL for index 1 of a
>> sparse array of clocks like follows:
>>
>> clk_num == 3
>> idx 0: UART clk
>> idx 1: NULL (no clk is allocated)
>> idx 2: I2C clk
>>
>> In such cases, clk_get() successfully returns NULL.
>>
>> A problem is that most drivers only check IS_ERR(), like follows:
>>
>> clk = devm_clk_get(dev, NULL);
>> if (IS_ERR(clk))
>> return PTR_ERR(clk);
>>
>> It carries on moving forward and will probably be hit by a different
>> error check with a different error message.
>
> NULL is a valid clk pointer, so we can't really do anything here
> besides rely on driver authors to do the right thing.
I still do not understand this.
I think clk_get() should return > 0 pointer on success,
error-pointer on failure.
I have no idea when NULL is useful as a return value of clk_get().
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-08-10 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 9:03 [PATCH] clk: prevent __of_clk_get_hw_from_provider() from returning NULL Masahiro Yamada
2016-08-04 20:57 ` Stephen Boyd
2016-08-05 8:29 ` Sylwester Nawrocki
2016-08-07 17:05 ` Masahiro Yamada
2016-08-10 8:16 ` Masahiro Yamada [this message]
2016-08-10 23:23 ` Stephen Boyd
2016-08-12 6:59 ` Masahiro Yamada
2016-08-13 7:38 ` Russell King - ARM Linux
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=CAK7LNAQL2u1YTxr_SWR6S_2aFPfXAPcaFfkWKSV_D-RU2vq7BQ@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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