0861b5ba11
Add some details to help new users learn how to manage the nodes for compatibles corresponding to IP blocks on Nordic SoCs. The focus is on IP blocks where the pinmux is configured in devicetree. These typically have individual properties for each pin, like a SCK pin on a SPI peripheral, which correspond directly to a PSEL register value. These violate the usual devicetree convention of using a 'foo-gpios <&gpioX ...>' phandle property and work in ways that only make sense if you understand the underlying register map, so it's worth explaining them a bit more carefully. Skip these two bindings, which have no drivers: nordic,nrf-i2s.yaml, nordic,nrf-pdm.yaml. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| atmel,sam0-nvmctrl.yaml | ||
| atmel,sam-flash-controller.yaml | ||
| cypress,psoc6-flash-controller.yaml | ||
| flash-controller.yaml | ||
| ite,it8xxx2-flash-controller.yaml | ||
| nordic,nrf51-flash-controller.yaml | ||
| nordic,nrf52-flash-controller.yaml | ||
| nordic,nrf53-flash-controller.yaml | ||
| nordic,nrf91-flash-controller.yaml | ||
| nordic,nrf-qspi.yaml | ||
| nxp,kinetis-ftfa.yaml | ||
| nxp,kinetis-ftfe.yaml | ||
| nxp,kinetis-ftfl.yaml | ||
| nxp,lpc-iap.yaml | ||
| openisa,rv32m1-ftfe.yaml | ||
| silabs,gecko-flash-controller.yaml | ||
| st,stm32-flash-controller.yaml | ||
| st,stm32-qspi-nor.yaml | ||
| st,stm32f0-flash-controller.yaml | ||
| st,stm32f1-flash-controller.yaml | ||
| st,stm32f2-flash-controller.yaml | ||
| st,stm32f3-flash-controller.yaml | ||
| st,stm32f4-flash-controller.yaml | ||
| st,stm32f7-flash-controller.yaml | ||
| st,stm32g0-flash-controller.yaml | ||
| st,stm32g4-flash-controller.yaml | ||
| st,stm32h7-flash-controller.yaml | ||
| st,stm32l0-flash-controller.yaml | ||
| st,stm32l1-flash-controller.yaml | ||
| st,stm32l4-flash-controller.yaml | ||
| st,stm32l5-flash-controller.yaml | ||
| st,stm32wb-flash-controller.yaml | ||
| ti,stellaris-flash-controller.yaml | ||
| zephyr,sim-flash.yaml | ||