Skip to content
Browse files

scripts/dts: Remove DT_CHOSEN generation

We never used DT_CHOSEN so lets remove this and add it back if/when
there's an actual need for it.

Signed-off-by: Kumar Gala <>
  • Loading branch information...
galak committed Jun 22, 2019
1 parent 08a5f9f commit 95f28eb764556895e39d76a8c0b299c4738da1dc
Showing with 0 additions and 12 deletions.
  1. +0 −8 doc/guides/dts/index.rst
  2. +0 −4 scripts/dts/
@@ -316,14 +316,6 @@ The full set of Zephyr-specific ``chosen`` nodes follows:
* - ``zephyr,uart-mcumgr``

As chosen properties tend to be related to software configuration, it can be
useful for the build system to know if a chosen property was defined. We
generate a define for each chosen property, for example:

``zephyr,flash`` will generate: ``#define DT_CHOSEN_ZEPHYR_FLASH 1``

As a consequence ``zephyr,flash`` related code could safely be implemented
under ``#ifdef DT_CHOSEN_ZEPHYR_FLASH`` instruction.

Adding support for device tree in drivers
@@ -454,10 +454,6 @@ def generate_defines():

# Add DT_CHOSEN_<X> defines
for c in sorted(chosen):
insert_defs('chosen', {'DT_CHOSEN_' + str_to_label(c): '1'}, {})

def parse_arguments():
rdh = argparse.RawDescriptionHelpFormatter

0 comments on commit 95f28eb

Please sign in to comment.
You can’t perform that action at this time.