Searched +full:host +full:- +full:interface (Results 1 – 25 of 726) sorted by relevance
12345678910>>...30
| /Zephyr-latest/drivers/hdlc_rcp_if/ |
| D | Kconfig | 1 # Configuration options for HDLC RCP communication Interface
4 # SPDX-License-Identifier: Apache-2.0
7 # HDLC communication Interface used by Zephyr running Openthread RCP host
11 bool "HDLC interface for a Zephyr Openthread RCP host"
20 string "HDLC RCP Interface Driver's name"
26 module-str = HDLC driver for Openthread RCP host
27 module-help = Sets log level for Openthread HDLC RCP host interface Device Drivers.
|
| D | Kconfig.uart | 1 # Configuration options for NXP HDLC RCP UART communication Interface
5 # SPDX-License-Identifier: Apache-2.0
8 # HDLC UART communication Interface used by Zephyr running Openthread RCP host
12 bool "UART HDLC interface for Zephyr Openthread RCP host"
20 RX buffer size for the OpenThread HDLC host UART.
26 TX buffer size for the OpenThread HDLC host UART.
|
| D | Kconfig.nxp | 1 # Configuration options for NXP HDLC RCP communication Interface
4 # SPDX-License-Identifier: Apache-2.0
7 # HDLC communication Interface used by Zephyr running Openthread RCP host
11 bool "NXP HDLC interface for Zephyr Openthread RCP host"
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig.xec | 4 # SPDX-License-Identifier: Apache-2.0
49 send over eSPI from host.
66 to override if eSPI host doesn't support it.
89 int "Host I/O peripheral port size for shared memory in MEC172X series"
93 This is the port size used by the Host and EC to communicate over
97 int "Host I/O peripheral port size for ec host command in MEC172X series"
101 This is the port size used by the Host and EC to communicate over
102 the shared memory region to return the host command parameter data.
112 Enable a 32 byte mailbox interface accessible via Host I/O over the
118 Enable ACPI EC2 interface accessible via Host I/O over the
[all …]
|
| D | Kconfig.npcx | 4 # SPDX-License-Identifier: Apache-2.0
13 This option enables the Intel Enhanced Serial Peripheral Interface
17 int "Host I/O peripheral port size for shared memory in npcx series"
21 This is the port size used by the Host and EC to communicate over
27 int "Host I/O peripheral port size for ec host command in npcx series"
31 This is the port size used by the Host and EC to communicate over
32 the shared memory region to return the host command parameter data.
48 bool "Host can write 1/2/4 bytes of Port80 data in a eSPI transaction"
52 EC can accept 1/2/4 bytes of Port 80 data written from the Host in an
61 Postcodes from Host.
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | usbnet_setup.rst | 10 This page describes how to set up networking between a Linux host
13 The board is connected to Linux host using USB cable
14 and provides an Ethernet interface to the host.
15 The :zephyr:code-sample:`sockets-echo-server` application from the Zephyr source
17 Linux host using a USB cable providing an Ethernet interface to the host.
23 interface, we need to assign IP addresses and set up a routing table for
24 the Linux host.
25 After plugging a USB cable from the board to the Linux host, the
30 running dmesg from the Linux host.
32 .. code-block:: console
[all …]
|
| D | eth_bridge_native_sim_setup.rst | 10 This document describes how to set up a bridged Ethernet network between a (Linux) host
14 :kconfig:option:`CONFIG_NET_ETHERNET_BRIDGE` Kconfig option. In this setup, the net-tools
15 configuration creates two host network interfaces ``zeth0`` and ``zeth1`` and connects them
18 First create the host interfaces. In this example two interfaces are created.
20 .. code-block:: console
22 cd $ZEPHYR_BASE/../tools/net-tools
23 ./net-setup.sh -c zeth-multiface.conf -i zeth0 -t 2
25 The ``-c`` tells which configuration file to use, where ``zeth-multiface.conf`` is tailored
26 for generating multiple network interfaces in the host.
27 The ``-i`` option tells what is the first host interface name. The ``-t`` tells how
[all …]
|
| D | networking_with_multiple_instances.rst | 12 or could be native_sim board processes. The Linux host can be used
18 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
19 found in a Zephyr standard installation under the ``tools/net-tools`` directory
22 .. code-block:: console
24 git clone https://github.com/zephyrproject-rtos/net-tools
31 * Terminal #1 and #2 are terminal windows with net-tools being the current
32 directory (``cd net-tools``)
33 * Terminal #3, where you setup bridging in Linux host
44 Step 1 - Create configuration files
48 Zephyr instance should be created in the host system. The default setup for
[all …]
|
| D | native_sim_setup.rst | 13 This paragraph describes how to set up a virtual network between a (Linux) host
16 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
18 native_sim board instance is connected to a Linux host using a tuntap device
19 which is modeled in Linux as an Ethernet network interface.
24 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
25 found in a Zephyr standard installation under the ``tools/net-tools`` directory
28 .. code-block:: console
30 git clone https://github.com/zephyrproject-rtos/net-tools
38 * Terminal #1 is terminal window with net-tools being the current
39 directory (``cd net-tools``)
[all …]
|
| D | network_monitoring.rst | 13 that user is able to use Wireshark or similar tool in remote host to see the
16 See also the :zephyr:code-sample:`net-capture` sample application from the Zephyr
19 Host Configuration
22 The instructions here describe how to setup a Linux host to capture Zephyr
26 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
27 found in a Zephyr standard installation under the ``tools/net-tools`` directory
30 .. code-block:: console
32 git clone https://github.com/zephyrproject-rtos/net-tools
34 The ``net-tools`` project provides a configure file to setup IP-to-IP tunnel
35 interface so that we can transfer monitoring data from Zephyr to host.
[all …]
|
| D | qemu_eth_setup.rst | 10 This page describes how to set up a virtual network between a (Linux) host
13 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
15 connected to a Linux host using a tuntap device which is modeled in Linux as
16 an Ethernet network interface.
21 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
22 found in a Zephyr standard installation under the ``tools/net-tools`` directory
25 .. code-block:: console
27 git clone https://github.com/zephyrproject-rtos/net-tools
35 * Terminal #1 is terminal window with net-tools being the current
36 directory (``cd net-tools``)
[all …]
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 3 Controller Area Network (CAN) Host Tests
9 This test suite uses `python-can`_ for testing Controller Area Network (CAN) communication between a
10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
17 * The python-can library installed on the host PC.
18 * A CAN fixture creating a CAN bus between the host PC and the DUT.
25 the ``bitrate`` and ``bitrate-data`` CAN controller devicetree properties if needed. Default
29 The host end of the CAN fixture can be configured through python-can. Available configuration
30 options depend on the type of host CAN adapter used. The python-can library provides a lot of
31 flexibility for configuration as decribed in the `python-can configuration`_ page, all centered
35 * By default, the python-can configuration context is not specified, causing python-can to use the
[all …]
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.native_posix | 4 # SPDX-License-Identifier: Apache-2.0
11 a process in your host system.
22 By default only one network interface is created. It is possible
31 This option sets the driver name and name of the network interface
32 in your host system. If there are multiple network interfaces defined,
33 then this value is used as a prefix and the interface names will be
37 string "Host ethernet TUN/TAP device name"
40 This option sets the TUN/TAP device name in your host system.
66 string "MAC address for the interface"
70 Specify a MAC address for the ethernet interface in the form of
[all …]
|
| /Zephyr-latest/samples/boards/nxp/s32/netc/ |
| D | README.rst | 1 .. zephyr:code-sample:: nxp_s32_netc
10 for the different use-cases:
12 1. Zephyr application controls the Physical Station Interface (PSI) and the
18 The sample enables the net-shell and mdio-shell (only available when Zephyr
28 To run this sample is needed to set-up a host machine running GNU/Linux or Windows
35 To build and run the sample application for use-case 1:
37 .. zephyr-app-commands::
38 :zephyr-app: samples/boards/nxp/s32/netc
42 Once started, you should see the network interface details, for example:
44 .. code-block:: console
[all …]
|
| /Zephyr-latest/dts/bindings/shi/ |
| D | ite,it8xxx2-shi.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 description: ITE, IT8XXX2 Serial Host Interface (SHI) node
6 compatible: "ite,it8xxx2-shi"
8 include: [pinctrl-device.yaml, shi-device.yaml]
11 pinctrl-0:
14 pinctrl-names:
17 cs-gpios:
18 type: phandle-array
21 Pin used as chip-select for the SHI interface. Change in level will
22 trigger the interrupt for the handler of host commands.
|
| /Zephyr-latest/dts/bindings/can/ |
| D | zephyr,native-linux-can.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "zephyr,native-linux-can"
8 include: can-fd-controller.yaml
11 host-interface:
15 Linux host interface name (e.g. zcan0, vcan0, can0, ...).
16 This property can be overridden using the --can-if command-line
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 1 .. _bluetooth-arch:
13 Zephyr supports mainly Bluetooth Low Energy (BLE), the low-power
15 for portions of the BR/EDR Host. Throughout this architecture document we
18 .. _bluetooth-layers:
26 * **Host**: This layer sits right below the application, and is comprised of
27 multiple (non real-time) network and transport protocols enabling
31 low-level, real-time protocol which provides, in conjunction with the Radio
32 Hardware, standard-interoperable over-the-air communication. The LL schedules
39 .. _bluetooth-hci:
41 Host Controller Interface
[all …]
|
| /Zephyr-latest/soc/nuvoton/npcx/common/ |
| D | soc_espi.h | 4 * SPDX-License-Identifier: Apache-2.0
17 * @brief Turn on all interrupts of eSPI host interface module.
24 * @brief Turn off all interrupts of eSPI host interface module.
|
| D | soc_host.h | 4 * SPDX-License-Identifier: Apache-2.0
21 * @brief Initializes all host sub-modules in Core domain.
23 * This routine initializes all host sub-modules which HW blocks belong to
27 * @param dev Pointer to the device structure for the host bus driver instance.
31 * @retval -EIO if cannot turn on host sub-module source clocks in core domain.
37 * @brief Initializes all host sub-modules in Host domain.
39 * This routine initializes all host sub-modules which HW blocks belong to
40 * Host domain. Please notice it must be executed after receiving PLT_RST
41 * de-asserted signal and eSPI peripheral channel is enabled and ready.
46 * @brief Reads data from a host sub-module which is updated via eSPI.
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/pcie/ |
| D | ptm.h | 4 * SPDX-License-Identifier: Apache-2.0
12 * @brief PCIe Host PTM Interface
13 * @defgroup pcie_host_ptm_interface PCIe Host PTM Interface
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ec_host_cmd.rst | 3 EC Host Command
8 The host command protocol defines the interface for a host, or application processor, to
9 communicate with a target embedded controller (EC). The EC Host command subsystem implements the
10 target side of the protocol, generating responses to commands sent by the host. The host command
11 protocol interface supports multiple versions, but this subsystem implementation only support
16 The Host Command subsystem contains a few components:
32 SHI (Serial Host Interface) is different to this because it is used only for communication with a
33 host. SHI does not have API itself, thus the backend and peripheral driver layers are combined into
39 Another case is SPI. Unfortunately, the current SPI API can't be used to handle the host commands
40 communication. The main issues are unknown command size sent by the host (the SPI transaction
[all …]
|
| /Zephyr-latest/boards/shields/nrf7002ek/doc/ |
| D | index.rst | 10 Nordic and non-Nordic host boards.
12 The nRF7002 EK unlocks low-power Wi-Fi 6 capabilities for your host device. It support dual-band Wi…
14 Seamlessly connect to Wi-Fi networks and leverage Wi-Fi-based locationing, enabling advanced
15 features such as SSID sniffing of local Wi-Fi hubs
27 communication interface. Any host board that supports the Arduino connector can be used with
31 -------------
33 the nRF70 driver requires firmware binary blobs for Wi-Fi operation. Run the command
36 .. code-block:: console
44 The shield can be used in any application by setting ``--shield nrf7002ek`` when invoking ``west bu…
46 SR Co-existence
[all …]
|
| /Zephyr-latest/tests/bluetooth/host/ |
| D | CMakeLists.txt | 2 # CMakeLists.txt file for creating of host mocks library.
11 ${ZEPHYR_BASE}/subsys/bluetooth/host
12 ${ZEPHYR_BASE}/tests/bluetooth/host
16 target_compile_options(test_interface INTERFACE -include ztest.h)
|
| /Zephyr-latest/dts/bindings/bluetooth/ |
| D | zephyr,bt-hci-spi-slave.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 Zephyr's Bluetooth Host Controller Interface SPI (HCI SPI) driver.
11 bt-hci@0 {
12 compatible = "zephyr,bt-hci-spi-slave";
14 irq-gpios = <&gpio1 2 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
18 The bt-hci@0 node configures an HCI SPI slave on SPI slave
19 interface myspi.
21 The host interrupt GPIO is set to gpio1 pin 2 via irq-gpios. The
25 compatible: "zephyr,bt-hci-spi-slave"
29 on-bus: spi
[all …]
|
| /Zephyr-latest/drivers/dai/intel/ssp/ |
| D | dai-params-intel-ipc4.h | 4 * SPDX-License-Identifier: Apache-2.0
19 /**< HD/A host output (-> DSP). */
21 /**< HD/A host input (<- DSP). */
23 /**< HD/A host input/output (rsvd for future use). */
26 /**< HD/A link output (DSP ->). */
28 /**< HD/A link input (DSP <-). */
33 /**< DMIC link input (DSP <-). */
36 /**< I2S link output (DSP ->). */
38 /**< I2S link input (DSP <-). */
41 /**< ALH link output, legacy for SNDW (DSP ->). */
[all …]
|
12345678910>>...30
