You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An example from the MCU world is the 96board Carbon in which we have a ST STM32F401 and Nordic NRF 51822. The NRF is acting as a bluetooth radio.
We should have some means to utilize SoC dtsi files and compose a single system devicetree that represents the boards and the connections between the various Soc's (in this case via SPI).
The text was updated successfully, but these errors were encountered:
Having become more familiar with the system DT specification, I think it would be challenging to do this. There doesn't seem to be a clean way to compose system devicetrees. The main challenges are related to namespace management. Consider that CPU clusters, as top level nodes, share a namespace. So if we want to be able to compose a system devicetree by #include of other SoC level system devicetrees, there is the potential for two CPU clusters with the same name to conflict. A similar problem exists in the /domains node.
I think this issue should be closed. As I have already communicated internally within the zephyr project efforts for this, I believe this is a non-goal for an initial effort.
An example from the MCU world is the 96board Carbon in which we have a ST STM32F401 and Nordic NRF 51822. The NRF is acting as a bluetooth radio.
We should have some means to utilize SoC dtsi files and compose a single system devicetree that represents the boards and the connections between the various Soc's (in this case via SPI).
The text was updated successfully, but these errors were encountered: