michaelh/zephyr
1
0
Fork 0
Code Releases Activity

storage/flash_map: Use larger type for alignment

Browse source 
In MCUboot:
    commit 4aa286d2db2d02a8f0ff29cdc3304f3185dbe261
    Author: Gustavo Henrique Nihei <gustavo.nihei@espressif.com>
    Date:   Wed Nov 24 14:54:56 2021 -0300

        flash_map: Increase minimum supported write align via
            flash_area_align

MCUboot changed the type of the alignment value in flash from a uint8_t
to a uint32_t.  Indeed, Zephyr contains flash devices that have a larger
alignment than will fit in an 8-bit value.  This generally means that
`flash_area_align` will just return 0 on these platforms.

Change call in Zephyr as well.

This shouldn't cause any observable behavior changes in Zephyr, other
than making some cases that don't work currently begin to work.  If a
client is storing these results in a u8, it will be truncated, the same
as things were previously.  If, however, the caller is prepared to
handle a larger type, this will result in having correct information,
instead of the truncated value.

Signed-off-by: David Brown <david.brown@linaro.org>
This commit is contained in:
David Brown 2021-12-29 16:27:27 -07:00 • committed by Christopher Friedt
commit fac2c22824
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
include/storage/flash_map.h
View file

@ -191,7 +191,7 @@ int flash_area_erase(const struct flash_area *fa, off_t off, size_t len);
*
* @return Alignment restriction for flash writes in [B].
*/
uint8_t flash_area_align(const struct flash_area *fa);
uint32_t flash_area_align(const struct flash_area *fa);
/**
* Retrieve info about sectors within the area.