linux-kernel - Re: [PATCH v3 20/24] pmdomain: core: Default to use of_genpd_sync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <be41e552-e626-4923-a9e7-15acbafc19e3@nvidia.com>
Date: Fri, 26 Sep 2025 16:32:46 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>, Stephen Boyd <sboyd@...nel.org>,
 linux-pm@...r.kernel.org, "Rafael J . Wysocki" <rafael@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Michael Grzeschik <m.grzeschik@...gutronix.de>,
 Bjorn Andersson <andersson@...nel.org>, Abel Vesa <abel.vesa@...aro.org>,
 Peng Fan <peng.fan@....nxp.com>,
 Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
 Johan Hovold <johan@...nel.org>, Maulik Shah <maulik.shah@....qualcomm.com>,
 Michal Simek <michal.simek@....com>, Konrad Dybcio <konradybcio@...nel.org>,
 Thierry Reding <thierry.reding@...il.com>,
 Hiago De Franco <hiago.franco@...adex.com>,
 Geert Uytterhoeven <geert@...ux-m68k.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v3 20/24] pmdomain: core: Default to use
 of_genpd_sync_state() for genpd providers

On 25/09/2025 23:31, Saravana Kannan wrote:

...

>> I have been doing more testing and do see a lot of "tegra-bpmp bpmp:
>> sync_state() pending due to" on our platforms for basically are driver
>> that is built as a module.
> 
> It being "built as a module" is not reason enough for this warning to
> happen though. One of the main points of fw_devlink is for things to
> work just as well with modules.
> 
> In this particular system, do you never plan to load the modules? Or
> is the module load just missing this timeout by a few seconds or
> something?

We absolutely do load the drivers. Initially, I observed cases where 
drivers are missing, but doing more testing with the necessary drivers 
present, I still see such messages. A lot of our test infrastructure is 
set up to use NFS for mounting to the rootfs and so I am wondering if 
that can also be a factor?

> If these can be turned off, why not turn these off using the sysfs
> file or the timeout commandline option to turn them off? You are
> burning power by leaving these on. A warning seems appropriate to me.

Again the drivers get loaded, so that shouldn't be the case.

Jon

-- 
nvpublic