Searched refs:device (Results 3876 – 3900 of 4950) sorted by relevance
1...<<151152153154155156157158159160>>...198
| /Zephyr-latest/samples/drivers/adc/adc_sequence/src/ |
| D | main.c | 17 static const struct device *adc = DEVICE_DT_GET(ADC_NODE);
|
| /Zephyr-latest/dts/common/nordic/ |
| D | nrf_common.dtsi | 26 /* Pin controller is a "virtual" device since nRF SoCs do pin
|
| /Zephyr-latest/drivers/bbram/ |
| D | Kconfig | 26 # MCP7940N is an I2C device, therefore the init priority must be
|
| /Zephyr-latest/tests/boards/mec172xevb_assy6906/i2c_api/ |
| D | README.txt | 11 As the I2C slave device NXP pca95xx on mec172xevb_assy6906 is connected
|
| /Zephyr-latest/tests/drivers/pinctrl/gd32/boards/ |
| D | gd32f450i_eval.overlay | 8 compatible = "vnd,pinctrl-device";
|
| /Zephyr-latest/subsys/storage/flash_map/ |
| D | flash_map_layout.c | 97 const struct device *flash_dev; in flash_area_sectors()
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/ |
| D | index.rst | 57 You will need the Intel® Quartus® Prime SDK in order to work with this device. The
72 II peripheral, which is the built-in JTAG interface for this device.
211 You can either debug a running image that was flashed onto the device in User
245 …Info : JTAG tap: fpgasoc.fpga.tap tap/device found: 0x02d020dd (mfg: 0x06e (Altera), part: 0x2d02,…
246 …Info : JTAG tap: fpgasoc.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver…
284 …Info : JTAG tap: fpgasoc.fpga.tap tap/device found: 0x02d020dd (mfg: 0x06e (Altera), part: 0x2d02,…
285 …Info : JTAG tap: fpgasoc.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver…
310 …Info : JTAG tap: fpgasoc.fpga.tap tap/device found: 0x02d020dd (mfg: 0x06e (Altera), part: 0x2d02,…
311 …Info : JTAG tap: fpgasoc.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver…
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 75 example, the pairing of an NFC token or a Bluetooth device might use
84 activities. Attestation is the ability for a device to sign an array
85 of bytes with a device private key and return the result to the
87 device state, to the ability to generate a key pair and prove that it
94 field. This API provides the APIs necessary for populating a device
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/src/ |
| D | main.c | 68 static const struct device *const wdt = DEVICE_DT_GET(WDT_NODE);
83 static void wdt_test_06b_cb(const struct device *wdt_dev, int channel_id) in wdt_test_06b_cb()
90 static void wdt_test_08b_cb(const struct device *wdt_dev, int channel_id) in wdt_test_08b_cb()
97 static void wdt_test_08d_A_cb(const struct device *wdt_dev, int channel_id) in wdt_test_08d_A_cb()
104 static void wdt_test_08d_B_cb(const struct device *wdt_dev, int channel_id) in wdt_test_08d_B_cb()
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 223 device connects.
375 but want to rely on the remote device to initiate the procedure at its
395 supported but want to rely on the remote device to initiate the
443 Enable privacy for the local device. This makes the device use Resolvable
480 those IRs are reused, this device can be tracked across factory resets.
484 to be recognizable by only that one bonded device.
565 mode device shall only use Security Mode 1 Level 4 with exception
585 bool "Allow unauthenticated pairing for paired device"
589 This would enable cases where an attacker could copy the peer device
734 and overwritten by the pairing device.
[all …]
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 31 - The target device is not connected and not available for flashing
210 A list of custom binaries to be kept for device testing.
504 on device testing must use the hardware map, or west flash to load
648 Specify a test scenario dependency on an external device(e.g., sensor),
996 Executing tests on a single device
999 To use this feature on a single connected device, run twister with
1008 scripts/twister --device-testing --device-serial /dev/ttyACM0 \
1009 --device-serial-baud 115200 -p frdm_k64f -T tests/kernel
1015 python .\scripts\twister --device-testing --device-serial COM1 \
1016 --device-serial-baud 115200 -p frdm_k64f -T tests/kernel
[all …]
|
| /Zephyr-latest/drivers/spi/ |
| D | spi_rtio.c | 24 const struct device *dev = dt_spec->bus; in spi_rtio_iodev_default_submit_sync()
100 void spi_rtio_iodev_default_submit(const struct device *dev, in spi_rtio_iodev_default_submit()
303 const struct device *dev) in spi_rtio_init()
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 40 * Requesting multiple reads to the same device for Ping-Pong (double buffering)
70 polling I/O device (akin to a file descriptor) for the sensor with the desired
96 Handling triggers with `Read and Decode`_ works by setting up a stream I/O device
|
| /Zephyr-latest/boards/silabs/starter_kits/slstk3400a/doc/ |
| D | index.rst | 20 - USB device interface
113 - A Serial Flash device, which implements the USB flash disk file storage.
128 you should see a USB connection that exposes a mass storage device (STK3400)
|
| /Zephyr-latest/boards/silabs/starter_kits/slstk3401a/doc/ |
| D | index.rst | 122 - A USB connection to the host computer, which exposes a mass storage device and a
124 - A serial flash device, which implements the USB flash disk file storage.
139 should see a USB connection which exposes a mass storage device(SLSTK3401A).
|
| /Zephyr-latest/samples/drivers/clock_control_litex/ |
| D | README.rst | 55 struct device *dev;
117 device name: clock0
118 clock control device is 0x40013460, name is clock0
|
| /Zephyr-latest/boards/pine64/pinetime_devkit0/doc/ |
| D | index.rst | 121 - Unlock the device
144 Unlocking the device is a one-time action that is needed to enable to debug
145 port and provide full access to the device. This will erase all existing
|
| /Zephyr-latest/samples/bluetooth/iso_connected_benchmark/ |
| D | README.rst | 65 Choose device role - type c (central role) or p (peripheral role), or q to quit: p
89 scanning for and connecting to a peer device running the sample as peripheral
97 Choose device role - type c (central role) or p (peripheral role), or q to quit: c
|
| /Zephyr-latest/boards/others/stm32_min_dev/doc/ |
| D | index.rst | 29 for connecting an LED, so only this device is supported by our Zephyr port.
30 Additional device support is left for the user to implement.
104 | USB | on-chip | USB device |
|
| /Zephyr-latest/scripts/support/ |
| D | quartus-flash.py | 133 flash_kernel(args.device, args.sof, args.kernel)
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.rtt | 14 This option enables access RTT channel as UART device.
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/inc/ |
| D | fmac_main.h | 40 const struct device *zep_dev_ctx;
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | intc_irqmp.c | 111 static int irqmp_init(const struct device *dev) in irqmp_init()
|
| /Zephyr-latest/drivers/firmware/scmi/ |
| D | mailbox.h | 110 const struct device *shmem;
|
| /Zephyr-latest/drivers/fuel_gauge/max17048/ |
| D | emul_max17048.c | 138 static int emul_max17048_init(const struct emul *target, const struct device *parent) in emul_max17048_init()
|
1...<<151152153154155156157158159160>>...198
