[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFBinCAkW+G9oV+SOJdac50oLezQnbc358dBgs56-RfjPd-zgA@mail.gmail.com>
Date: Wed, 2 Jul 2025 20:40:19 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Da Xue <da@...re.computer>
Cc: Jerome Brunet <jbrunet@...libre.com>, Anand Moon <linux.amoon@...il.com>,
Ulf Hansson <ulf.hansson@...aro.org>, Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>, linux-mmc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] mmc: meson-gx-mmc: add delay during poweroff
On Wed, Jul 2, 2025 at 7:22 PM Da Xue <da@...re.computer> wrote:
>
> On Wed, Jul 2, 2025 at 1:07 PM Jerome Brunet <jbrunet@...libre.com> wrote:
> ...
> > If, as the description suggest, the regulator framework somehow ignore
> > the timing set in DT, maybe this is what needs to be checked ?
>
> The regulator framework only cares about timing for regulator on.
> Regulator off just turns off the regulator and returns without delay.
There's an exception to this: gpio-regulators without an enable-gpios
property. My understanding is that regulator_disable() is a no-op in
that case (meson_mmc_set_ios() even has a comment above the
switch/case statement), see [0].
> The code makes incorrect assumptions. Then the kernel resets the board
> without having enough time.
Can you please name the board you're testing? I'm worried that I'll be
looking at one .dts but you're looking at another one.
Best regards,
Martin
[0] https://elixir.bootlin.com/linux/v6.15/source/drivers/regulator/core.c#L2980
Powered by blists - more mailing lists