Home
last modified time | relevance | path

Searched +full:vendor +full:- +full:specific (Results 1 – 25 of 222) sorted by relevance

123456789

/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/
Dpdu_vendor.h4 * SPDX-License-Identifier: Apache-2.0
13 /* Presence of vendor Data PDU struct octet3 */
16 uint8_t resv[OCTET3_LEN]; /* nRF specific octet3 required for NRF_CCM use */
24 /* Presence of vendor BIS PDU struct octet3 */
27 uint8_t resv[OCTET3_LEN]; /* nRF specific octet3 required for NRF_CCM use */
31 /* Presence of vendor CIS PDU struct octet3 */
34 uint8_t resv[OCTET3_LEN]; /* nRF specific octet3 required for NRF_CCM use */
38 /* Presence of ISOAL helper vendor ISO PDU struct octet3 */
41 uint8_t resv[OCTET3_LEN]; /* nRF specific octet3 required for NRF_CCM use */
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/
Dull_iso_internal.h2 * Copyright (c) 2020-2021 Nordic Semiconductor ASA
4 * SPDX-License-Identifier: Apache-2.0
14 CONFIG_BT_CTLR_ISO_TX_BUFFERS) - \
38 MIN((CONFIG_BT_CTLR_ISO_TX_BUFFER_SIZE - BT_HCI_ISO_SDU_TS_HDR_SIZE), \
56 /* Must be implemented by vendor if vendor-specific data path is supported */
58 /* Must be implemented by vendor if vendor-specific data path is supported */
64 /* Must be implemented by vendor if vendor-specific data path is supported */
72 /* Must be implemented by vendor if vendor-specific data path is supported */
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst1 .. _dt-writing-bindings:
21 Zephyr aims for devicetree :ref:`dt-source-compatibility`. Therefore, if there
24 justify any Zephyr-specific divergences.
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
55 - For example, a binding for compatible ``vnd,foo`` must be named ``vnd,foo.yaml``.
56 - If the binding is bus-specific, you can append the bus to the file name;
57 for example, if the binding YAML has ``on-bus: bar``, you may name the file
58 ``vnd,foo-bar.yaml``.
[all …]
/Zephyr-latest/dts/bindings/mtd/
Datmel,at25.yaml2 # SPDX-License-Identifier: Apache-2.0
11 - Microchip AT25xxx
12 - ST M95xxx
15 width, and timeout) available from the datasheet of the specific EEPROM. The compatible string for
16 these can list the specific EEPROM vendor and model along with the vendor EEPROM family as long as
17 the least-specific compatible entry is "atmel,at25".
29 address-width = <16>;
30 spi-max-frequency = <DT_FREQ_M(20)>;
37 include: ["atmel,at2x-base.yaml", spi-device.yaml]
Datmel,at24.yaml3 # SPDX-License-Identifier: Apache-2.0
12 - Microchip AT24xxx
13 - ST M24xxx
16 width, and timeout) available from the datasheet of the specific EEPROM. The compatible string for
17 these can list the specific EEPROM vendor and model along with the vendor EEPROM family as long as
18 the least-specific compatible entry is "atmel,at24".
24 clock-frequency = <I2C_BITRATE_FAST>;
31 address-width = <16>;
38 include: ["atmel,at2x-base.yaml", i2c-device.yaml]
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig.silabs3 # SPDX-License-Identifier: Apache-2.0
8 bool "Silicon Labs vendor specific HCI extensions"
10 Enable Silicon Labs vendor specific HCI extensions.
51 # Hidden option for Co-Operative Link Layer thread priority
Dapollox_blue.h4 * SPDX-License-Identifier: Apache-2.0
45 * The devices mainly include the required gpio (e.g. reset-gpios,
46 * irq-gpios).
92 * @brief Vendor specific setup before general HCI command sequence for
100 * @brief Check if vendor specific receiving handling is ongoing.
104 * @return true indicates if vendor specific receiving handling is ongoing.
109 * @brief Do the specific preprocessing in HCI packet receiving ISR if needed,
/Zephyr-latest/samples/bluetooth/hci_vs_scan_req/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_vs_scan_req
2 :name: HCI Vendor-Specific Scan Request
3 :relevant-api: bluetooth
5 Use vendor-specific HCI commands to enable Scan Request events when using legacy advertising.
31 See :zephyr:code-sample-category:`bluetooth` samples for details.
Dsample.yaml2 name: Bluetooth HCI Vendor-Specific Scan Request
7 - nrf52dk/nrf52832
9 - nrf52dk/nrf52832
11 - CONFIG_BT_LL_SW_SPLIT=y
/Zephyr-latest/samples/bluetooth/hci_vs_scan_req/src/
Dmain.c1 /* main.c - Application main entry point */
6 * SPDX-License-Identifier: Apache-2.0
14 "This app requires Zephyr-specific HCI vendor extensions");
17 #define DEVICE_NAME_LENGTH (sizeof(DEVICE_NAME) - 1)
60 * Added a Vendor Specific command to add this feature and save RAM.
75 cp->enable = (uint8_t) enable; in enable_legacy_adv_scan_request_event()
90 evt = (void *)buf->data; in vs_scanned()
93 vs->subevent, bt_addr_le_str(&evt->addr), evt->rssi); in vs_scanned()
137 printk("Vendor-Specific Scan Request sample started\n"); in bt_ready()
144 printk("Starting Vendor-Specific Scan Request sample\n"); in main()
/Zephyr-latest/samples/subsys/usb/webusb/src/
Dwebusb.h2 * Copyright (c) 2015-2019 Intel Corporation
4 * SPDX-License-Identifier: Apache-2.0
21 /* Handler for WebUSB Vendor specific commands */
32 * @brief Register Custom and Vendor request callbacks
34 * Function to register Custom and Vendor request callbacks
/Zephyr-latest/samples/bluetooth/st_ble_sensor/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_st_ble_sensor
3 :relevant-api: bt_gatt bluetooth
5 Export vendor-specific GATT services over Bluetooth.
10 This application demonstrates Bluetooth LE peripheral by exposing vendor-specific
32 See :zephyr:code-sample-category:`bluetooth` samples for details.
Dsample.yaml3 description: Demonstrates Bluetooth LE peripheral by exposing vendor-specific GATT
/Zephyr-latest/drivers/ethernet/
Dphy_xlnx_gem.h7 * SPDX-License-Identifier: Apache-2.0
21 /* PHY register addresses & constants that are not vendor-specific */
25 /* PHY registers & constants -> Marvell Alaska specific */
27 /* Marvell PHY ID bits [3..0] = revision -> discard during ID check */
79 /* TI PHY ID bits [3..0] = revision -> discard during ID check */
126 * @brief Vendor-specific PHY management function pointer table struct
128 * Contains the PHY management function pointers for a specific PHY
142 * Contains the PHY management function pointers for a specific PHY
152 /* PHY identification function -> generic, not vendor-specific */
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dhealth_srv.h8 * SPDX-License-Identifier: Apache-2.0
32 * vendor. Vendor specific faults should be interpreted in the context
38 * representing the device vendor or some other vendor whose vendor
39 * specific fault values are used.
67 * vendor. Vendor specific faults should be interpreted in the context
96 /** @brief Run a self-test.
98 * The Health server may support up to 256 self-tests for each Company
99 * ID. The behavior for all test IDs are vendor specific, and should be
121 * also help identify the specific element the server is in.
/Zephyr-latest/include/zephyr/net/
Dieee802154_ie.h4 * SPDX-License-Identifier: Apache-2.0
16 * All specification references in this file refer to IEEE 802.15.4-2020.
50 * @details See section 7.4.2.1, table 7-7, partial list, only IEs actually used
54 IEEE802154_HEADER_IE_ELEMENT_ID_VENDOR_SPECIFIC_IE = 0x00, /**< Vendor specific IE */
68 /** @brief Vendor Specific Header IE, see section 7.4.2.3. */
70 /** Vendor OUI */
72 /** Vendor specific information */
213 * @brief Define a vendor specific header IE, see section 7.4.2.3.
218 * uint8_t vendor_specific_info[] = {...some vendor specific IE content...};
223 * @param _vendor_oui an initializer for a 3 byte vendor oui array in little
[all …]
Dieee802154_radio_openthread.h4 * SPDX-License-Identifier: Apache-2.0
17 /** Bit number starting the OpenThread specific capabilities of ieee802154 driver. */
21 * OpenThread specific capabilities of ieee802154 driver.
30 /** Capability to support CST-related features.
32 * The CST-related features are described by "Specification changes for Thread-in-Mobile"
34 * CST Period IEs as described by chapter 4.6.6.1 of the Thread-in-Mobile specification
55 * 1 + max_extra_cca_attempts CCAs performed back-to-back.
57 * This mode is a non-standard experimental OpenThread feature. It allows transmission
76 * T_maxtxdelay = max_extra_cca_attempts * (aCcaTime + T_recca) - T_recca + T_ccatx
79 * See IEEE 802.15.4-2020, section 11.3, table 11-1 for the definition of aCcaTime.
[all …]
/Zephyr-latest/subsys/net/lib/dhcpv4/
DKconfig6 # SPDX-License-Identifier: Apache-2.0
18 module-dep = NET_LOG
19 module-str = Log level for DHCPv4 client
20 module-help = Enable debug diagnostic from DHCPV4 client.
51 bool "Encapsulated vendor specific option callbacks"
55 If set, custom callbacks for encapsulated vendor-specific
67 bool "Send vendor class identifier in DHCPv4 request"
71 DHCPv4 vendor class identifier option in the DHCPv4 request.
74 string "Vendor class identifier"
78 The string to include in the DHCPv4 vendor class identifier option
[all …]
/Zephyr-latest/include/zephyr/drivers/misc/
DREADME4 Zephyr Device Drivers API. Such drivers have only device-specific API providing
16 rendering. These operations are controlled by a vendor-specific API designed
19 * STM32 Wake-up Pins
20 STM32 wake-up pins are part of the Power Control (PWR) peripheral.
21 They can be used to wake-up the system from Poweroff through GPIO pins.
/Zephyr-latest/include/zephyr/drivers/firmware/scmi/
Dshmem.h4 * SPDX-License-Identifier: Apache-2.0
61 * @param mask value to negate and bitwise-and the old
64 * bitwise-or with the masked old value
77 * @brief Process vendor specific features when writing message
87 * @brief Process vendor specific features when reading message
/Zephyr-latest/subsys/net/ip/
DKconfig.stats4 # SPDX-License-Identifier: Apache-2.0
14 module-dep = NET_LOG
15 module-str = Log level for network statistics
16 module-help = Enables statistics module to output debug messages.
118 bool "Point-to-point (PPP) statistics"
134 bool "Vendor specific Ethernet statistics"
138 from vendor specific hardware registers in a form of
139 key-value pairs. Deciphering the information may require
140 vendor documentation.
150 bool "Wi-Fi statistics"
[all …]
/Zephyr-latest/include/zephyr/drivers/pcie/
Dcap.h4 * SPDX-License-Identifier: Apache-2.0
30 #define PCI_CAP_ID_PCIX 0x07U /**< PCI-X */
32 #define PCI_CAP_ID_VNDR 0x09U /**< Vendor-Specific */
35 #define PCI_CAP_ID_SHPC 0x0CU /**< PCI Standard Hot-Plug Controller */
36 #define PCI_CAP_ID_SSVID 0x0DU /**< Bridge subsystem vendor/device ID */
40 #define PCI_CAP_ID_MSIX 0x11U /**< MSI-X */
62 #define PCIE_EXT_CAP_ID_MFVC 0x0008U /**< Multi-Function VC Capability */
65 #define PCIE_EXT_CAP_ID_VNDR 0x000BU /**< Vendor-Specific Extended Capability */
66 #define PCIE_EXT_CAP_ID_CAC 0x000CU /**< Config Access Correlation - obsolete */
68 #define PCIE_EXT_CAP_ID_ARI 0x000EU /**< Alternate Routing-ID Interpretation */
[all …]
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst21 - Support for multi-core, multi-arch AMP (Asymmetrical Multi Processing) SoCs
22 - Support for multi-SoC boards
23 - Support for reusing the SoC and board Kconfig trees outside of the Zephyr
25 - Support for advanced use cases with :ref:`sysbuild`
26 - Removal of all existing arbitrary and inconsistent uses of Kconfig and folder
38 Some non-critical features, enhancements and improvements of the new hardware
47 with two options if they have an out-of-tree board (or SoC):
49 #. Convert the out-of-tree board to the current hardware model (recommended)
57 can then use the `example-application conversion Pull Request`_ as an example on
59 and works reliably in many cases (though multi-core SoCs may not be handled
[all …]
/Zephyr-latest/dts/bindings/firmware/
Darm,scmi-clock.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "arm,scmi-clock"
8 include: [base.yaml, clock-controller.yaml]
18 "#clock-cells":
22 Vendor-specific clock identifier. Needs to match identifier
26 clock-cells:
27 - name
/Zephyr-latest/dts/bindings/base/
Dbase.yaml12 - "okay" means the resource is operational and, for example,
14 - "disabled" means the resource is not operational and the system
19 - "ok" # Deprecated form
20 - "okay"
21 - "disabled"
22 - "reserved"
23 - "fail"
24 - "fail-sss"
27 type: string-array
32 represents. Each device driver checks for specific compatible
[all …]

123456789