79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
||
---|---|---|
.. | ||
boards | ||
src | ||
CMakeLists.txt | ||
README.rst | ||
prj.conf | ||
sample.yaml |
README.rst
.. _adc_cmp_npcx: NPCX ADC Comparator ################### Overview ******** This sample show how to use the NPCX ADC Comparator driver. The sample supports the :ref:`npcx9m6f_evb`. This application is a voltage comparator with hysteresis, upper limit is set at 1 V while lower limit is 250 mV. Initially configured to detect upper limit. Building and Running ******************** Build the application for the :ref:`npcx9m6f_evb` board, and provide voltage to ADC channel 8, when voltages cross upper/lower limits, detection messages will be printed. .. zephyr-app-commands:: :zephyr-app: samples/sensor/adc_cmp :board: npcx9m6f_evb :goals: flash :compact: