Hi Michał - You want the devicetree organization to match the hardware description. So in the case of the Ambiq GPIO controller, I think your best bet is to create only GPIOA and GPIOB controllers. Th

#bluetooth #ambiq

Hey Keith, Thanks for the lead. This certainly helps. I still have some questions, hope that's ok. Lets say I'm describing the bytes that relate to gpio controller A: ``` gpioa: gpio@40010000 { compat

#bluetooth #ambiq

The GPIO driver for the ITE IT8xxx2 family also interleaves the register space. You could follow the model used for that driver - create multiple reg phandles for the individual registers. https://git

#bluetooth #ambiq

Hello, I'm trying to add support for the Ambiq Apollo series chips. I'm new to the Zephyr and not very experienced with Device Tree format. Currently I'm working on the zephyr/dts/arm/ambiq/apollo.dts

#bluetooth #ambiq