From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Cristian Birsan <cristian.birsan@microchip.com>
Subject: Re: [PATCH] ARM: at91: pm: change BU Power Switch to automatic mode
Date: Mon, 9 Dec 2024 09:15:45 +0100 [thread overview]
Message-ID: <af867f52-37f9-4caa-ab6e-8d7e409bbc87@microchip.com> (raw)
In-Reply-To: <32b1ae9d-f55b-43d0-bb24-1fd486440ab6@tuxon.dev>
On 08/12/2024 at 16:48, Claudiu Beznea wrote:
> On 25.11.2024 18:56, nicolas.ferre@microchip.com wrote:
>> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>>
>> Change how the Backup Unit Power is configured and force the
>> automatic/hardware mode.
>> This change eliminates the need for software management of the power
>> switch, ensuring it transitions to the backup power source before
>> entering low power modes.
>>
>> This is done in the only locaton where this swich was configured. It's
>> usually done in the bootloader.
>>
>> Previously, the loss of the VDDANA (or VDDIN33) power source was not
>> automatically compensated by an alternative power source. This resulted
>> in the loss of Backup Unit content, including Backup Self-refresh low
>> power mode information, OTP emulation configuration, and boot
>> configuration, for instance.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>
> I've added the fixes tag, s/locaton/location, s/swich/switch.
Thanks for your help Claudiu. Regards,
Nicolas
>
> Applied to at91-soc, thanks!
prev parent reply other threads:[~2024-12-09 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 16:56 [PATCH] ARM: at91: pm: change BU Power Switch to automatic mode nicolas.ferre
2024-12-02 8:05 ` Claudiu Beznea
2024-12-02 16:44 ` Nicolas Ferre
2024-12-06 14:14 ` Nicolas Ferre
2024-12-06 14:24 ` Claudiu Beznea
2024-12-08 15:48 ` Claudiu Beznea
2024-12-09 8:15 ` Nicolas Ferre [this message]
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=af867f52-37f9-4caa-ab6e-8d7e409bbc87@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=cristian.birsan@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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