Lines Matching full:backend

18 * Backend
22 The backend is a layer between a peripheral driver and the general handler. It is responsible for
25 The general handler validates data from the backend e.g. check sizes, checksum, etc. If the command
33 host. SHI does not have API itself, thus the backend and peripheral driver layers are combined into
34 one backend layer.
42 is enabled and disabled per transaction). It forces implementing the SPI driver within a backend,
43 as it is done for SHI. That means a SPI backend has to be implemented per chip family. However, it
67 The STM32 SPI host command backend driver supports the :dtcompatible:`st,stm32h7-spi` and
80 For the SPI, it is required to set the backend chosen node ``zephyr,host-cmd-spi-backend``.
82 The supported backend and peripheral drivers:
94 If the application configures one of the following backend chosen nodes and
95 :kconfig:option:`CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT` is set, then the corresponding backend
98 * ``zephyr,host-cmd-espi-backend``
99 * ``zephyr,host-cmd-shi-backend``
100 * ``zephyr,host-cmd-uart-backend``
101 * ``zephyr,host-cmd-spi-backend``
103 If no backend chosen node is configured, the application must call the :c:func:`ec_host_cmd_init`
104 function directly. This way of initialization is useful if a backend is chosen in runtime
114 backend would increase the memory usage. However, some buffers can be defined by a peripheral driver