From: Nishanth Menon <nm@ti.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Markus Schneider-Pargmann <msp@baylibre.com>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Vibhore Vardhan <vibhore@ti.com>,
Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v11 4/4] firmware: ti_sci: add CPU latency constraint management
Date: Tue, 3 Sep 2024 07:45:40 -0500 [thread overview]
Message-ID: <20240903124540.73cdhsf755lyfisa@tartness> (raw)
In-Reply-To: <20240903005422.GA4638@thelio-3990X>
On 17:54-20240902, Nathan Chancellor wrote:
[...]
> > @@ -3669,7 +3671,27 @@ static int ti_sci_prepare_system_suspend(struct ti_sci_info *info)
> > static int __maybe_unused ti_sci_suspend(struct device *dev)
> > {
> > struct ti_sci_info *info = dev_get_drvdata(dev);
> > - int ret;
> > + struct device *cpu_dev, *cpu_dev_max = NULL;
> > + s32 val, cpu_lat = 0;
> > + int i, ret;
> > +
> > + if (info->fw_caps & MSG_FLAG_CAPS_LPM_DM_MANAGED) {
> > + for_each_possible_cpu(i) {
> > + cpu_dev = get_cpu_device(i);
> > + val = dev_pm_qos_read_value(cpu_dev, DEV_PM_QOS_RESUME_LATENCY);
>
> This change is now in -next as commit 458d22d2e064 ("firmware: ti_sci:
> add CPU latency constraint management"), where it breaks the build
> when this driver is built as a module because dev_pm_qos_read_value() is
> not exported to modules:
>
> ERROR: modpost: "dev_pm_qos_read_value" [drivers/firmware/ti_sci.ko] undefined!
>
> Obviously exporting it would fix the build but sometimes that is
> controversial, hence just the report.
Thank you for the report. I will drop the series from my queue for now.
That should give us some time to sort things out properly for the next
window.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-09-03 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 20:16 [PATCH v11 0/4] firmware: ti_sci: Introduce system suspend support Markus Schneider-Pargmann
2024-08-29 20:16 ` [PATCH v11 1/4] firmware: ti_sci: Add support for querying the firmware caps Markus Schneider-Pargmann
2024-08-30 4:29 ` Dhruva Gole
2024-08-29 20:16 ` [PATCH v11 2/4] firmware: ti_sci: Add system suspend and resume call Markus Schneider-Pargmann
2024-08-29 20:16 ` [PATCH v11 3/4] firmware: ti_sci: Introduce Power Management Ops Markus Schneider-Pargmann
2024-08-30 4:35 ` Dhruva Gole
2024-08-29 20:16 ` [PATCH v11 4/4] firmware: ti_sci: add CPU latency constraint management Markus Schneider-Pargmann
2024-09-03 0:54 ` Nathan Chancellor
2024-09-03 12:45 ` Nishanth Menon [this message]
2024-09-03 15:23 ` Markus Schneider-Pargmann
2024-09-01 20:30 ` [PATCH v11 0/4] firmware: ti_sci: Introduce system suspend support Nishanth Menon
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=20240903124540.73cdhsf755lyfisa@tartness \
--to=nm@ti.com \
--cc=d-gole@ti.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nathan@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vibhore@ti.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