From: Nagarjuna Kristam <nkristam@nvidia.com>
To: Jon Hunter <jonathanh@nvidia.com>, <thierry.reding@gmail.com>,
<kishon@ti.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc/tegra: fuse: Add clock error check in tegra_fuse_readl
Date: Tue, 3 Sep 2019 10:29:24 +0530 [thread overview]
Message-ID: <282de63e-6a0f-349f-0df9-a6a54cab6ea3@nvidia.com> (raw)
In-Reply-To: <95734aa4-c7cb-17a2-fa4c-416a5a40b3e6@nvidia.com>
On 02-09-2019 16:15, Jon Hunter wrote:
>
> On 28/08/2019 12:18, Nagarjuna Kristam wrote:
>> Tegra fuse clock handle is retrieved in tegra_fuse_probe().
>> tegra_fuse_readl() is exported symbol, which can be called from drivers
>> at any time. tegra_fuse_readl() enables fuse clock and reads corresponding
>> fuse register offset.
>>
>> Calling tegra_fuse_readl() before tegra_fuse_probe(), will cause data
>> abort. Add DEFER_PROBE error check for fuse clock in tegra_fuse_readl(),
>> to avoid enabling of fuse clock, before clock is available.
>>
>> Signed-off-by: Nagarjuna Kristam <nkristam@nvidia.com>
>> ---
>> drivers/soc/tegra/fuse/fuse-tegra.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/tegra/fuse/fuse-tegra.c b/drivers/soc/tegra/fuse/fuse-tegra.c
>> index 3eb44e6..21b39b7 100644
>> --- a/drivers/soc/tegra/fuse/fuse-tegra.c
>> +++ b/drivers/soc/tegra/fuse/fuse-tegra.c
>> @@ -186,7 +186,7 @@ u32 __init tegra_fuse_read_early(unsigned int offset)
>>
>> int tegra_fuse_readl(unsigned long offset, u32 *value)
>> {
>> - if (!fuse->read)
>> + if (!fuse->read || (PTR_ERR(fuse->clk) == -EPROBE_DEFER))
>> return -EPROBE_DEFER;
>
> What about the case where fuse->clk is NULL or a different error value?
>
> Jon
>
Yes, all error checks are needed, will use IS_ERR as a separate condition for clock.
Thanks,
Nagarjuna
prev parent reply other threads:[~2019-09-03 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 11:18 Nagarjuna Kristam
2019-09-02 10:45 ` Jon Hunter
2019-09-03 4:59 ` Nagarjuna Kristam [this message]
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=282de63e-6a0f-349f-0df9-a6a54cab6ea3@nvidia.com \
--to=nkristam@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®