Github/littlefs
1
Fork 0
Code Actions Activity

Adopted erase_size config changes in block devices and test runners

Browse Source 
This ended up needing a bit of API rework since littlefs no longer needs
to know the actual erase_count. We can no longer rely on lfs_config to
contain all the information necessary to configure the block devices.

Changing the lfs_bd_config structs to be required is probably a good
idea anyways as it moves us more towards separating the bds from
littlefs, though we can't quite get rid of the lfs_config parameter
because of the block-device API in lfs_config. Eventually it would be
nice to get rid of it, but that would require API breakage.
This commit is contained in:
Christopher Haster
2022-11-11 15:05:34 -06:00
parent c16120bf5f
commit 21e54ee458
15 changed files with 303 additions and 203 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lfs.h
+2 -3
View File
@@ -197,9 +197,8 @@ struct lfs_config {
// will be a multiple of this value.
lfs_size_t prog_size;
// Minimum size of an erase operation in bytes. All erase operations
// will be a multiple of this value. This must be a multiple of the read
// and program sizes.
// Size of an erase operation in bytes. This must be a multiple of the
// read and program sizes.
//
// If zero, the block_size is used as the erase_size. This is mostly for
// backwards compatibility.