Home
last modified time | relevance | path

Searched refs:prefixes (Results 1 – 25 of 29) sorted by relevance

12

/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst104 Rules for vendor prefixes
107 The following general rules apply to vendor prefixes in :ref:`compatible
114 :zephyr_file:`dts/bindings/vendor-prefixes.txt`, you must use that vendor
118 invent a vendor prefix. Vendor prefixes are not mandatory parts of compatible
123 - Do not submit additions to Zephyr's :file:`dts/bindings/vendor-prefixes.txt`
129 :file:`dts/bindings/vendor-prefixes.txt` file to any directory in your
131 prefixes, and will not generate warnings or errors if you use them in your
134 - We sometimes synchronize Zephyr's vendor-prefixes.txt file with the Linux
Dbindings-syntax.rst106 :zephyr_file:`dts/bindings/vendor-prefixes.txt` for a list of accepted vendor
107 prefixes. The ``device`` part is usually from the datasheet.
Dintro-syntax-structure.rst233 :zephyr_file:`dts/bindings/vendor-prefixes.txt` contains a list of commonly
/Zephyr-latest/cmake/modules/
Dpre_dt.cmake9 # DTS files, bindings, and vendor prefixes are.
15 # implementation files (like bindings, vendor prefixes, etc.) are
Ddts.cmake70 # implementation files (like bindings, vendor prefixes, etc.) are
131 # The location of a file containing known vendor prefixes, relative to
134 set(VENDOR_PREFIXES dts/bindings/vendor-prefixes.txt)
178 # well as all the devicetree bindings and vendor prefixes associated
233 list(APPEND EXTRA_GEN_EDT_ARGS --vendor-prefixes ${vendor_prefixes})
/Zephyr-latest/doc/
DCMakeLists.txt140 --vendor-prefixes ${ZEPHYR_BASE}/dts/bindings/vendor-prefixes.txt
/Zephyr-latest/doc/connectivity/networking/
Deth_bridge_native_sim_setup.rst119 IPv6 prefixes (max 2):
147 IPv6 prefixes (max 2):
Doverview.rst26 * The system also supports multiple IPv6 prefixes and the maximum
/Zephyr-latest/subsys/logging/
DKconfig.mode37 but not runtime filtering. There are no timestamps, prefixes,
/Zephyr-latest/doc/contribute/style/
Dcmake.rst80 - **Consistent Prefixing**: Use consistent prefixes for variables to avoid name
/Zephyr-latest/samples/net/capture/
DREADME.rst130 IPv6 prefixes (max 2):
187 IPv6 prefixes (max 2):
/Zephyr-latest/doc/connectivity/networking/api/
Dieee802154.rst62 IEEE802154/ieee802154 prefixes there.
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst157 The following are the prefixes used to indicate the cores:
159 .. csv-table:: nRF54H20 log prefixes
221 The following are the prefixes used to indicate the cores:
223 .. csv-table:: nRF54H20 log prefixes
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig138 platforms which prefixes a WAITI entry with 128 NOP
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv636 int "Max number of IPv6 prefixes per network interface"
253 Size of the allow/deny filter list of IPv6 prefixes. User can
/Zephyr-latest/doc/build/
Dzephyr_cmake_package.rst360 .. note:: The ``<PackageName>_ROOT`` variables, as well as the default paths, are just the prefixes
361 to the search path. These prefixes get combined with additional path suffixes, which together
/Zephyr-latest/doc/hardware/porting/
Dsoc_porting.rst50 :zephyr_file:`dts/bindings/vendor-prefixes.txt`. If the SoC vendor does not
Dboard_porting.rst246 :zephyr_file:`dts/bindings/vendor-prefixes.txt` then you must use
/Zephyr-latest/doc/develop/west/
Dbuilt-in.rst125 ``always``. SHAs may be given as unique prefixes as long as they are acceptable
/Zephyr-latest/doc/releases/
Dmigration-guide-4.0.rst338 to use lower-case strings without the ``BT_HCI_QUIRK_`` and ``BT_HCI_BUS_`` prefixes.
Drelease-notes-1.7.rst274 * ``ZEP-1329`` - Rename kernel APIs that have nano\_ prefixes
Drelease-notes-2.7.rst785 Known vendor prefixes are defined in
786 :file:`dts/bindings/vendor-prefixes.txt` files, which may appear in any
794 * Various bindings had incorrect vendor prefixes in their :ref:`compatible
1365 * :github:`37797` - Merge vendor-prefixes.txt from all modules with build.settings.dts_root in zeph…
Drelease-notes-2.1.rst929 * :github:`7213` - DTS should use (one or more) prefixes on all defines
/Zephyr-latest/doc/develop/application/
Dindex.rst733 Application-specific source code should not use symbol name prefixes that have
1153 :zephyr_file:`dts/bindings/vendor-prefixes.txt` if submitting upstream to Zephyr, or be
/Zephyr-latest/dts/bindings/
Dvendor-prefixes.txt4 # This isn't an exhaustive list, but you should add new prefixes to it

12