From: Kevin Hilman <khilman@baylibre.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vibhore Vardhan <vibhore@ti.com>, Dhruva Gole <d-gole@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: Re: [PATCH v12 1/5] PM: QoS: Export dev_pm_qos_read_value
Date: Tue, 10 Sep 2024 16:51:51 -0700 [thread overview]
Message-ID: <7hbk0vukx4.fsf@baylibre.com> (raw)
In-Reply-To: <20240904194229.109886-2-msp@baylibre.com>
Markus Schneider-Pargmann <msp@baylibre.com> writes:
> In the ti_sci driver we would like to pass the resume latencies set on
> devices to the firmware so it can decide which power mode is the best to
> choose. To be able to build a driver using this function as a module,
> this function should be exported.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
Tested-by: Kevin Hilman <khilman@baylibre.com>
Rafael, if there are no objects, feel free to take this one via your
tree. Thanks!
Kevin
> ---
> drivers/base/power/qos.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/base/power/qos.c b/drivers/base/power/qos.c
> index bd77f6734f14..ff393cba7649 100644
> --- a/drivers/base/power/qos.c
> +++ b/drivers/base/power/qos.c
> @@ -137,6 +137,7 @@ s32 dev_pm_qos_read_value(struct device *dev, enum dev_pm_qos_req_type type)
>
> return ret;
> }
> +EXPORT_SYMBOL_GPL(dev_pm_qos_read_value);
>
> /**
> * apply_constraint - Add/modify/remove device PM QoS request.
> --
> 2.45.2
next prev parent reply other threads:[~2024-09-10 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 19:42 [PATCH v12 0/5] firmware: ti_sci: Introduce system suspend support Markus Schneider-Pargmann
2024-09-04 19:42 ` [PATCH v12 1/5] PM: QoS: Export dev_pm_qos_read_value Markus Schneider-Pargmann
2024-09-05 6:26 ` Dhruva Gole
2024-09-10 23:51 ` Kevin Hilman [this message]
2024-09-04 19:42 ` [PATCH v12 2/5] firmware: ti_sci: Add support for querying the firmware caps Markus Schneider-Pargmann
2024-09-04 19:42 ` [PATCH v12 3/5] firmware: ti_sci: Add system suspend and resume call Markus Schneider-Pargmann
2024-09-17 11:12 ` Kamlesh Gurudasani
2024-09-04 19:42 ` [PATCH v12 4/5] firmware: ti_sci: Introduce Power Management Ops Markus Schneider-Pargmann
2024-09-04 19:42 ` [PATCH v12 5/5] firmware: ti_sci: add CPU latency constraint management Markus Schneider-Pargmann
2024-09-06 16:01 ` [PATCH v12 0/5] firmware: ti_sci: Introduce system suspend support Kevin Hilman
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=7hbk0vukx4.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kristo@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).