Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-pm@vger.kernel.org,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michael Grzeschik <m.grzeschik@pengutronix.de>,
	Bjorn Andersson <andersson@kernel.org>,
	Abel Vesa <abel.vesa@linaro.org>, Peng Fan <peng.fan@oss.nxp.com>,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
	Johan Hovold <johan@kernel.org>,
	Maulik Shah <maulik.shah@oss.qualcomm.com>,
	Michal Simek <michal.simek@amd.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Hiago De Franco <hiago.franco@toradex.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v3 20/24] pmdomain: core: Default to use of_genpd_sync_state() for genpd providers
Date: Fri, 26 Sep 2025 16:32:46 +0100	[thread overview]
Message-ID: <be41e552-e626-4923-a9e7-15acbafc19e3@nvidia.com> (raw)
In-Reply-To: <CAGETcx9CpOgtPSDK_qPRQ_u58w3fedSFAfFzugXW4eYq2TLECw@mail.gmail.com>


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


  reply	other threads:[~2025-09-26 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250701114733.636510-1-ulf.hansson@linaro.org>
     [not found] ` <CGME20250710122654eucas1p20f1179a9ff22d562d89252f924d34dae@eucas1p2.samsung.com>
     [not found]   ` <20250701114733.636510-22-ulf.hansson@linaro.org>
     [not found]     ` <212a1a56-08a5-48a5-9e98-23de632168d0@samsung.com>
     [not found]       ` <CAPDyKFrPOgWW_=ehCjtqAUR97HoLKmgFNO3bRT50-w6A1LgGFw@mail.gmail.com>
2025-07-15 10:28         ` [PATCH v3 21/24] pmdomain: core: Leave powered-on genpds on until late_initcall_sync Jon Hunter
2025-07-15 11:32           ` Ulf Hansson
2025-07-15 11:34             ` Ulf Hansson
2025-07-31 12:53               ` Jon Hunter
     [not found] ` <20250701114733.636510-21-ulf.hansson@linaro.org>
2025-07-31 15:07   ` [PATCH v3 20/24] pmdomain: core: Default to use of_genpd_sync_state() for genpd providers Jon Hunter
2025-08-11 12:11     ` Ulf Hansson
2025-09-03 12:33       ` Jon Hunter
2025-09-24 11:40         ` Jon Hunter
2025-09-24 15:53           ` Ulf Hansson
2025-09-25  9:34             ` Jon Hunter
2025-09-25 22:31           ` Saravana Kannan
2025-09-26 15:32             ` Jon Hunter [this message]
2025-09-30 11:33               ` Ulf Hansson

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=be41e552-e626-4923-a9e7-15acbafc19e3@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hiago.franco@toradex.com \
    --cc=johan@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=m.grzeschik@pengutronix.de \
    --cc=maulik.shah@oss.qualcomm.com \
    --cc=michal.simek@amd.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=sboyd@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=ulf.hansson@linaro.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