Searched +full:host +full:- +full:interface (Results 1 – 25 of 506) sorted by relevance
12345678910>>...21
| /Zephyr-Core-3.5.0/drivers/ethernet/ |
| D | Kconfig.native_posix | 4 # SPDX-License-Identifier: Apache-2.0
11 a process in your host system.
15 bool "Start network interface automatically"
18 interface, requiring ``zephyr.exe`` to be run with root privileges
20 If not set (the default and recommended way), the network interface
21 must be set up manually using ``net-setup.sh`` (from the net-tools
23 non-root user.
28 string "Host setup script"
31 This option sets the name of the script that is run when the host TAP
32 network interface is created. The script should setup IP addresses
[all …]
|
| /Zephyr-Core-3.5.0/drivers/espi/ |
| D | Kconfig.xec | 4 # SPDX-License-Identifier: Apache-2.0
47 send over eSPI from host.
64 to override if eSPI host doesn't support it.
87 int "Host I/O peripheral port size for shared memory in MEC172X series"
91 This is the port size used by the Host and EC to communicate over
95 int "Host I/O peripheral port size for ec host command in MEC172X series"
99 This is the port size used by the Host and EC to communicate over
100 the shared memory region to return the host command parameter data.
110 Enable a 32 byte mailbox interface accessible via Host I/O over the
116 Enable ACPI EC2 interface accessible via Host I/O over the
[all …]
|
| /Zephyr-Core-3.5.0/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 | networking_with_multiple_instances.rst | 12 or could be native_posix board processes. The Linux host can be used
18 On the Linux Host, fetch the Zephyr ``net-tools`` project, which is located
21 .. code-block:: console
23 git clone https://github.com/zephyrproject-rtos/net-tools
30 * Terminal #1 and #2 are terminal windows with net-tools being the current
31 directory (``cd net-tools``)
32 * Terminal #3, where you setup bridging in Linux host
43 Step 1 - Create configuration files
47 Zephyr instance should be created in the host system. The default setup for
48 creating network interface cannot be used here as that is for connecting one
[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
25 On the Linux Host, fetch the Zephyr ``net-tools`` project, which is located
28 .. code-block:: console
30 git clone https://github.com/zephyrproject-rtos/net-tools
32 The ``net-tools`` project provides a configure file to setup IP-to-IP tunnel
33 interface so that we can transfer monitoring data from Zephyr to host.
37 .. code-block:: console
[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, fetch the Zephyr ``net-tools`` project, which is located
24 .. code-block:: console
26 git clone https://github.com/zephyrproject-rtos/net-tools
34 * Terminal #1 is terminal window with net-tools being the current
35 directory (``cd net-tools``)
51 Step 1 - Create Ethernet interface
[all …]
|
| D | native_posix_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 native_posix board instance is connected to a Linux host using a tuntap device
16 which is modeled in Linux as an Ethernet network interface.
21 On the Linux Host, fetch the Zephyr ``net-tools`` project, which is located
24 .. code-block:: console
26 git clone https://github.com/zephyrproject-rtos/net-tools
34 * Terminal #1 is terminal window with net-tools being the current
35 directory (``cd net-tools``)
41 Step 1 - Create Ethernet interface
[all …]
|
| /Zephyr-Core-3.5.0/samples/boards/nxp_s32/netc/ |
| D | README.rst | 1 .. _nxp_s32_netc-samples:
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-Core-3.5.0/dts/bindings/can/ |
| D | zephyr,native-posix-linux-can.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "zephyr,native-posix-linux-can"
8 include: can-controller.yaml
11 host-interface:
14 description: Linux host interface name (e.g. zcan0, vcan0, can0, ...)
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/samples/net/eth_native_posix/ |
| D | README.rst | 1 .. zephyr:code-sample:: eth-native-posix
3 :relevant-api: net_core ethernet
5 Create a network interface to the host system.
11 interface to the host system. One can communicate with Zephyr via this network
12 interface.
23 .. zephyr-app-commands::
24 :zephyr-app: samples/net/eth_native_posix
25 :host-os: unix
32 the host system. If the user has set the
37 .. code-block:: console
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/soc/arm/nuvoton_npcx/common/ |
| 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 …]
|
| 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.
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/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-Core-3.5.0/arch/posix/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
12 # For ex. target_compile_options(native_simulator INTERFACE "-m64")
16 # For ex. target_link_options(native_simulator INTERFACE "-lstdc++")
19 # For ex. target_sources(native_simulator INTERFACE silly.c)
20 # Note that these are built with the host libC and the include directories
31 add_library(native_simulator INTERFACE)
37 # @Intent: Set necessary compiler & linker options for this specific host architecture & OS
41 # some gcc versions fail to build without -fPIC
42 zephyr_compile_options(-m64 -fPIC)
43 zephyr_link_libraries(-m64)
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/drivers/dai/intel/ssp/ |
| D | dai-params-intel-ipc4.h | 4 * SPDX-License-Identifier: Apache-2.0
16 /**< HD/A host output (-> DSP). */
18 /**< HD/A host input (<- DSP). */
20 /**< HD/A host input/output (rsvd for future use). */
23 /**< HD/A link output (DSP ->). */
25 /**< HD/A link input (DSP <-). */
30 /**< DMIC link input (DSP <-). */
33 /**< I2S link output (DSP ->). */
35 /**< I2S link input (DSP <-). */
38 /**< ALH link output, legacy for SNDW (DSP ->). */
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/include/zephyr/mgmt/ec_host_cmd/ |
| D | backend.h | 4 * SPDX-License-Identifier: Apache-2.0
9 * @brief Public APIs for Host Command backends that respond to host commands
33 * @brief EC Host Command Interface
34 * @defgroup ec_host_cmd_interface EC Host Command Interface
40 * @brief Context for host command backend and handler to pass rx data.
54 * @brief Context for host command backend and handler to pass tx data
58 * Data to write to the host The buffer is provided by the handler if
71 * @brief Initialize a host command backend
73 * This routine initializes a host command backend. It includes initialization
79 * data from the driver when the host sends data. The buf member can be
[all …]
|
| D | simulator.h | 4 * SPDX-License-Identifier: Apache-2.0
13 * device interface.
20 * @brief Install callback for when this device would sends data to host
22 * When this host command simulator device should send data to the host, it
27 * @param cb Callback that is called when device would send data to host.
35 * @brief Simulate receiving data from host as passed in to this function
37 * Calling this function simulates that data was sent from the host to the DUT.
43 * @retval -ENOMEM if len is greater than the RX buffer size.
44 * @retval -EBUSY if the host command framework is busy with another request.
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
3 add_library(subsys__bluetooth INTERFACE)
5 target_include_directories(subsys__bluetooth INTERFACE ${CMAKE_CURRENT_SOURCE_DIR})
8 add_subdirectory_ifdef(CONFIG_BT_HCI host)
|
| /Zephyr-Core-3.5.0/subsys/mgmt/ec_host_cmd/backends/ |
| D | Kconfig | 1 # Host Command backend configs
4 # SPDX-License-Identifier: Apache-2.0
6 DT_CHOSEN_ESPI_BACKEND := zephyr,host-cmd-espi-backend
7 DT_CHOSEN_SHI_BACKEND := zephyr,host-cmd-shi-backend
8 DT_CHOSEN_UART_BACKEND := zephyr,host-cmd-uart-backend
9 DT_CHOSEN_SPI_BACKEND := zephyr,host-cmd-spi-backend
12 bool "Embedded Controller Host Command Backend Simulator"
15 Enable the EC host command simulator.
18 bool "Host commands support using eSPI bus"
23 Enable support for Embedded Controller host commands using
[all …]
|
| /Zephyr-Core-3.5.0/samples/net/virtual/ |
| D | README.rst | 1 .. zephyr:code-sample:: virtual-network-interface
2 :name: Virtual network interface
3 :relevant-api: virtual virtual_mgmt
5 Create a sample virtual network interface.
10 This sample application creates a sample virtual network interface for
14 Ethernet network interface is providing the real network interface and
17 On top of Ethernet interface there are two virtual network interfaces,
21 The sample provides tunnel interface which runs on top of the IPv6 tunnel.
29 - :ref:`networking_with_host`
34 The `net-tools`_ project provides a configuration that can be used
[all …]
|
12345678910>>...21
