devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Ryan.Wanner@microchip.com, lee@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, sre@kernel.org,
	Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
	p.zabel@pengutronix.de
Cc: linux@armlinux.org.uk, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 12/15] ARM: at91: pm: Enable ULP0 for SAMA7D65
Date: Mon, 17 Feb 2025 09:18:42 +0200	[thread overview]
Message-ID: <b3de47a4-614c-4650-a866-5718b2e2b50a@tuxon.dev> (raw)
In-Reply-To: <5c6910ce-b0e4-47e6-9c9b-f0093d34f4a6@microchip.com>

Hi, Ryan,

On 14.02.2025 20:09, Ryan.Wanner@microchip.com wrote:
> On 2/13/25 01:20, Claudiu Beznea wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Hi, Ryan,
>>
>>
>> On 10.02.2025 23:13, Ryan.Wanner@microchip.com wrote:
>>> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>>>
>>> New clocks are saved to enable ULP0 for SAMA7D65 because this SoC has a
>>> total of 10 main clocks that need to be saved for ULP0 mode.
>>
>> Isn't 9 the total number of MCKs that are handled in the last/first phase
>> of suspend/resume?
> Yes I was including 10 to match the indexing in the mck_count variable.
> Since bgt instruction was suggested I will correct this to reflect the
> true behavior of the change.
>>
>> Also, the state of MCKs are saved/restored for ULP0 and ULP1 as well.
>>
>>>
>>> Add mck_count member to at91_pm_data, this will be used to determine
>>> how many mcks need to be saved. In the mck_count member will also make
>>> sure that no unnecessary clock settings are written during
>>> mck_ps_restore.
>>>
>>> Add SHDWC to ULP0 mapping to clear the SHDWC status after exiting low
>>> power modes.
>>
>> Can you explain why this clear need to be done? The commit message should
>> answer to the "what?" and "why?" questions.
>>
>>>
>>> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
>>> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>> ---
>>>  arch/arm/mach-at91/pm.c              | 19 +++++-
>>>  arch/arm/mach-at91/pm.h              |  1 +
>>>  arch/arm/mach-at91/pm_data-offsets.c |  2 +
>>>  arch/arm/mach-at91/pm_suspend.S      | 97 ++++++++++++++++++++++++++--
>>>  4 files changed, 110 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
>>> index 55cab31ce1ecb..50bada544eede 100644
>>> --- a/arch/arm/mach-at91/pm.c
>>> +++ b/arch/arm/mach-at91/pm.c
>>> @@ -1337,6 +1337,7 @@ struct pmc_info {
>>>       unsigned long uhp_udp_mask;
>>>       unsigned long mckr;
>>>       unsigned long version;
>>> +     unsigned long mck_count;>  };
>>>
>>>  static const struct pmc_info pmc_infos[] __initconst = {
>>> @@ -1344,30 +1345,42 @@ static const struct pmc_info pmc_infos[] __initconst = {
>>>               .uhp_udp_mask = AT91RM9200_PMC_UHP | AT91RM9200_PMC_UDP,
>>>               .mckr = 0x30,
>>>               .version = AT91_PMC_V1,
>>> +             .mck_count = 1,
>>
>> As this member is used only for SAMA7 SoCs I would drop it here and above
>> (where initialized with 1).
>>
>>>       },
>>>
>>>       {
>>>               .uhp_udp_mask = AT91SAM926x_PMC_UHP | AT91SAM926x_PMC_UDP,
>>>               .mckr = 0x30,
>>>               .version = AT91_PMC_V1,
>>> +             .mck_count = 1,
>>>       },
>>>       {
>>>               .uhp_udp_mask = AT91SAM926x_PMC_UHP,
>>>               .mckr = 0x30,
>>>               .version = AT91_PMC_V1,
>>> +             .mck_count = 1,
>>>       },
>>>       {       .uhp_udp_mask = 0,
>>>               .mckr = 0x30,
>>>               .version = AT91_PMC_V1,
>>> +             .mck_count = 1,
>>>       },
>>>       {
>>>               .uhp_udp_mask = AT91SAM926x_PMC_UHP | AT91SAM926x_PMC_UDP,
>>>               .mckr = 0x28,
>>>               .version = AT91_PMC_V2,
>>> +             .mck_count = 1,
>>>       },
>>>       {
>>>               .mckr = 0x28,
>>>               .version = AT91_PMC_V2,
>>> +             .mck_count = 5,
>>
>> I'm not sure mck_count is a good name when used like proposed in this
>> patch. We know that only 4 MCKs need to be handled for SAMA7G5 and 9 for
>> SAMA7D65.
>>
>> Maybe, better change it here to 4 (.mck_count = 4) and to 9 above
>> (.mck_count = 9) and adjust properly the assembly macros (see below)? What
>> do you think?
> 
> Yes I think this is better and cleaner to read. Should this mck_count
> match the pmc_mck_count variable name? Or should this be more
> descriptive or would mcks be sufficient.

mck_count/mcks should be enough. These will be anyway in the context of
pmc_info.

>>
>>> +     },
>>> +     {
>>> +             .uhp_udp_mask = AT91SAM926x_PMC_UHP,
>>> +             .mckr = 0x28,
>>> +             .version = AT91_PMC_V2,
>>> +             .mck_count = 10,
>>>       },
>>>
>>>  };
>>> @@ -1386,7 +1399,7 @@ static const struct of_device_id atmel_pmc_ids[] __initconst = {
>>>       { .compatible = "atmel,sama5d2-pmc", .data = &pmc_infos[1] },
>>>       { .compatible = "microchip,sam9x60-pmc", .data = &pmc_infos[4] },
>>>       { .compatible = "microchip,sam9x7-pmc", .data = &pmc_infos[4] },
>>> -     { .compatible = "microchip,sama7d65-pmc", .data = &pmc_infos[4] },
>>> +     { .compatible = "microchip,sama7d65-pmc", .data = &pmc_infos[6] },
>>>       { .compatible = "microchip,sama7g5-pmc", .data = &pmc_infos[5] },
>>>       { /* sentinel */ },
>>>  };
>>> @@ -1457,6 +1470,7 @@ static void __init at91_pm_init(void (*pm_idle)(void))
>>>       soc_pm.data.uhp_udp_mask = pmc->uhp_udp_mask;
>>>       soc_pm.data.pmc_mckr_offset = pmc->mckr;
>>>       soc_pm.data.pmc_version = pmc->version;
>>> +     soc_pm.data.pmc_mck_count = pmc->mck_count;
>>>
>>>       if (pm_idle)
>>>               arm_pm_idle = pm_idle;
>>> @@ -1659,7 +1673,8 @@ void __init sama7_pm_init(void)
>>>               AT91_PM_STANDBY, AT91_PM_ULP0, AT91_PM_ULP1, AT91_PM_BACKUP,
>>>       };
>>>       static const u32 iomaps[] __initconst = {
>>> -             [AT91_PM_ULP0]          = AT91_PM_IOMAP(SFRBU),
>>> +             [AT91_PM_ULP0]          = AT91_PM_IOMAP(SFRBU) |
>>> +                                       AT91_PM_IOMAP(SHDWC),
>>
>> In theory, as the wakeup sources can also resumes the system from standby
>> (WFI), the shdwc should be mapped for standby, too. Unless I'm wrong and
>> the wakeup sources covered by the SHDWC_SR register don't apply to standby
>> (WFI).
> The device can wake up from an RTT or RTC alarm event on both the
> standby power mode and the ULP0 power mode, since the RTT/RTC are
> included in the SHDWC_SR I think it is safe to have this.
> If I understand what you are asking correctly.

I was asking if the SHDWC should also be mapped for standby like:

        static const u32 iomaps[] __initconst = {

                [AT91_PM_STANDBY]       = AT91_PM_IOMAP(SHDWC) |

                [AT91_PM_ULP0]          = AT91_PM_IOMAP(SFRBU) |

                                          AT91_PM_IOMAP(SHDWC),

                [AT91_PM_ULP1]          = AT91_PM_IOMAP(SFRBU) |

                                          AT91_PM_IOMAP(SHDWC) |

                                          AT91_PM_IOMAP(ETHC),

                [AT91_PM_BACKUP]        = AT91_PM_IOMAP(SFRBU) |

                                          AT91_PM_IOMAP(SHDWC),

        };



>>
>>
>>>               [AT91_PM_ULP1]          = AT91_PM_IOMAP(SFRBU) |
>>>                                         AT91_PM_IOMAP(SHDWC) |
>>>                                         AT91_PM_IOMAP(ETHC),
>>> diff --git a/arch/arm/mach-at91/pm.h b/arch/arm/mach-at91/pm.h
>>> index 53bdc9000e447..ccde9c8728c27 100644
>>> --- a/arch/arm/mach-at91/pm.h
>>> +++ b/arch/arm/mach-at91/pm.h
>>> @@ -39,6 +39,7 @@ struct at91_pm_data {
>>>       unsigned int suspend_mode;
>>>       unsigned int pmc_mckr_offset;
>>>       unsigned int pmc_version;
>>> +     unsigned int pmc_mck_count;
>>>  };
>>>  #endif
>>>
>>> diff --git a/arch/arm/mach-at91/pm_data-offsets.c b/arch/arm/mach-at91/pm_data-offsets.c
>>> index 40bd4e8fe40a5..59a4838038381 100644
>>> --- a/arch/arm/mach-at91/pm_data-offsets.c
>>> +++ b/arch/arm/mach-at91/pm_data-offsets.c
>>> @@ -18,6 +18,8 @@ int main(void)
>>>                                                pmc_mckr_offset));
>>>       DEFINE(PM_DATA_PMC_VERSION,     offsetof(struct at91_pm_data,
>>>                                                pmc_version));
>>> +     DEFINE(PM_DATA_PMC_MCK_COUNT,   offsetof(struct at91_pm_data,
>>> +                                              pmc_mck_count));
>>>
>>>       return 0;
>>>  }
>>> diff --git a/arch/arm/mach-at91/pm_suspend.S b/arch/arm/mach-at91/pm_suspend.S
>>> index e5869cca5e791..2bbcbb26adb28 100644
>>> --- a/arch/arm/mach-at91/pm_suspend.S
>>> +++ b/arch/arm/mach-at91/pm_suspend.S
>>> @@ -814,17 +814,19 @@ sr_dis_exit:
>>>  .endm
>>>
>>>  /**
>>> - * at91_mckx_ps_enable:      save MCK1..4 settings and switch it to main clock
>>> + * at91_mckx_ps_enable:      save MCK settings and switch it to main clock
>>>   *
>>> - * Side effects: overwrites tmp1, tmp2
>>> + * Side effects: overwrites tmp1, tmp2, tmp3
>>>   */
>>>  .macro at91_mckx_ps_enable
>>>  #ifdef CONFIG_SOC_SAMA7
>>>       ldr     pmc, .pmc_base
>>> +     ldr     tmp3, .mck_count
>>>
>>> -     /* There are 4 MCKs we need to handle: MCK1..4 */
>>> +     /* Start at MCK1 and go until MCK_count */
>>
>> s/MCK_count/mck_count to align with the mck_count above.
>>
>>>       mov     tmp1, #1
>>> -e_loop:      cmp     tmp1, #5
>>> +e_loop:
>>> +     cmp     tmp1, tmp3
>>>       beq     e_done
>>
>> If providing mck_count = 4 (for SAMA7G5) and mck_count = 9 (for SAMA7D65)
>> you can change this to:
>>
>>         bqt     e_done
>>
>>>
>>>       /* Write MCK ID to retrieve the settings. */
>>> @@ -850,7 +852,37 @@ e_save_mck3:
>>>       b       e_ps
>>>
>>>  e_save_mck4:
>>> +     cmp     tmp1, #4
>>> +     bne     e_save_mck5
>>>       str     tmp2, .saved_mck4
>>> +     b       e_ps
>>> +
>>> +e_save_mck5:
>>> +     cmp     tmp1, #5
>>> +     bne     e_save_mck6
>>> +     str     tmp2, .saved_mck5
>>> +     b       e_ps
>>> +
>>> +e_save_mck6:
>>> +     cmp     tmp1, #6
>>> +     bne     e_save_mck7
>>> +     str     tmp2, .saved_mck6
>>> +     b       e_ps
>>> +
>>> +e_save_mck7:
>>> +     cmp     tmp1, #7
>>> +     bne     e_save_mck8
>>> +     str     tmp2, .saved_mck7
>>> +     b       e_ps
>>> +
>>> +e_save_mck8:
>>> +     cmp     tmp1, #8
>>> +     bne     e_save_mck9
>>> +     str     tmp2, .saved_mck8
>>> +     b       e_ps
>>> +
>>> +e_save_mck9:
>>> +     str     tmp2, .saved_mck9
>>>
>>>  e_ps:
>>>       /* Use CSS=MAINCK and DIV=1. */
>>> @@ -870,17 +902,19 @@ e_done:
>>>  .endm
>>>
>>>  /**
>>> - * at91_mckx_ps_restore: restore MCK1..4 settings
>>> + * at91_mckx_ps_restore: restore MCKx settings
>>
>> s/MCKx/MCK to align with the description from at91_mckx_ps_enable
>>
>>>   *
>>>   * Side effects: overwrites tmp1, tmp2
>>>   */
>>>  .macro at91_mckx_ps_restore
>>>  #ifdef CONFIG_SOC_SAMA7
>>>       ldr     pmc, .pmc_base
>>> +     ldr     tmp2, .mck_count
>>>
>>> -     /* There are 4 MCKs we need to handle: MCK1..4 */
>>> +     /* Start from MCK1 and go up to MCK_count */
>>>       mov     tmp1, #1
>>> -r_loop:      cmp     tmp1, #5
>>> +r_loop:
>>> +     cmp     tmp1, tmp2
>>>       beq     r_done
>>
>> Same here:
>>         bgt     r_done
>>
>> should be enough if providing mck_count = 4 or 9
>>
>>>
>>>  r_save_mck1:
>>> @@ -902,7 +936,37 @@ r_save_mck3:
>>>       b       r_ps
>>>
>>>  r_save_mck4:
>>> +     cmp     tmp1, #4
>>> +     bne     r_save_mck5
>>>       ldr     tmp2, .saved_mck4
>>> +     b       r_ps
>>> +
>>> +r_save_mck5:
>>> +     cmp     tmp1, #5
>>> +     bne     r_save_mck6
>>> +     ldr     tmp2, .saved_mck5
>>> +     b       r_ps
>>> +
>>> +r_save_mck6:
>>> +     cmp     tmp1, #6
>>> +     bne     r_save_mck7
>>> +     ldr     tmp2, .saved_mck6
>>> +     b       r_ps
>>> +
>>> +r_save_mck7:
>>> +     cmp     tmp1, #7
>>> +     bne     r_save_mck8
>>> +     ldr     tmp2, .saved_mck7
>>> +     b       r_ps
>>> +
>>> +r_save_mck8:
>>> +     cmp     tmp1, #8
>>> +     bne     r_save_mck9
>>> +     ldr     tmp2, .saved_mck8
>>> +     b       r_ps
>>> +
>>> +r_save_mck9:
>>> +     ldr     tmp2, .saved_mck9
>>>
>>>  r_ps:
>>>       /* Write MCK ID to retrieve the settings. */
>>> @@ -921,6 +985,7 @@ r_ps:
>>>       wait_mckrdy tmp1
>>>
>>>       add     tmp1, tmp1, #1
>>> +     ldr     tmp2, .mck_count
>>
>> Or you can add tmp4 for this
>>
>>>       b       r_loop
>>>  r_done:
>>>  #endif
>>> @@ -1045,6 +1110,10 @@ ENTRY(at91_pm_suspend_in_sram)
>>>       str     tmp1, .memtype
>>>       ldr     tmp1, [r0, #PM_DATA_MODE]
>>>       str     tmp1, .pm_mode
>>> +#ifdef CONFIG_SOC_SAMA7
>>> +     ldr     tmp1, [r0, #PM_DATA_PMC_MCK_COUNT]
>>> +     str     tmp1, .mck_count
>>> +#endif
>>>
>>>       /*
>>>        * ldrne below are here to preload their address in the TLB as access
>>> @@ -1132,6 +1201,10 @@ ENDPROC(at91_pm_suspend_in_sram)
>>>       .word 0
>>>  .pmc_version:
>>>       .word 0
>>> +#ifdef CONFIG_SOC_SAMA7
>>> +.mck_count:
>>> +     .word 0
>>> +#endif
>>>  .saved_mckr:
>>>       .word 0
>>>  .saved_pllar:
>>> @@ -1155,6 +1228,16 @@ ENDPROC(at91_pm_suspend_in_sram)
>>>       .word 0
>>>  .saved_mck4:
>>>       .word 0
>>> +.saved_mck5:
>>> +     .word 0
>>> +.saved_mck6:
>>> +     .word 0
>>> +.saved_mck7:
>>> +     .word 0
>>> +.saved_mck8:
>>> +     .word 0
>>> +.saved_mck9:
>>> +     .word 0
>>>  #endif
>>>
>>>  ENTRY(at91_pm_suspend_in_sram_sz)
>>
> 


  reply	other threads:[~2025-02-17  7:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 21:13 [PATCH v2 00/15] Enable Power Modes Support for SAMA7D65 SoC Ryan.Wanner
2025-02-10 21:13 ` [PATCH v2 01/15] dt-bindings: mfd: syscon: add microchip,sama7d65-ddr3phy Ryan.Wanner
2025-02-11  8:12   ` Krzysztof Kozlowski
2025-02-10 21:13 ` [PATCH v2 02/15] dt-bindings: mfd: syscon: add microchip,sama7d65-sfrbu Ryan.Wanner
2025-02-11  8:14   ` Krzysztof Kozlowski
2025-02-13 20:30     ` Conor Dooley
2025-02-14  7:20       ` Krzysztof Kozlowski
2025-02-10 21:13 ` [PATCH v2 03/15] dt-bindings: sram: Add microchip,sama7d65-sram Ryan.Wanner
2025-02-10 21:13 ` [PATCH v2 04/15] dt-bindings: power: reset: atmel,sama5d2-shdwc: Add microchip,sama7d65-shdwc Ryan.Wanner
2025-02-10 21:13 ` [PATCH v2 05/15] dt-bindings: reset: atmel,at91sam9260-reset: add microchip,sama7d65-rstc Ryan.Wanner
2025-02-14  8:27   ` Krzysztof Kozlowski
2025-02-10 21:13 ` [PATCH v2 06/15] dt-bindings: rtc: at91rm9200: add microchip,sama7d65-rtc Ryan.Wanner
2025-02-12  8:18   ` Claudiu Beznea
2025-02-14  8:27   ` Krzysztof Kozlowski
2025-02-10 21:13 ` [PATCH v2 07/15] dt-bindings: at91rm9260-rtt: add microchip,sama7d65-rtt Ryan.Wanner
2025-02-12  8:18   ` Claudiu Beznea
2025-02-14  8:28   ` Krzysztof Kozlowski
2025-02-10 21:13 ` [PATCH v2 08/15] ARM: at91: Add PM support to sama7d65 Ryan.Wanner
2025-02-10 21:13 ` [PATCH v2 09/15] ARM: at91: pm: fix at91_suspend_finish for ZQ calibration Ryan.Wanner
2025-02-12  8:17   ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 10/15] ARM: at91: pm: add DT compatible support for sama7d65 Ryan.Wanner
2025-02-12  8:20   ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 11/15] ARM: at91: PM: Add Backup mode for SAMA7D65 Ryan.Wanner
2025-02-12  8:15   ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 12/15] ARM: at91: pm: Enable ULP0 " Ryan.Wanner
2025-02-13  8:20   ` Claudiu Beznea
2025-02-14 18:09     ` Ryan.Wanner
2025-02-17  7:18       ` Claudiu Beznea [this message]
2025-02-19 15:24         ` Ryan.Wanner
2025-02-24  8:55           ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 13/15] power: reset: at91-sama5d2_shdwc: Add sama7d65 PMC Ryan.Wanner
2025-02-12  8:20   ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 14/15] ARM: dts: microchip: sama7d65: Add Reset and Shutdown and PM support Ryan.Wanner
2025-02-13  8:28   ` Claudiu Beznea
2025-02-10 21:13 ` [PATCH v2 15/15] ARM: dts: microchip: add shutdown controller and rtt timer Ryan.Wanner
2025-02-13  8:30   ` 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=b3de47a4-614c-4650-a866-5718b2e2b50a@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Ryan.Wanner@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sre@kernel.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;
as well as URLs for NNTP newsgroup(s).