From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: linux-kernel@vger.kernel.org, ludovic.desroches@microchip.com,
linux-arm-kernel@lists.infradead.org, wenyou.yang@atmel.com
Subject: Re: [PATCH v2 2/3] ARM: at91: pm: add per soc validation of pm modes
Date: Tue, 4 Aug 2020 13:42:23 +0200 [thread overview]
Message-ID: <20200804114223.GC7836@piout.net> (raw)
In-Reply-To: <1596539258-20719-3-git-send-email-claudiu.beznea@microchip.com>
Hello,
On 04/08/2020 14:07:37+0300, Claudiu Beznea wrote:
> void __init at91rm9200_pm_init(void)
> {
> + static const int modes[] __initconst = {
You don't need that to be static as it is now local to the function.
> + AT91_PM_STANDBY, AT91_PM_ULP0
> + };
> +
> if (!IS_ENABLED(CONFIG_SOC_AT91RM9200))
> return;
>
> + at91_pm_modes_validate(modes, ARRAY_SIZE(modes));
For rm9200 and at91sam9, I would not allow changing the pm_modes and
simply enforce standby_mode = AT91_PM_STANDBY and suspend_mode =
AT91_PM_ULP0. I don't think you have any user that ever changed that
behaviour also that avoids increasing the boot time for those slow SoCs.
> at91_dt_ramc();
>
> /*
> @@ -838,9 +888,14 @@ void __init at91rm9200_pm_init(void)
>
> void __init sam9x60_pm_init(void)
> {
> + static const int modes[] __initconst = {
> + AT91_PM_STANDBY, AT91_PM_ULP0, AT91_PM_ULP0_FAST, AT91_PM_ULP1,
> + };
> +
> if (!IS_ENABLED(CONFIG_SOC_SAM9X60))
> return;
>
> + at91_pm_modes_validate(modes, ARRAY_SIZE(modes));
> at91_pm_modes_init();
> at91_dt_ramc();
> at91_pm_init(at91sam9x60_idle);
> @@ -851,14 +906,19 @@ void __init sam9x60_pm_init(void)
>
> void __init at91sam9_pm_init(void)
> {
> + static const int modes[] __initconst = {
> + AT91_PM_STANDBY, AT91_PM_ULP0,
> + };
> +
> if (!IS_ENABLED(CONFIG_SOC_AT91SAM9))
> return;
>
> + at91_pm_modes_validate(modes, ARRAY_SIZE(modes));
> at91_dt_ramc();
> at91_pm_init(at91sam9_idle);
> }
>
> -void __init sama5_pm_init(void)
> +static void __init sama5_pm(void)
> {
> if (!IS_ENABLED(CONFIG_SOC_SAMA5))
> return;
> @@ -867,13 +927,32 @@ void __init sama5_pm_init(void)
> at91_pm_init(NULL);
> }
>
> +void __init sama5_pm_init(void)
> +{
> + static const int modes[] __initconst = {
> + AT91_PM_STANDBY, AT91_PM_ULP0, AT91_PM_ULP0_FAST,
> + };
> +
> + if (!IS_ENABLED(CONFIG_SOC_SAMA5))
> + return;
> +
> + at91_pm_modes_validate(modes, ARRAY_SIZE(modes));
> + sama5_pm();
> +}
> +
> void __init sama5d2_pm_init(void)
> {
> + static const int modes[] __initconst = {
> + AT91_PM_STANDBY, AT91_PM_ULP0, AT91_PM_ULP0_FAST, AT91_PM_ULP1,
> + AT91_PM_BACKUP,
> + };
> +
> if (!IS_ENABLED(CONFIG_SOC_SAMA5D2))
> return;
>
> + at91_pm_modes_validate(modes, ARRAY_SIZE(modes));
> at91_pm_modes_init();
> - sama5_pm_init();
> + sama5_pm();
I would call those two directly:
at91_dt_ramc();
at91_pm_init(NULL);
instead of having a function that doesn't do much.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-04 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 11:07 [PATCH v2 0/3] AT91 PM improvements Claudiu Beznea
2020-08-04 11:07 ` [PATCH v2 1/3] ARM: at91: pm: add support for ULP0 fast wakeup Claudiu Beznea
2020-08-04 11:07 ` [PATCH v2 2/3] ARM: at91: pm: add per soc validation of pm modes Claudiu Beznea
2020-08-04 11:42 ` Alexandre Belloni [this message]
2020-08-04 15:00 ` Claudiu.Beznea
2020-08-04 15:08 ` Alexandre Belloni
2020-08-04 15:45 ` Claudiu.Beznea
2020-08-04 15:56 ` Alexandre Belloni
2020-08-04 11:07 ` [PATCH v2 3/3] ARM: at91: pm: of_node_put() after its usage Claudiu Beznea
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=20200804114223.GC7836@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=wenyou.yang@atmel.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).