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> |
||
---|---|---|
.. | ||
src | ||
CMakeLists.txt | ||
Kconfig | ||
README.rst | ||
prj.conf | ||
sample.yaml |
README.rst
.. _tmp108_sample: TMP108 sample ############# Description *********** This sample writes the temperature to the console once every 3 seconds. There are macro definitions included for turning off and on alerts if that is set up, and also using low power one shot mode. Requirements ************ A board with the :dtcompatible:`ti,tmp108` built in to its :ref:`devicetree <dt-guide>`, or a devicetree overlay with such a node added. Sample Output ============= .. code-block:: console ** Booting Zephyr OS build zephyr-v2.6.0-1923-g72bb75a360ce *** TI TMP108 Example, arm Temperature is 22.875C Temperature is 22.875C Temperature is 22.875C Temperature is 22.875C Temperature is 22.875C Temperature is 22.875C