From: Marek Vasut <marex@denx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-pm@vger.kernel.org, Adam Ford <aford173@gmail.com>,
Fabio Estevam <festevam@denx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jacky Bai <ping.bai@nxp.com>, Kevin Hilman <khilman@kernel.org>,
Len Brown <len.brown@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Mark Brown <broonie@kernel.org>,
Martin Kepplinger <martink@posteo.de>,
Pavel Machek <pavel@ucw.cz>, Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-clk@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH 1/3] [RFC] PM: domains: Introduce .power_pre/post_on/off callbacks
Date: Wed, 9 Nov 2022 14:25:51 +0100 [thread overview]
Message-ID: <187e6074-c232-3f56-d3b6-aaefc26eea14@denx.de> (raw)
In-Reply-To: <Y2uoxuAXrVSD0r6k@pendragon.ideasonboard.com>
On 11/9/22 14:19, Laurent Pinchart wrote:
Hi,
[...]
>> @@ -1413,6 +1479,7 @@ static int genpd_restore_noirq(struct device *dev)
>> static void genpd_complete(struct device *dev)
>> {
>> struct generic_pm_domain *genpd;
>> + int ret;
>
> This variable is unused, causing a compilation error.
I suspect only with -Werror, but anyway, already fixed locally, it's a
rebase on latest next artifact.
[...]
>> diff --git a/include/linux/pm_domain.h b/include/linux/pm_domain.h
>> index ebc3516980907..3cf231a27cb1b 100644
>> --- a/include/linux/pm_domain.h
>> +++ b/include/linux/pm_domain.h
>> @@ -134,8 +134,12 @@ struct generic_pm_domain {
>> unsigned int prepared_count; /* Suspend counter of prepared devices */
>> unsigned int performance_state; /* Aggregated max performance state */
>> cpumask_var_t cpus; /* A cpumask of the attached CPUs */
>> + int (*power_off_pre)(struct generic_pm_domain *domain);
>> int (*power_off)(struct generic_pm_domain *domain);
>> + int (*power_off_post)(struct generic_pm_domain *domain);
>> + int (*power_pre_on)(struct generic_pm_domain *domain);
>> int (*power_on)(struct generic_pm_domain *domain);
>> + int (*power_post_on)(struct generic_pm_domain *domain);
>> struct raw_notifier_head power_notifiers; /* Power on/off notifiers */
>> struct opp_table *opp_table; /* OPP table of the genpd */
>> unsigned int (*opp_to_performance_state)(struct generic_pm_domain *genpd,
I am looking more for a feedback on this extension of the callbacks, and
on the overall approach. Is this something which looks OK, or would
there be better way to handle this ?
next prev parent reply other threads:[~2022-11-09 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 1:35 [PATCH 1/3] [RFC] PM: domains: Introduce .power_pre/post_on/off callbacks Marek Vasut
2022-11-08 1:35 ` [PATCH 2/3] [RFC] soc: imx: gpcv2: Split clock prepare from clock enable in the domain Marek Vasut
2022-11-11 8:27 ` Peng Fan
2022-11-08 1:35 ` [PATCH 3/3] [RFC] soc: imx: imx8m-blk-ctrl: " Marek Vasut
2022-11-09 13:19 ` [PATCH 1/3] [RFC] PM: domains: Introduce .power_pre/post_on/off callbacks Laurent Pinchart
2022-11-09 13:25 ` Marek Vasut [this message]
2022-11-14 19:40 ` Ulf Hansson
2022-11-14 20:32 ` Marek Vasut
2022-11-16 12:41 ` Ulf Hansson
2022-11-16 13:25 ` Lucas Stach
2022-11-16 16:30 ` Ulf Hansson
2023-01-04 8:37 ` Peng Fan
2023-01-18 12:55 ` Ulf Hansson
2023-01-18 13:07 ` Marek Vasut
2023-02-16 1:47 ` Peng Fan
2023-02-16 10:48 ` Ulf Hansson
2023-03-01 0:52 ` Peng Fan
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=187e6074-c232-3f56-d3b6-aaefc26eea14@denx.de \
--to=marex@denx.de \
--cc=aford173@gmail.com \
--cc=broonie@kernel.org \
--cc=festevam@denx.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=len.brown@intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=martink@posteo.de \
--cc=p.zabel@pengutronix.de \
--cc=pavel@ucw.cz \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=rafael@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.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