From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org, Kim Christensen <kch@skov.dk>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH 4/6] ARM: i.MX8MP: skov: halt startup until power is good
Date: Mon, 14 Apr 2025 13:11:12 +0200 [thread overview]
Message-ID: <d131210c-40f7-47d5-bf96-ac200ab71cc7@pengutronix.de> (raw)
In-Reply-To: <20250414105638.uxzlbcigm765uyyg@pengutronix.de>
Hello Marco,
On 4/14/25 12:56, Marco Felsch wrote:
> On 25-04-14, Ahmad Fatoum wrote:
>> Hello Marco,
>>
>> On 14.04.25 11:21, Marco Felsch wrote:
>>> On 25-04-14, Ahmad Fatoum wrote:
>>>> Hello Marco,
>>>>
>>>> On 14.04.25 10:40, Marco Felsch wrote:
>>>>> Hi,
>>>>>
>>>>> On 25-04-14, Ahmad Fatoum wrote:
>>>>>> The 24V regulator supplying the system can indicate via a GPIO imminent
>>>>>> voltage loss. The board's capacitors hold enough charge to power the system
>>>>>> a while longer in such a state, but eventually, unless external power is
>>>>>> restored, the brownout detection of the PMIC will kick in.
>>>>>>
>>>>>> For the span of time between voltage drop detection and PMIC brownout,
>>>>>> let's detect this situation and delay startup. This way, Linux can
>>>>>> detect the ongoing voltage loss, power down the eMMC, reboot into
>>>>>> barebox and barebox will delay boot as long as the problem persists.
>>>>>>
>>>>>> Co-developed-by: Kim Christensen <kch@skov.dk>
>>>>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>>>>> ---
>>>>>> arch/arm/boards/skov-imx8mp/lowlevel.c | 60 ++++++++++++++++++++++++++
>>>>>> 1 file changed, 60 insertions(+)
>>>>>>
>>>>>> diff --git a/arch/arm/boards/skov-imx8mp/lowlevel.c b/arch/arm/boards/skov-imx8mp/lowlevel.c
>>>>>> index 637fc50b3f30..d7bd771f259d 100644
>>>>>> --- a/arch/arm/boards/skov-imx8mp/lowlevel.c
>>>>>> +++ b/arch/arm/boards/skov-imx8mp/lowlevel.c
>>>>>> @@ -20,6 +20,9 @@
>>>>>>
>>>>>> extern char __dtb_z_imx8mp_skov_start[];
>>>>>>
>>>>>> +#define PGOOD_PAD_CTRL MUX_PAD_CTRL(MX8MP_PAD_CTL_PUE | \
>>>>>> + MX8MP_PAD_CTL_PE)
>>>>>> +
>>>>>> #define UART_PAD_CTRL MUX_PAD_CTRL(MX8MP_PAD_CTL_DSE6 | \
>>>>>> MX8MP_PAD_CTL_FSEL | \
>>>>>> MX8MP_PAD_CTL_PUE | \
>>>>>> @@ -30,6 +33,12 @@ extern char __dtb_z_imx8mp_skov_start[];
>>>>>> MX8MP_PAD_CTL_PUE | \
>>>>>> MX8MP_PAD_CTL_PE)
>>>>>>
>>>>>> +static inline void led_d1_toggle(bool *on)
>>>>>> +{
>>>>>> + imx8m_gpio_direction_output(IOMEM(MX8MP_GPIO1_BASE_ADDR), 5, *on);
>>>>>> + *on = !*on;
>>>>>> +}
>>>>>> +
>>>>>> static void setup_uart(void)
>>>>>> {
>>>>>> void __iomem *uart = IOMEM(MX8M_UART2_BASE_ADDR);
>>>>>> @@ -67,6 +76,55 @@ static struct pmic_config pca9450_cfg[] = {
>>>>>> { PCA9450_BUCK2OUT_DVS0, 0x14 },
>>>>>> };
>>>>>>
>>>>>> +static inline bool power_good(void)
>>>>>> +{
>>>>>> + /* IMX_SHDN_MF in schematics */
>>>>>> + return imx8m_gpio_val(IOMEM(MX8MP_GPIO4_BASE_ADDR), 23);
>>>>>> +}
>>>>>> +
>>>>>> +static void wait_for_power_good(void)
>>>>>> +{
>>>>>> + void __iomem *gpio4 = IOMEM(MX8MP_GPIO4_BASE_ADDR);
>>>>>> + int timeout_ms = 0;
>>>>>> + bool led_active = true;
>>>>>> +
>>>>>> + imx8mp_setup_pad(MX8MP_PAD_SAI2_RXD0__GPIO4_IO23 | PGOOD_PAD_CTRL);
>>>>>> + imx8m_gpio_direction_input(gpio4, 23);
>>>>>> +
>>>>>> + led_d1_toggle(&led_active);
>>>>>> +
>>>>>> + if (power_good())
>>>>>> + return;
>>>>>> +
>>>>>> + pr_warn("\nDelaying boot until power stabilizes\n");
>>>>>> +
>>>>>> + /* If we reach this, because Linux did a hw_protection_reboot, we don't
>>>>>> + * want to continue booting right away.
>>>>>> + *
>>>>>> + * Thus let's either wait for the condition to subscede or for voltage
>>>>>> + * to reach a low enough level for the PMIC to detect VSYS_UVLO going
>>>>>> + * lower than allowed
>>>>>> + */
>>>>>> +
>>>>>> + while (1) {
>>>>>> + if (power_good()) {
>>>>>> + /* wait 10ms longer and check if it still good */
>>>>>> + udelay(10000);
>>>>>> + if (power_good()) {
>>>>>> + pr_info("IMX_SHDN_MF stuck low for ~%ums.\n", timeout_ms);
>>>>>> + break;
>>>>>> + }
>>>>>> + }
>>>>>> + /* fast blink LED D1 */
>>>>>> + if (timeout_ms % 100 == 0) {
>>>>>> + pr_debug(".");
>>>>>> + led_d1_toggle(&led_active);
>>>>>> + }
>>>>>> + udelay(1000);
>>>>>> + timeout_ms++;
>>>>>> + }
>>>>>> +}
>>>>>> +
>>>>>> static void power_init_board(void)
>>>>>> {
>>>>>> struct pbl_i2c *i2c;
>>>>>> @@ -77,6 +135,8 @@ static void power_init_board(void)
>>>>>> imx8mp_setup_pad(MX8MP_PAD_SAI3_TXD__GPIO5_IO01);
>>>>>> imx8m_gpio_direction_output(IOMEM(MX8MP_GPIO5_BASE_ADDR), 1, 0);
>>>>>>
>>>>>> + wait_for_power_good();
>>>>>
>>>>> out of curiosity, wouldn't it be more useful to do the check right
>>>>> before the system wants to boot the kernel and abort in that case?
>>>>
>>>> How so?
>>>>
>>>> When we have brownout, we usually never make it out of the PBL,
>>>
>>> Okay, since your backup charge is really low already.
>>>
>>>> so I prefer the SoC gets powered off during this loop instead
>>>> of during the RAM setup.
>>>
>>> I understand that to wait for the power to become good again, but what
>>> if the power is getting good and changes to bad again once you entered
>>> barebox? Do you get notified about such an event?
>>>
>>> IMHO the later point a bit more important since this ensures that the
>>> system was in power-good state before we the system starts.
>>
>> Checking just before booting is insufficient anyway, because power good
>> may fluctuate before the Linux driver starts taking care of the power
>> good GPIO. Given that we need to handle this anyway, I don't think
>> it makes much difference whether when we check the power good GPIO
>> during barebox runtime.
>
> I know, but still it is good to check and to wait for power-good state
> before you cont. booting. Like you do for barebox: you wait till the
> power is good or die within the PBL.
I will take note of this, so I can revisit it with Oleksij in the future.
Thanks,
Ahmad
>
> Regards,
> Marco
>
>
>>
>> Cheers,
>> Ahmad
>>
>>>
>>> Regards,
>>> Marco
>>>
>>
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-04-14 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 6:50 [PATCH 1/6] ARM: dts: i.MX8MP: drop now upstream imx8mp-nominal.dtsi Ahmad Fatoum
2025-04-14 6:50 ` [PATCH 2/6] ARM: i.MX8MP: skov: decrease VDD_SOC to 850mV Ahmad Fatoum
2025-04-14 6:50 ` [PATCH 3/6] ARM: i.MX8MP: skov: assert switch reset early Ahmad Fatoum
2025-04-14 6:50 ` [PATCH 4/6] ARM: i.MX8MP: skov: halt startup until power is good Ahmad Fatoum
2025-04-14 8:40 ` Marco Felsch
2025-04-14 8:46 ` Ahmad Fatoum
2025-04-14 9:21 ` Marco Felsch
2025-04-14 9:36 ` Ahmad Fatoum
2025-04-14 10:56 ` Marco Felsch
2025-04-14 11:11 ` Ahmad Fatoum [this message]
2025-04-14 6:50 ` [PATCH 5/6] ARM: skov-imx8mp: print initial > on every boot Ahmad Fatoum
2025-04-14 6:50 ` [PATCH 6/6] ARM: i.MX8MP: skov: add new 7" g07017 variant support Ahmad Fatoum
2025-04-14 8:37 ` [PATCH 1/6] ARM: dts: i.MX8MP: drop now upstream imx8mp-nominal.dtsi Sascha Hauer
2025-04-14 8:46 ` Ahmad Fatoum
2025-04-14 9:19 ` Sascha Hauer
2025-04-15 6:48 ` Sascha Hauer
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=d131210c-40f7-47d5-bf96-ac200ab71cc7@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=kch@skov.dk \
--cc=m.felsch@pengutronix.de \
--cc=o.rempel@pengutronix.de \
/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