public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-pm@vger.kernel.org,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2 2/8] cpuidle: psci: Transition to the faux device interface
Date: Fri, 2 May 2025 11:20:57 +0100	[thread overview]
Message-ID: <c63d7864-2a1a-40f7-acb7-ba0bc3311fba@nvidia.com> (raw)
In-Reply-To: <20250501-pony-of-undeniable-reverence-f34cb7@sudeepholla>


On 01/05/2025 17:07, Sudeep Holla wrote:

...

>> I have noticed the following error messages on some of our Tegra devices ...
>>
>>   ERR KERN faux psci-cpuidle: probe did not succeed, tearing down the device
>>   ERR KERN CPUidle PSCI: Failed to create psci-cpuidle device
>>
>> I had a quick look at this and this occurs because of the following code in
>> the probe cpuidle-psci driver ...
>>
>>          /*
>>           * If no DT idle states are detected (ret == 0) let the driver
>>           * initialization fail accordingly since there is no reason to
>>           * initialize the idle driver if only wfi is supported, the
>>           * default archictectural back-end already executes wfi
>>           * on idle entry.
>>           */
>>          ret = dt_init_idle_driver(drv, psci_idle_state_match, 1);
>>          if (ret <= 0)
>>                  return ret ? : -ENODEV;
>>
>>
>> So although it could be argued that the error message is valid, I am not
>> sure if there is anything that mandates that we need to have the idle-states
>> present.
>>
>> We are always checking for new kernel errors and so if something new occurs,
>> I am trying to figure out what is the correct way to fix. For this case I am
>> not sure what is best.
>>
> 
> This is another case where probe was failing before too just that faux
> device probe throws the error. I will take a look and see what can be done.
> But yes, we shouldn't throw error if no idle-states are present in the DT.


Yes exactly this was already failing. Thanks for taking a look!

Cheers
Jon

-- 
nvpublic


      reply	other threads:[~2025-05-02 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250318-plat2faux_dev-v2-0-e6cc73f78478@arm.com>
     [not found] ` <20250318-plat2faux_dev-v2-2-e6cc73f78478@arm.com>
2025-05-01 13:01   ` [PATCH v2 2/8] cpuidle: psci: Transition to the faux device interface Jon Hunter
2025-05-01 16:07     ` Sudeep Holla
2025-05-02 10:20       ` Jon Hunter [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=c63d7864-2a1a-40f7-acb7-ba0bc3311fba@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.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