Home
last modified time | relevance | path

Searched refs:vendor (Results 76 – 100 of 183) sorted by relevance

12345678

/Zephyr-latest/subsys/bluetooth/services/
DKconfig.dis102 The Vendor ID field is intended to uniquely identify the vendor of the
117 made by the vendor identified with the Vendor ID field. The vendors
126 release number in Binary-Coded Decimal. This is a vendor-assigned value,
/Zephyr-latest/doc/
DCMakeLists.txt140 --vendor-prefixes ${ZEPHYR_BASE}/dts/bindings/vendor-prefixes.txt
/Zephyr-latest/include/zephyr/sensing/
Dsensing_sensor.h151 .vendor = DT_NODE_VENDOR_OR(node, NULL), \
/Zephyr-latest/modules/openthread/
DCMakeLists.txt105 …ONFIG_OPENTHREAD_NETDIAG_VENDOR_INFO OT_NETDIAG_VENDOR_INFO "Allow setting vendor info at runtime")
135 …CE ${CONFIG_OPENTHREAD_COPROCESSOR_VENDOR_HOOK_SOURCE} CACHE STRING "NCP vendor hook source file n…
143 …ENSION} CACHE STRING "Path to CMake file to define and link Openthread CLI vendor extension" FORCE)
DKconfig.features269 bool "Allow setting vendor info at runtime"
402 string "Path to CMake file to define and link Openthread CLI vendor extension"
/Zephyr-latest/doc/services/portability/
Dcmsis_rtos_v2.rst6 Cortex-M Software Interface Standard (CMSIS) RTOS is a vendor-independent
/Zephyr-latest/subsys/bluetooth/common/
DKconfig255 Supported Commands, Supported Features vendor commands.
258 bool "Allow vendor specific HCI event Zephyr Fatal Error"
265 bool "Use heuristics to guess HCI vendor extensions support in advance"
270 supports the HCI vendor extensions in advance, in order to prevent
271 sending vendor commands to controller which may interpret them in
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst230 The recommended format is ``"vendor,device"``, like ``"avago,apds9960"``,
231 or a sequence of these, like ``"ti,hdc", "ti,hdc1010"``. The ``vendor``
232 part is an abbreviated name of the vendor. The file
233 :zephyr_file:`dts/bindings/vendor-prefixes.txt` contains a list of commonly
234 accepted ``vendor`` names. The ``device`` part is usually taken from the
Dbindings-syntax.rst79 # Note the comma-separated vendor prefix and device name
105 The ``manufacturer`` prefix identifies the device vendor. See
106 :zephyr_file:`dts/bindings/vendor-prefixes.txt` for a list of accepted vendor
110 vendor. In these cases, there is no vendor prefix. One example is the
/Zephyr-latest/doc/hardware/peripherals/
Di3c.rst176 compatible = "vendor,i3c";
194 compatible = "vendor,i3c-dev";
202 compatible = "vendor-i2c-dev";
336 compatible = "vendor-i2c-dev";
Dbc12.rst51 The power down operation is vendor specific.
/Zephyr-latest/samples/subsys/usb/testusb/
DREADME.rst26 $ sudo modprobe usbtest vendor=0x2fe3 product=0x0009
/Zephyr-latest/doc/services/storage/disk/
Dnvme.rst49 vendor-id = <VENDOR_ID>;
/Zephyr-latest/drivers/serial/
DKconfig.ns1655076 Texas Instruments K3 SoCs by enabling a vendor specific extended register
/Zephyr-latest/drivers/ieee802154/
DKconfig.nrf546 This option enables setting custom vendor EUI64 value
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dtestplan.py705 vendor_filter = self.options.vendor
753 platforms = list(filter(lambda p: p.vendor in vendor_filter, self.platforms))
902 if ts.vendor_allow and plat.vendor not in ts.vendor_allow:
908 if ts.vendor_exclude and plat.vendor in ts.vendor_exclude:
1126 lambda inst: inst.platform.vendor not in vendor_filter,
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst19 frequency. The available configuration options are vendor/SoC dependent and can
23 The way pin control is implemented in hardware is vendor/SoC specific. It is
229 vendor/SoC, so the Devicetree binding files for the pin control drivers are the
376 The pin configuration is stored in an opaque type that is vendor/SoC dependent:
396 already used by the same vendor in other operating systems, e.g. Linux.
/Zephyr-latest/doc/build/
Dzephyr_cmake_package.rst49 Zephyr freestanding applications, Zephyr workspace application with vendor forks, etc..
270 ├── zephyr-vendor
284 * ``zephyr-vendor``
294 set(ZEPHYR_PREFER "zephyr-custom" "zephyr-vendor")
/Zephyr-latest/doc/_scripts/
Dgen_devicetree_rest.py47 def vendor(self, vnd): member in VndLookup
419 title = vnd_lookup.vendor(vnd).strip()
/Zephyr-latest/subsys/net/l2/openthread/
DKconfig256 string "Path to vendor hook source file"
258 Provides path to compile vendor hook file.
/Zephyr-latest/samples/subsys/usb/hid-mouse/
DREADME.rst80 Input device ID: bus 0x3 vendor 0x2fe3 product 0x7 version 0x110
/Zephyr-latest/boards/others/stm32_min_dev/doc/
Dindex.rst27 Each board vendor has their own variations in pin mapping on their boards'
/Zephyr-latest/include/zephyr/drivers/
Dsensor.h1389 const char *vendor; member
1397 .vendor = _vendor, \
/Zephyr-latest/dts/bindings/
Dvendor-prefixes.txt1 # Device tree binding vendor prefix registry. Keep this list in
11 # <vendor-prefix><TAB><Full name of vendor>
720 virtual Used for virtual device without specific vendor.
725 vnd A stand-in for a real vendor which can be used in examples and tests
/Zephyr-latest/drivers/wifi/infineon/
DKconfig.airoc56 custom or vendor CYW43xx modules.

12345678