Module device_tree
Modules§
Structs§
- CanIrq
- CanPin
- CanRegistry
Entry - I2cBus
Pin - I2cBus
Registry Entry - I2cDev
Pin - I2cDevice
Registry Entry - KeyRegistry
Entry - LedRegistry
Entry - Peripheral
- SpiBus
Pin - SpiBus
Registry Entry - SpiDev
Pin - SpiDevice
Registry Entry - Tree
Node
Enums§
Constants§
Functions§
- can_
by_ compatible compatiblematches either the osiris-namespacedosiris,stm32l4-canor the canonical Zephyrst,stm32-bxcan— both refer to the same bxCAN hardware, and the registry stores whichever the DT node declared. Either string accepted on lookup so callers don’t need to know which name the board overlay used.- i2c_
bus_ by_ dev - i2c_
device_ by_ compatible - key_
by_ alias - resolve a /aliases entry to its KeyRegistryEntry
- key_
by_ code - find a key by its
osiris,code/zephyr,codevalue - key_
by_ label - find a key by its
labelproperty (exact match) - led_
by_ alias - resolve a /aliases entry to its LedRegistryEntry
- led_
by_ label - find an LED by its
labelproperty (exact match) - led_
by_ node - find an LED by its NODES index
- peripheral_
by_ compatible - find the first enabled peripheral for which any compatible string equals
c - peripheral_
by_ name_ under - find a peripheral by name scoped to a specific parent node index safe form of name lookup since node names are only unique among siblings
- peripheral_
by_ node - find a peripheral by its NODES index NODES indices are unique
- peripheral_
by_ path - find a peripheral by its full path from root, with or without unit addresses
e.g.
soc/i2c@40005400/lsm6dsl@6aorsoc/i2c/lsm6dslat each level the first sibling whose name matches is taken - peripheral_
by_ phandle - find a peripheral by its phandle value ignores enabled status - phandle targets like clock providers may have no status prop phandle values are unique
- peripherals_
by_ compatible - iterate all enabled peripherals for which any compatible string equals
c - peripherals_
by_ name - iterate all peripherals whose node name matches, with or without unit address
e.g.
channelmatcheschannel@0,channel@1, etc. across all parents node names are only unique among siblings - useperipheral_by_name_underorperipheral_by_pathwhen you need an unambiguous match - spi_
bus_ by_ dev - spi_
device_ by_ compatible