linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Elder <elder@linaro.org>
To: Heiner Kallweit <hkallweit1@gmail.com>,
	davem@davemloft.net, kuba@kernel.org
Cc: elder@kernel.org, evgreen@chromium.org,
	bjorn.andersson@linaro.org, cpratapa@codeaurora.org,
	subashab@codeaurora.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 2/5] net: ipa: don't report EPROBE_DEFER error
Date: Thu, 11 Feb 2021 16:13:10 -0600	[thread overview]
Message-ID: <b342bbe2-7031-1cc1-6abf-55431f123f5f@linaro.org> (raw)
In-Reply-To: <b1824bb1-5e17-7e5c-98e4-9249fbb1188a@gmail.com>

On 2/11/21 4:11 PM, Heiner Kallweit wrote:
> On 11.02.2021 22:19, Alex Elder wrote:
>> When initializing the IPA core clock and interconnects, it's
>> possible we'll get an EPROBE_DEFER error.  This isn't really an
>> error, it's just means we need to be re-probed later.
>>
>> Check the return code when initializing these, and if it's
>> EPROBE_DEFER, skip printing the error message.
>>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> ---
>>   drivers/net/ipa/ipa_clock.c | 12 ++++++++----
>>   1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ipa/ipa_clock.c b/drivers/net/ipa/ipa_clock.c
>> index 354675a643db5..238a713f6b604 100644
>> --- a/drivers/net/ipa/ipa_clock.c
>> +++ b/drivers/net/ipa/ipa_clock.c
>> @@ -1,7 +1,7 @@
>>   // SPDX-License-Identifier: GPL-2.0
>>   
>>   /* Copyright (c) 2012-2018, The Linux Foundation. All rights reserved.
>> - * Copyright (C) 2018-2020 Linaro Ltd.
>> + * Copyright (C) 2018-2021 Linaro Ltd.
>>    */
>>   
>>   #include <linux/refcount.h>
>> @@ -68,8 +68,9 @@ static int ipa_interconnect_init_one(struct device *dev,
>>   	if (IS_ERR(path)) {
>>   		int ret = PTR_ERR(path);
>>   
>> -		dev_err(dev, "error %d getting %s interconnect\n", ret,
>> -			data->name);
>> +		if (ret != -EPROBE_DEFER)
>> +			dev_err(dev, "error %d getting %s interconnect\n", ret,
>> +				data->name);
>>   
> 
> You may want to use dev_err_probe() here.

Great suggestion, I haven't used that before.

I will post v3 with that suggested change,
tomorrow morning.

Thanks!

					-Alex

>>   		return ret;
>>   	}
>> @@ -281,7 +282,10 @@ ipa_clock_init(struct device *dev, const struct ipa_clock_data *data)
>>   
>>   	clk = clk_get(dev, "core");
>>   	if (IS_ERR(clk)) {
>> -		dev_err(dev, "error %ld getting core clock\n", PTR_ERR(clk));
>> +		ret = PTR_ERR(clk);
>> +		if (ret != -EPROBE_DEFER)
>> +			dev_err(dev, "error %d getting core clock\n", ret);
>> +
>>   		return ERR_CAST(clk);
>>   	}
>>   
>>
> 


  reply	other threads:[~2021-02-11 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 21:19 [PATCH v2 net-next 0/5] net: ipa: some more cleanup Alex Elder
2021-02-11 21:19 ` [PATCH v2 net-next 1/5] net: ipa: use a separate pointer for adjusted GSI memory Alex Elder
2021-02-11 21:19 ` [PATCH v2 net-next 2/5] net: ipa: don't report EPROBE_DEFER error Alex Elder
2021-02-11 22:11   ` Heiner Kallweit
2021-02-11 22:13     ` Alex Elder [this message]
2021-02-11 21:19 ` [PATCH v2 net-next 3/5] net: ipa: fix register write command validation Alex Elder
2021-02-11 21:19 ` [PATCH v2 net-next 4/5] net: ipa: introduce ipa_table_hash_support() Alex Elder
2021-02-11 21:19 ` [PATCH v2 net-next 5/5] net: ipa: introduce gsi_channel_initialized() Alex Elder

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=b342bbe2-7031-1cc1-6abf-55431f123f5f@linaro.org \
    --to=elder@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=evgreen@chromium.org \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=subashab@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;
as well as URLs for NNTP newsgroup(s).