From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 03/10] block: allow block devices to implement the cdev erase operation
Date: Tue, 30 Jul 2024 13:21:43 +0200 [thread overview]
Message-ID: <ZqjMx1xWl1toOM59@pengutronix.de> (raw)
In-Reply-To: <fed9e44d-dc12-483c-ac02-7e63e2190b72@pengutronix.de>
On Tue, Jul 30, 2024 at 01:10:05PM +0200, Ahmad Fatoum wrote:
> On 30.07.24 10:55, Sascha Hauer wrote:
> > On Tue, Jul 30, 2024 at 09:19:22AM +0200, Ahmad Fatoum wrote:
> >> We mainly implement cdev erase for raw flashes. Many block devices, like
> >> NVMe, SSD or SD/MMC are also flash-based and expose a mechanism or
> >> multiple to trigger an erase on hardware or flash translation layer
> >> level without an accompanied write.
> >>
> >> To make it possible to use this functionality elsewhere in barebox,
> >> let's have the common block device layer pass through the erase
> >> operation, so it may be implemented in a device-specific manner.
> >>
> >> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> >> ---
> >> common/block.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> >> include/block.h | 1 +
> >> 2 files changed, 44 insertions(+)
> >>
> >> diff --git a/common/block.c b/common/block.c
> >> index f55da775a797..b43fcbe6927b 100644
> >> --- a/common/block.c
> >> +++ b/common/block.c
> >> @@ -380,10 +380,45 @@ static int block_op_discard_range(struct cdev *cdev, loff_t count, loff_t offset
> >> return 0;
> >> }
> >>
> >> +static bool region_overlap(loff_t starta, loff_t lena,
> >> + loff_t startb, loff_t lenb)
> >> +{
> >> + if (starta + lena <= startb)
> >> + return 0;
> >> + if (startb + lenb <= starta)
> >> + return 0;
> >> + return 1;
> >> +}
> >
> > We already have this function in fs/devfs-core.c. Time to export it?
>
> This used to be exported, but the export was removed in commit
> 04e2aa516ed5 ("common.h: move and rename lregion_overlap()").
>
> I can add it back if you prefer.
I think now that we have two users it makes sense to add it back.
Sascha
--
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:[~2024-07-30 11:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 7:19 [PATCH 00/10] mmc: add SD/eMMC erase support Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 01/10] fs: give erase() a new erase_type parameter Ahmad Fatoum
2024-07-30 8:31 ` Sascha Hauer
2024-07-30 8:32 ` Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 02/10] block: factor out chunk_flush helper Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 03/10] block: allow block devices to implement the cdev erase operation Ahmad Fatoum
2024-07-30 8:55 ` Sascha Hauer
2024-07-30 11:10 ` Ahmad Fatoum
2024-07-30 11:21 ` Sascha Hauer [this message]
2024-07-30 7:19 ` [PATCH 04/10] mci: turn bool members into bitfield in struct mci Ahmad Fatoum
2024-07-30 9:06 ` Sascha Hauer
2024-07-30 11:10 ` Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 05/10] mci: describe more command structure in mci.h Ahmad Fatoum
2024-07-30 9:25 ` Yann Sionneau
2024-07-30 11:07 ` Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 06/10] mci: core: use CONFIG_MCI_WRITE, not CONFIG_BLOCK_WRITE Ahmad Fatoum
2024-07-30 9:18 ` Sascha Hauer
2024-07-30 11:08 ` Ahmad Fatoum
2024-07-31 7:19 ` Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 07/10] mci: add support for discarding write blocks Ahmad Fatoum
2024-07-30 9:23 ` Yann Sionneau
2024-07-30 11:14 ` Ahmad Fatoum
2024-07-30 10:05 ` Sascha Hauer
2024-07-30 11:17 ` Ahmad Fatoum
2024-07-30 7:19 ` [PATCH 08/10] commands: sync: add new command to flush cached writes Ahmad Fatoum
2024-07-30 10:08 ` Sascha Hauer
2024-07-30 7:19 ` [PATCH 09/10] mci: core: remove reference to SD Card from common mci_card_probe Ahmad Fatoum
2024-07-30 10:09 ` Sascha Hauer
2024-07-30 7:19 ` [PATCH 10/10] commands: blkstats: add command to print block device statistics Ahmad Fatoum
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=ZqjMx1xWl1toOM59@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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