Home
last modified time | relevance | path

Searched refs:manufacturer (Results 1 – 25 of 40) sorted by relevance

12

/Zephyr-latest/scripts/tests/twister_blackbox/
Dtest_hardwaremap.py111 def test_generate(self, capfd, out_path, manufacturer, product, serial, runner): argument
122 manufacturer=id_man,
128 for id_man in manufacturer:
163 def test_few_generate(self, capfd, out_path, manufacturer, product, serial, runner): argument
174 manufacturer=manufacturer,
179 manufacturer=manufacturer,
184 manufacturer=manufacturer,
189 manufacturer=manufacturer,
244 def test_texas_exeption(self, capfd, out_path, manufacturer, product, serial, location): argument
255 manufacturer=manufacturer,
/Zephyr-latest/tests/bluetooth/host/crypto/mocks/
Dhci_core.c13 .manufacturer = 0x1234,
/Zephyr-latest/samples/bluetooth/broadcaster/
DREADME.rst5 Periodically send out advertising packets with a manufacturer data element.
12 a manufacturer data element. The content of the data is a single byte
/Zephyr-latest/tests/bluetooth/host/id/mocks/
Dhci_core.c15 .manufacturer = 0x1234,
/Zephyr-latest/scripts/tests/twister/
Dtest_hardwaremap.py399 mocked_hm.manufacturer = ['dummy manufacturer', 'Texas Instruments']
407 manufacturer='wrong manufacturer',
414 manufacturer='dummy manufacturer',
421 manufacturer='dummy manufacturer',
428 manufacturer='Texas Instruments',
435 manufacturer='Texas Instruments',
/Zephyr-latest/samples/subsys/usb/common/
DKconfig.sample_usbd13 string "USB device sample manufacturer string"
16 USB device sample manufacturer string.
/Zephyr-latest/tests/bluetooth/host/conn/mocks/
Dhci_core.c31 .manufacturer = 0x1234,
/Zephyr-latest/doc/security/standards/
Detsi-303645.rst64 - physical interface used by the manufacturer to communicate with the device during
70 manufacturer will provide security updates.
72 * - device manufacturer
99 * - manufacturer
100 - relevant economic operator in the supply chain (including the device manufacturer).
127 to the manufacturer.
136 - data from a device that can provide information to help the manufacturer identify issues
343 - The manufacturer should inform the user in a recognizable and apparent manner
360 - The manufacturer shall publish, in an accessible way that is clear and
370 support and a defined support period should be published by the manufacturer in an
[all …]
/Zephyr-latest/doc/build/dts/
Dbindings-syntax.rst35 compatible: "manufacturer,foo-device"
80 compatible: "manufacturer,device"
87 compatible = "manufacturer,device";
90 Assuming no binding has ``compatible: "manufacturer,device-v2"``, it would also
96 compatible = "manufacturer,device-v2", "manufacturer,device";
105 The ``manufacturer`` prefix identifies the device vendor. See
125 compatible: "manufacturer,serial"
137 In this example, a node with compatible ``"manufacturer,serial"`` must contain
519 compatible: "manufacturer,spi-peripheral"
534 compatible: "manufacturer,i3c-controller"
[all …]
/Zephyr-latest/subsys/bluetooth/services/
DKconfig.dis36 The device manufacturer inside Device Information Service.
183 …of an Organizationally Unique Identifier (OUI) concatenated with a manufacturer-defined identifier.
190 hex "Organizationally Unique Identifier (OUI) of the manufacturer."
196 …Shall contain an Organisationally Unique Identifier (OUI) followed by a manufacturer-defined inden…
203 The manufacturer-defined unique identifier is 40 bits long.
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dhardwaremap.py135 manufacturer = [ variable in HardwareMap
350 d.manufacturer
351 and d.manufacturer.casefold() in [m.casefold() for m in self.manufacturer]
356 if d.manufacturer == 'Texas Instruments' and not d.location.endswith('0'):
/Zephyr-latest/samples/bluetooth/scan_adv/
DREADME.rst12 advertising packets with a manufacturer data element. The content of the
/Zephyr-latest/drivers/sensor/st/vl53l0x/
DKconfig33 from the manufacturer default (0x29) to the address specified in the
/Zephyr-latest/doc/hardware/peripherals/
Dkscan.rst23 defined by a keymap provided by the keyboard manufacturer.
Dcharger.rst16 manufacturer. On charger devices with a control port, the charge profile can be configured by the
Dsmbus.rst16 lines. SMBus peripherals can provide various manufacturer information,
/Zephyr-latest/samples/bluetooth/broadcaster_multiple/
DREADME.rst20 manufacturer data is calculated to maximize the use of supported AD data length.
/Zephyr-latest/subsys/usb/device/class/netusb/
Dfunction_rndis.c164 static uint8_t manufacturer[] = CONFIG_USB_DEVICE_MANUFACTURER; variable
603 memcpy(net_buf_add(buf, sizeof(manufacturer) - 1), manufacturer, in rndis_query_handle()
604 sizeof(manufacturer) - 1); in rndis_query_handle()
/Zephyr-latest/drivers/flash/
DKconfig.nrf93 block size parameter (imposed by manufacturer) is possible but operation
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-shell.rst62 …] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
/Zephyr-latest/subsys/bluetooth/host/
Dhci_core.h368 uint16_t manufacturer; member
Dconn_internal.h279 uint16_t manufacturer; member
/Zephyr-latest/subsys/sd/
Dsd_ops.c187 cid->manufacturer = (uint8_t)((raw_cid[3U] & 0xFF000000U) >> 24U); in sdmmc_decode_cid()
314 LOG_DBG("Card MID: 0x%x, OID: %c%c", card_cid.manufacturer, in card_read_cid()
/Zephyr-latest/subsys/usb/device/
DKconfig32 string "USB manufacturer name"
/Zephyr-latest/drivers/modem/
Dmodem_cellular.c124 uint8_t manufacturer[MODEM_CELLULAR_DATA_MANUFACTURER_LEN]; member
383 strncpy(data->manufacturer, argv[1], sizeof(data->manufacturer) - 1); in modem_cellular_chat_on_cgmi()
1624 strncpy(info, &data->manufacturer[0], MIN(size, sizeof(data->manufacturer))); in modem_cellular_get_modem_info()

12