* Re: mmc: handling of Under-Voltage Events in eMMC
2023-11-22 11:22 ` mmc: handling of Under-Voltage Events in eMMC Oleksij Rempel
@ 2023-11-22 12:26 ` Mark Brown
2023-11-30 9:06 ` Ulf Hansson
1 sibling, 0 replies; 3+ messages in thread
From: Mark Brown @ 2023-11-22 12:26 UTC (permalink / raw)
To: Oleksij Rempel
Cc: Ulf Hansson, Yang Yingliang, linux-mmc, kernel, Ye Bin,
Heiner Kallweit, Matti Vaittinen, Liam Girdwood, Conor Dooley,
linux-kernel, devicetree, Naresh Solanki, zev, Sebastian Reichel,
linux-pm, Søren Andersen
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
On Wed, Nov 22, 2023 at 12:22:12PM +0100, Oleksij Rempel wrote:
> Some puzzle parts are now mainline, for example regulator framework
> can be configured to detect under-voltage events and execute
> hw_protection_shutdown(). So far it worked good enough to complete
> mmc_poweroff_notify() withing 100ms window. The problem is, the chance to
> execute mmc_poweroff_notify() depends on kernel configuration. If there are too
> many drivers and devices, mmc_poweroff_notify() will be not executed in time.
> For now, I workaround it by registering a reboot notifier for mmc shutdown.
> It works, because kernel_power_off() is executing all registered reboot
> notifiers at first place and there are no other slow reboot notifiers.
> But, it seems to be not reliable enough. Probably notifier prioritization
> is needed to make it more predictable.
> So far, I have two variants to implement it in more predictable way:
> variant 1 - forward the under-voltage notification to the mmc framework and
> execute mmc_poweroff_notify() or bus shutdown.
> variant 2 - use reboot notifier and introduce reboot notifier prioritization.
> Are there other options? What are your preferences?
My instinct is that we want to have prioritisation scheme rather than
something MMC specific, I'd guess that this issue applies in some way to
at least most storage. It's not a super strongly held opinion though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: mmc: handling of Under-Voltage Events in eMMC
2023-11-22 11:22 ` mmc: handling of Under-Voltage Events in eMMC Oleksij Rempel
2023-11-22 12:26 ` Mark Brown
@ 2023-11-30 9:06 ` Ulf Hansson
1 sibling, 0 replies; 3+ messages in thread
From: Ulf Hansson @ 2023-11-30 9:06 UTC (permalink / raw)
To: Oleksij Rempel
Cc: Mark Brown, Yang Yingliang, linux-mmc, kernel, Ye Bin,
Heiner Kallweit, Matti Vaittinen, Liam Girdwood, Conor Dooley,
linux-kernel, devicetree, Naresh Solanki, zev, Sebastian Reichel,
linux-pm, Søren Andersen
On Wed, 22 Nov 2023 at 12:22, Oleksij Rempel <o.rempel@pengutronix.de> wrote:
>
> Hi Ulf, Hi Mark,
>
> On Tue, Oct 10, 2023 at 04:48:24PM +0200, Ulf Hansson wrote:
> > On Fri, 29 Sept 2023 at 15:00, Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> > >
> > > Hi,
> > >
> > > I'm working on a project aiming to protect eMMC during power loss. Our
> > > hardware setup includes an under-voltage detector, circuits to disable
> > > non-critical components, and enough capacitance to allow the CPU to run
> > > for 100ms.
> > >
> > > I've added an interrupt handler to the fixed regulator to emit
> > > REGULATOR_EVENT_UNDER_VOLTAGE events, and modified
> > > drivers/mmc/host/sdhci.c to receive these events. Currently, the handler
> > > only produces debug output.
> > >
> > > What is the recommended approach for handling under-voltage situations?
> > > Should the driver finish ongoing write commands, block new ones, and
> > > shut down the eMMC? I'm looking for direction here.
> >
> > That's indeed a very good question. From a general point of view, I
> > think the best we can do is to stop any new I/O requests from being
> > managed - and try to complete only the last ongoing one, if any.
> > Exactly how to do that can be a bit tricky though.
> >
> > Beyond that, we should probably try to send the eMMC specific commands
> > that allow us to inform the eMMC that it's about to be powered-off.
> > Although, I am not sure that we actually will be able to complete
> > these operations within 100ms, so maybe it's not really worth trying?
> > See mmc_poweroff_notify(), for example.
>
> Some puzzle parts are now mainline, for example regulator framework
> can be configured to detect under-voltage events and execute
> hw_protection_shutdown(). So far it worked good enough to complete
> mmc_poweroff_notify() withing 100ms window. The problem is, the chance to
> execute mmc_poweroff_notify() depends on kernel configuration. If there are too
> many drivers and devices, mmc_poweroff_notify() will be not executed in time.
Right. I have been monitoring the discussions around the series
"[PATCH v1 0/3] introduce priority-based shutdown support", but wanted
to give a reply to $subject patch first.
I think the point here is not to *always make it*, but rather try our
best to improve the situation.
>
> For now, I workaround it by registering a reboot notifier for mmc shutdown.
> It works, because kernel_power_off() is executing all registered reboot
> notifiers at first place and there are no other slow reboot notifiers.
> But, it seems to be not reliable enough. Probably notifier prioritization
> is needed to make it more predictable.
I think I need to have a closer look at the code for such an approach,
to tell if that would work.
My main concern with this, is that we need to make sure the block
device queue needs to be flushed or made quiescent
(mmc_blk_shutdown()) first, so we don't end up processing I/O requests
beyond calling mmc_poweroff_notify().
>
> So far, I have two variants to implement it in more predictable way:
> variant 1 - forward the under-voltage notification to the mmc framework and
> execute mmc_poweroff_notify() or bus shutdown.
> variant 2 - use reboot notifier and introduce reboot notifier prioritization.
>
> Are there other options? What are your preferences?
Something along the variant2 seems to make most sense to me, but I
will continue to look at your other series in this regard.
Kind regards
Uffe
^ permalink raw reply [flat|nested] 3+ messages in thread