include/spi: Clarify spi_release() function behavior (dd66bdad) · Commits · Wenxi XU / zephyr

It will unlock and unhold the CS line. Note that the lock and the CS being hold on are 2 separate config bits, so if only one is selected spi_release() will only apply on this configuration. Note: this has been already the case in the controller drivers, where there implementation of spi_release() calls spi_context_unlock_unconditionally(). And that function always forces the CS line to an inactive state. Signed-off-by:

Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>

doc/guides/dts/howtos.rst

+4 −3

Original line number	Diff line number	Diff line
		@@ -205,8 +205,8 @@ list of overlay files to use. If :makevar:`DTC_OVERLAY_FILE` specifies multiple
		files, they are included in that order by the C preprocessor.

		You can set :makevar:`DTC_OVERLAY_FILE` to contain exactly the files you want
		to use. Here is an example :ref:`using west build
		<west-building-dtc-overlay-file>`.
		to use. Here is an :ref:`example <west-building-dtc-overlay-file>` using
		``using west build``.

		If you don't set :makevar:`DTC_OVERLAY_FILE`, the build system will follow
		these steps, looking for files in your application source directory to use
		@@ -225,7 +225,8 @@ as devicetree overlays:

		Using :ref:`shields` will also add devicetree overlay files.

		However you set the value, it is saved in the CMake cache between builds.
		The :makevar:`DTC_OVERLAY_FILE` value is stored in the CMake cache and used
		in successive builds.

		The :ref:`build system <build_overview>` prints all the devicetree overlays it
		finds in the configuration phase, like this:

Admin message