linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1] cpuidle: tegra: Correctly handle result of arm_cpuidle_simple_enter()
Date: Thu, 2 Jul 2020 01:49:02 +0300	[thread overview]
Message-ID: <de1d5c68-0714-3b50-9d39-9351950308e7@gmail.com> (raw)
In-Reply-To: <a55f74fd-1105-1576-8f73-d6d3062541ef@nvidia.com>

01.07.2020 16:56, Jon Hunter пишет:
> 
> On 30/06/2020 19:54, Dmitry Osipenko wrote:
>> 30.06.2020 12:02, Jon Hunter пишет:
>>>
>>> On 29/06/2020 23:26, Dmitry Osipenko wrote:
>>>> The arm_cpuidle_simple_enter() returns the entered idle-index and not a
>>>> error code. It happened that TEGRA_C1=index=err=0, and hence this typo
>>>> was difficult to notice in the code since everything happened to work
>>>> properly. This patch fixes the minor typo, it doesn't fix any problem.
>>>
>>> I guess that is dependent on if CPUIDLE is enabled ...
>>>
>>> #ifdef CONFIG_CPU_IDLE
>>> extern int arm_cpuidle_simple_enter(struct cpuidle_device *dev,
>>>                 struct cpuidle_driver *drv, int index);
>>> #else
>>> static inline int arm_cpuidle_simple_enter(struct cpuidle_device *dev,
>>>                  struct cpuidle_driver *drv, int index) { return -ENODEV; }
>>> #endif
>>>
>>> Looks like it could return an error.
>>
>> Hello Jon!
>>
>> The cpuidle's enter() callback returns an index of the entered state on
>> success, on negative value on failure.
> 
> Yes, however, when I read the first sentence of the changelog it seemed
> to suggested it would never return and error code. Perhaps you meant in
> the context of the Tegra CPUIdle driver because CPU_IDLE is always enabled?

Yes, the commit message could be improved in regards to the error
condition clarification. I'll update it in v2, thank you for the suggestion!

>> The negative number *could be* a proper error code, but in the same time
>> it also doesn't matter what's the exact negative value is for the
>> cpuidle's core code. Please see more below!
>>
>>>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>>>> ---
>>>>  drivers/cpuidle/cpuidle-tegra.c | 4 ++--
>>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/cpuidle/cpuidle-tegra.c b/drivers/cpuidle/cpuidle-tegra.c
>>>> index 150045849d78..9e9a9cccd755 100644
>>>> --- a/drivers/cpuidle/cpuidle-tegra.c
>>>> +++ b/drivers/cpuidle/cpuidle-tegra.c
>>>> @@ -236,14 +236,14 @@ static int tegra_cpuidle_enter(struct cpuidle_device *dev,
>>>>  			       int index)
>>>>  {
>>>>  	unsigned int cpu = cpu_logical_map(dev->cpu);
>>>> -	int err;
>>>> +	int err = 0;
>>>>  
>>>>  	index = tegra_cpuidle_adjust_state_index(index, cpu);
>>>>  	if (dev->states_usage[index].disable)
>>>>  		return -1;
>>>>  
>>>>  	if (index == TEGRA_C1)
>>>> -		err = arm_cpuidle_simple_enter(dev, drv, index);
>>>> +		index = arm_cpuidle_simple_enter(dev, drv, index);
>>>>  	else
>>>>  		err = tegra_cpuidle_state_enter(dev, index, cpu);
>>>>  
>>>>
>>>
>>> However, I do think that there is something not right in the error handling
>>> here. Would also be nice to get rid of these -1.
>>
>> IIRC, the -1 was borrowed from some other cpuidle driver, for example
>> cpuidle-psci[1] and coupled.c[2] are returning -1 on a failure.
> 
> Indeed. Maybe we just let sleeping dogs lie in this case.

+1

We could always return to this later on, once there will be a real need.

      reply	other threads:[~2020-07-01 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 22:26 [PATCH v1] cpuidle: tegra: Correctly handle result of arm_cpuidle_simple_enter() Dmitry Osipenko
2020-06-30  9:02 ` Jon Hunter
2020-06-30 18:54   ` Dmitry Osipenko
2020-07-01 13:56     ` Jon Hunter
2020-07-01 22:49       ` Dmitry Osipenko [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=de1d5c68-0714-3b50-9d39-9351950308e7@gmail.com \
    --to=digetx@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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;
as well as URLs for NNTP newsgroup(s).