Home
last modified time | relevance | path

Searched refs:vendor (Results 1 – 25 of 180) sorted by relevance

12345678

/Zephyr-latest/dts/x86/intel/
Delkhart_lake.dtsi62 vendor-id = <0x8086>;
71 vendor-id = <0x8086>;
85 vendor-id = <0x8086>;
100 vendor-id = <0x8086>;
115 vendor-id = <0x8086>;
130 vendor-id = <0x8086>;
145 vendor-id = <0x8086>;
160 vendor-id = <0x8086>;
175 vendor-id = <0x8086>;
190 vendor-id = <0x8086>;
[all …]
Dalder_lake.dtsi153 vendor-id = <0x8086>;
164 vendor-id = <0x8086>;
184 vendor-id = <0x8086>;
204 vendor-id = <0x8086>;
222 vendor-id = <0x8086>;
235 vendor-id = <0x8086>;
248 vendor-id = <0x8086>;
261 vendor-id = <0x8086>;
274 vendor-id = <0x8086>;
287 vendor-id = <0x8086>;
[all …]
Draptor_lake_p.dtsi56 vendor-id = <0x8086>;
66 vendor-id = <0x8086>;
79 vendor-id = <0x8086>;
94 vendor-id = <0x8086>;
111 vendor-id = <0x8086>;
128 vendor-id = <0x8086>;
146 vendor-id = <0x8086>;
159 vendor-id = <0x8086>;
172 vendor-id = <0x8086>;
185 vendor-id = <0x8086>;
[all …]
Draptor_lake_s.dtsi58 vendor-id = <0x8086>;
77 vendor-id = <0x8086>;
97 vendor-id = <0x8086>;
119 vendor-id = <0x8086>;
139 vendor-id = <0x8086>;
159 vendor-id = <0x8086>;
179 vendor-id = <0x8086>;
199 vendor-id = <0x8086>;
219 vendor-id = <0x8086>;
230 vendor-id = <0x8086>;
[all …]
Dapollo_lake.dtsi57 vendor-id = <0x8086>;
71 vendor-id = <0x8086>;
86 vendor-id = <0x8086>;
101 vendor-id = <0x8086>;
118 vendor-id = <0x8086>;
131 vendor-id = <0x8086>;
144 vendor-id = <0x8086>;
157 vendor-id = <0x8006>;
170 vendor-id = <0x8086>;
183 vendor-id = <0x8086>;
[all …]
/Zephyr-latest/include/zephyr/usb/class/
Dusbd_msc.h21 const char *vendor; member
51 .vendor = t10_vendor, \
/Zephyr-latest/samples/sensor/sensor_shell/
DREADME.rst40 info :Get sensor info, such as vendor and model name, for all sensors.
69 **info**: prints vendor, model, and friendly name information for all sensors.
75 device name: apds9960@39, vendor: Avago Technologies, model: apds9960, friendly name: (null)
76 device name: mma8652fc@1d, vendor: NXP Semiconductors, model: fxos8700, friendly name: (null)
77 device name: ti_hdc@43, vendor: Texas Instruments, model: hdc, friendly name: (null)
78 device name: temp@4000c000, vendor: Nordic Semiconductor, model: nrf-temp, friendly name: (null)
/Zephyr-latest/subsys/usb/device/class/
DKconfig.bt12 bool "USB Bluetooth H4 vendor command"
17 Enables vendor command to switch to H:4 transport using the bulk
/Zephyr-latest/subsys/dap/
DKconfig28 string "Probe vendor"
36 string "Target board vendor"
44 string "Target device vendor"
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst32 - Your hardware vendor provides an official binding outside of the Linux
104 Rules for vendor prefixes
107 The following general rules apply to vendor prefixes in :ref:`compatible
110 - If your device is manufactured by a specific vendor, then its compatible
111 should have a vendor prefix.
113 If your binding describes hardware with a well known vendor from the list in
114 :zephyr_file:`dts/bindings/vendor-prefixes.txt`, you must use that vendor
117 - If your device is not manufactured by a specific hardware vendor, do **not**
118 invent a vendor prefix. Vendor prefixes are not mandatory parts of compatible
120 actual vendor. There are some exceptions to this rule, but the practice is
[all …]
/Zephyr-latest/doc/_scripts/
Dgen_boards_catalog.py88 vendor = "others"
91 vendor = folder.name
114 "vendor": vendor,
/Zephyr-latest/soc/espressif/common/
DKconfig.flash18 Enable this to support auto detection of ISSI chips if chip vendor not directly
26 Enable this to support auto detection of MXIC chips if chip vendor not directly
34 Enable this to support auto detection of GD (GigaDevice) chips if chip vendor not
47 Enable this to support auto detection of Winbond chips if chip vendor not directly
55 Enable this to support auto detection of BOYA chips if chip vendor not directly
63 Enable this to support auto detection of TH chips if chip vendor not directly
72 Enable this to support auto detection of Octal MXIC chips if chip vendor not directly
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_offload.rst16 The network offloading API provides hooks that a device vendor can use
18 actual network connection creation, data transfer, etc., is done in the vendor
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_msc_scsi.h66 const char *vendor; member
85 void scsi_init(struct scsi_ctx *ctx, const char *disk, const char *vendor,
/Zephyr-latest/tests/drivers/disk/disk_performance/boards/
Dqemu_x86_64.overlay10 vendor-id = <0x1B36>;
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/boards/
Dpcie_ivshmem.dtsi13 vendor-id = <0x1af4>;
/Zephyr-latest/tests/drivers/virtualization/ivshmem/plain/
Dapp.overlay13 vendor-id = <0x1af4>;
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/boards/
Dpcie_ivshmem.dtsi13 vendor-id = <0x1af4>;
/Zephyr-latest/tests/drivers/virtualization/ivshmem/plain/boards/
Dpcie_ivshmem.dtsi13 vendor-id = <0x1af4>;
/Zephyr-latest/tests/drivers/disk/disk_access/boards/
Dqemu_x86_64.overlay10 vendor-id = <0x1B36>;
/Zephyr-latest/subsys/testsuite/boards/unit_testing/unit_testing/
DKconfig.defconfig10 # Bluetooth unit tests assume HCI vendor extensions are available
/Zephyr-latest/scripts/west_commands/
Dboards.py108 vendor=board.vendor,
/Zephyr-latest/doc/hardware/peripherals/audio/
Ddai.rst10 It can be configured with bespoke data for vendor specific configuration.
/Zephyr-latest/scripts/utils/
Dboard_v1_to_v2.py44 def board_v1_to_v2(board_root, board, new_board, group, vendor, soc, variants): argument
72 "vendor": vendor,
212 args.vendor,
/Zephyr-latest/samples/bluetooth/st_ble_sensor/
DREADME.rst5 Export vendor-specific GATT services over BLE.
10 This application demonstrates Bluetooth LE peripheral by exposing vendor-specific

12345678