Test expected path "zephyr/boards/Kconfig" but failed when the
repository had a different name.
Changed to "boards/Kconfig" to work with any repository name,
as code below.
Signed-off-by: Mateusz Junkier <mateusz.junkier@intel.com>
Add a test case that verifies Kconfig value origin traces are correctly
generated in both JSON and pickle formats. The test includes a sample
Kconfig configuration with dependencies, selections, and choices to
cover various scenarios. A validation script checks the generated source
origin data against expected values.
In addition, the 'traceconfig' target is called to test the generation
of the Markdown file with the Kconfig trace report.
Signed-off-by: Luca Burelli <l.burelli@arduino.cc>
Functions like `add` and `sub` can only return base 10 integers, which
means they can't really be used to define Kconfig symbols of type `hex`.
For the same reason, there already exist pairs of devicetree functions
named e.g., `dt_node_reg_addr_(int|hex)` after different return types.
Introduce `add_hex`, `sub_hex`, and friends.
To avoid confusion, it should be possible for those new functions to
accept arguments in base 16 as well. It's actually easier to let all
arithmetic functions take their inputs in "any" base, by leveraging
Python's built-in: `int(..., base=0)`.
Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no>
Commit 345735d0a8 removed all uses of the
now obsolete CONFIG_ZTEST_NEW_API Kconfig option. A couple of stray ones
are still remaining in the tree, remove them.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
