summaryrefslogtreecommitdiff
path: root/include/producer.h
diff options
context:
space:
mode:
authorShawn Nematbakhsh <shawnn@chromium.org>2015-09-01 14:52:12 -0700
committerchrome-bot <chrome-bot@chromium.org>2015-09-02 18:56:37 -0700
commitac9f0f37362901f2418d1059ad583405e20ce65c (patch)
treed0e3b739d88e35259bcc9d707dae81146c8e1814 /include/producer.h
parent2b5acbc8135ab49c5a10344f5d134153f52c4d17 (diff)
downloadchrome-ec-ac9f0f37362901f2418d1059ad583405e20ce65c.tar.gz
cleanup: Clarify use of flash layout CONFIGs
Based on feedback from programmers, it's not clear when config_std_internal_flash should be used, and when non-standard chip-specific layouts need to be defined. Add clarity here with the following changes: - Explain in-depth the one config that config_std_internal_flash should be used for. - Move non-standard chip-level flash layout CONFIGs to their own new chip-level file, config_flash_layout. All chips should either include config_std_internal_flash.h OR define their own layout in their own config_flash_layout. Functionally, this change is a NOP. BUG=chrome-os-partner:23796 TEST=`make buildall -j` BRANCH=None Change-Id: I6037b68db9048d90fa2a2da4c9c9e09d1143fa68 Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/296527 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Shawn N <shawnn@chromium.org>
Diffstat (limited to 'include/producer.h')
0 files changed, 0 insertions, 0 deletions