diff options
| author | Jack Rosenthal <jrosenth@chromium.org> | 2021-04-30 13:03:26 -0600 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2021-05-01 01:41:08 +0000 |
| commit | bf9979b91599ffc76018d60e780d19fa8d266ac0 (patch) | |
| tree | 56ca6031236d2af6b38944c373806a708e6adb7b /zephyr/include/cros/nuvoton | |
| parent | 3b156ad3993b99eb9ec056a1d4e60d04525faa77 (diff) | |
| download | chrome-ec-bf9979b91599ffc76018d60e780d19fa8d266ac0.tar.gz | |
zephyr: drop programmatic generation of binman device-tree input
Move the binman device-tree input into the Zephyr build system's DTS,
which allows overriding parts of the binman settings on a
board/project specific basis using device-tree.
In the process, we need to move the flash offset and size to
device-tree instead of Kconfig, because Kconfig is not including
during device-tree preprocessing. This is overall, a net-good change,
as this should never been Kconfig in the first place. This assumes
the existing Kconfig defaults of 512 KB of flash with 256 KB sections,
however can still be overridden via device-tree.
BUG=b:184388037
BRANCH=none
TEST=zmake testall
manually investigate the flash output for lazor using dump_fmap
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I424ea15454d5cd02947642116673bebcad3406cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2860987
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'zephyr/include/cros/nuvoton')
| -rw-r--r-- | zephyr/include/cros/nuvoton/npcx.dtsi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/zephyr/include/cros/nuvoton/npcx.dtsi b/zephyr/include/cros/nuvoton/npcx.dtsi index 8251a34ade..e31b4c1b7c 100644 --- a/zephyr/include/cros/nuvoton/npcx.dtsi +++ b/zephyr/include/cros/nuvoton/npcx.dtsi @@ -6,6 +6,7 @@ /dts-v1/; +#include <cros/binman.dtsi> #include <nuvoton/npcx7m6fb.dtsi> / { |