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>, linux-kernel@vger.kernel.org
Cc: 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: Thu, 1 May 2025 14:01:19 +0100	[thread overview]
Message-ID: <cf4e70e4-9fe5-4697-8744-8c12c41b5ff9@nvidia.com> (raw)
In-Reply-To: <20250318-plat2faux_dev-v2-2-e6cc73f78478@arm.com>

Hi Sudeep,

On 18/03/2025 17:01, Sudeep Holla wrote:
> The PSCI cpuidle driver does not require the creation of a platform
> device. Originally, this approach was chosen for simplicity when the
> driver was first implemented.
> 
> With the introduction of the lightweight faux device interface, we now
> have a more appropriate alternative. Migrate the driver to utilize the
> faux bus, given that the platform device it previously created was not
> a real one anyway. This will simplify the code, reducing its footprint
> while maintaining functionality.
> 
> Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: linux-pm@vger.kernel.org
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>   drivers/cpuidle/cpuidle-psci.c | 32 ++++----------------------------
>   1 file changed, 4 insertions(+), 28 deletions(-)
> 
> diff --git a/drivers/cpuidle/cpuidle-psci.c b/drivers/cpuidle/cpuidle-psci.c
> index 2562dc001fc1de69732ef28f383d2809262a3d96..5d4d6daed36d8540ba2ce3dc54a3180731b03d22 100644
> --- a/drivers/cpuidle/cpuidle-psci.c
> +++ b/drivers/cpuidle/cpuidle-psci.c
> @@ -16,7 +16,7 @@
>   #include <linux/kernel.h>
>   #include <linux/module.h>
>   #include <linux/of.h>
> -#include <linux/platform_device.h>
> +#include <linux/device/faux.h>
>   #include <linux/psci.h>
>   #include <linux/pm_domain.h>
>   #include <linux/pm_runtime.h>
> @@ -404,14 +404,14 @@ static int psci_idle_init_cpu(struct device *dev, int cpu)
>    * to register cpuidle driver then rollback to cancel all CPUs
>    * registration.
>    */
> -static int psci_cpuidle_probe(struct platform_device *pdev)
> +static int psci_cpuidle_probe(struct faux_device *fdev)
>   {
>   	int cpu, ret;
>   	struct cpuidle_driver *drv;
>   	struct cpuidle_device *dev;
>   
>   	for_each_possible_cpu(cpu) {
> -		ret = psci_idle_init_cpu(&pdev->dev, cpu);
> +		ret = psci_idle_init_cpu(&fdev->dev, cpu);
>   		if (ret)
>   			goto out_fail;
>   	}
> @@ -431,28 +431,4 @@ static int psci_cpuidle_probe(struct platform_device *pdev)
>   	return ret;
>   }
>   
> -static struct platform_driver psci_cpuidle_driver = {
> -	.probe = psci_cpuidle_probe,
> -	.driver = {
> -		.name = "psci-cpuidle",
> -	},
> -};
> -
> -static int __init psci_idle_init(void)
> -{
> -	struct platform_device *pdev;
> -	int ret;
> -
> -	ret = platform_driver_register(&psci_cpuidle_driver);
> -	if (ret)
> -		return ret;
> -
> -	pdev = platform_device_register_simple("psci-cpuidle", -1, NULL, 0);
> -	if (IS_ERR(pdev)) {
> -		platform_driver_unregister(&psci_cpuidle_driver);
> -		return PTR_ERR(pdev);
> -	}
> -
> -	return 0;
> -}
> -device_initcall(psci_idle_init);
> +module_faux_driver(psci_cpuidle, psci_cpuidle_probe, NULL, true);
> 


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.

Thanks
Jon

-- 
nvpublic


       reply	other threads:[~2025-05-01 13:01 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   ` Jon Hunter [this message]
2025-05-01 16:07     ` [PATCH v2 2/8] cpuidle: psci: Transition to the faux device interface Sudeep Holla
2025-05-02 10:20       ` Jon Hunter

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=cf4e70e4-9fe5-4697-8744-8c12c41b5ff9@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