From: Francesco Dolcini <francesco@dolcini.it>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Christian Loehle <christian.loehle@arm.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Mark Brown" <broonie@kernel.org>,
kernel@pengutronix.de, "Søren Andersen" <san@skov.dk>
Subject: Re: [PATCH v1 0/3] introduce priority-based shutdown support
Date: Thu, 30 Nov 2023 22:59:09 +0100 [thread overview]
Message-ID: <ZWkFrY1k2C_7LovQ@livingston.pivistrello.it> (raw)
In-Reply-To: <20231127113611.GD877872@pengutronix.de>
Hello all,
On Mon, Nov 27, 2023 at 12:36:11PM +0100, Oleksij Rempel wrote:
> On Mon, Nov 27, 2023 at 10:13:49AM +0000, Christian Loehle wrote:
> > > Same problem was seen not only in automotive devices, but also in
> > > industrial or agricultural. With other words, it is important enough to bring
> > > some kind of solution mainline.
> > >
> >
> > IMO that is a serious problem with the used storage / eMMC in that case and it
> > is not suitable for industrial/automotive uses?
> > Any industrial/automotive-suitable storage device should detect under-voltage and
> > just treat it as a power-down/loss, and while that isn't nice for the storage device,
> > it really shouldn't be able to brick a device (within <1M cycles anyway).
> > What does the storage module vendor say about this?
>
> Good question. I do not have insights ATM. I'll forward it.
From personal experience I can tell that bricked eMMC devices happen because of
eMMC controller firmware bugs. You might find some recently committed quirk
on this regard.
Waiting for any additional details you might be able to find, given my past
experience I would agree with what Christian wrote.
Francesco
next prev parent reply other threads:[~2023-11-30 21:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 14:53 [PATCH v1 0/3] introduce priority-based shutdown support Oleksij Rempel
2023-11-24 14:53 ` [PATCH v1 1/3] driver core: move core part of device_shutdown() to a separate function Oleksij Rempel
2023-11-24 15:07 ` Greg Kroah-Hartman
2023-11-24 20:04 ` kernel test robot
2023-11-24 14:53 ` [PATCH v1 2/3] driver core: introduce prioritized device shutdown sequence Oleksij Rempel
2023-11-24 15:10 ` Greg Kroah-Hartman
2023-11-24 14:53 ` [PATCH v1 3/3] mmc: core: increase shutdown priority for MMC devices Oleksij Rempel
2023-11-24 15:05 ` [PATCH v1 0/3] introduce priority-based shutdown support Greg Kroah-Hartman
2023-11-24 15:21 ` Mark Brown
2023-11-24 15:27 ` Greg Kroah-Hartman
2023-11-24 15:49 ` Mark Brown
2023-11-24 15:56 ` Greg Kroah-Hartman
2023-11-24 16:32 ` Oleksij Rempel
2023-11-24 17:26 ` Greg Kroah-Hartman
2023-11-24 18:57 ` Oleksij Rempel
2023-11-25 6:51 ` Greg Kroah-Hartman
2023-11-25 8:50 ` Oleksij Rempel
2023-11-25 9:09 ` Greg Kroah-Hartman
2023-11-25 10:30 ` Mark Brown
2023-11-25 14:35 ` Greg Kroah-Hartman
2023-11-25 15:43 ` Mark Brown
2023-11-25 19:58 ` Greg Kroah-Hartman
2023-11-26 10:14 ` Mark Brown
2023-11-26 19:31 ` Oleksij Rempel
2023-11-27 11:27 ` Christian Loehle
2023-11-27 11:44 ` Oleksij Rempel
2023-11-27 11:57 ` Christian Loehle
2023-11-26 19:42 ` Ferry Toth
2023-11-27 14:09 ` Mark Brown
2023-11-27 10:13 ` Christian Loehle
2023-11-27 11:36 ` Oleksij Rempel
2023-11-30 21:59 ` Francesco Dolcini [this message]
2023-11-27 12:54 ` Matti Vaittinen
2023-11-27 13:08 ` Greg Kroah-Hartman
2023-11-27 14:24 ` Mark Brown
2023-11-27 14:49 ` Matti Vaittinen
2023-11-27 16:23 ` Mark Brown
2023-11-30 9:57 ` Ulf Hansson
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=ZWkFrY1k2C_7LovQ@livingston.pivistrello.it \
--to=francesco@dolcini.it \
--cc=broonie@kernel.org \
--cc=christian.loehle@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=san@skov.dk \
--cc=ulf.hansson@linaro.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).