diff options
| author | Yuval Peress <peress@chromium.org> | 2021-01-14 01:29:08 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2021-01-15 04:07:55 +0000 |
| commit | 9e422c3c05fdd324565049b09be27c446f9dc0ca (patch) | |
| tree | b4694ca5abc8c1be1000a1efe7a7bd8a02ddd856 /board/zinger | |
| parent | 6aa3d78608b681e6374f30747a7f6ab80938bde6 (diff) | |
| download | chrome-ec-9e422c3c05fdd324565049b09be27c446f9dc0ca.tar.gz | |
Refactor CONFIG_FLASH_SIZE to CONFIG_FLASH_SIZE_BYTES
In Zephyr CONFIG_FLASH_SIZE is a Kconfig value that is used
throughout. The issue is that the units don't match. In
Zephyr the value is in KiB instead of bytes. This refactor
simply renames CONFIG_FLASH_SIZE in platform/ec to include
the unit (via _BYTES).
BRANCH=none
BUG=b:174873770
TEST=make buildall
be generated by the build instead of per board
Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I44bf3c7a20fcf62aaa9ae15715be78db4210f384
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2627638
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Diffstat (limited to 'board/zinger')
| -rw-r--r-- | board/zinger/hardware.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/board/zinger/hardware.c b/board/zinger/hardware.c index ceeac38d38..7e1f29da38 100644 --- a/board/zinger/hardware.c +++ b/board/zinger/hardware.c @@ -308,7 +308,8 @@ int flash_physical_write(int offset, int size, const char *data) int res = EC_SUCCESS; int i; - if ((uint32_t)address > CONFIG_PROGRAM_MEMORY_BASE + CONFIG_FLASH_SIZE) + if ((uint32_t)address > + CONFIG_PROGRAM_MEMORY_BASE + CONFIG_FLASH_SIZE_BYTES) return EC_ERROR_INVAL; /* unlock CR if needed */ |