93d3a42776
'cell_string' yaml attribute has been introduced in order to help enforcement of specific string during defines generation. This adds complexity in understanding script behavior as a black box and create additional dependency which is not strictly required. For node specific generation functions (pinctrl and interrupts), this could be replaced directly by an hardcoded version (as everyone used the same 'cell_string' anyway). For extract_cells functions, string could be replaced by extracted property name. As a consequence, we're now able to generate defines for properties refering to these controllers via phandle. For instance, in following node spbtle-rf@0 { compatible = "st,spbtle-rf"; reg = <0>; reset-gpios = <&gpioa 8 0>; }; We'll be able to generate: #define ST_STM32_SPI_...LE_RF_0_RESET_GPIOS_CONTROLLER "GPIOA" #define ST_STM32_SPI_...PBTLE_RF_0_RESET_GPIOS_FLAGS_0 0 #define ST_STM32_SPI_..._SPBTLE_RF_0_RESET_GPIOS_PIN_0 8 Only impact for this whole change is for NXP clocks which were the only ones using 'cell_string' attribute with a value different than the default one. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> |
||
---|---|---|
.. | ||
arm,cmsdk-gpio.yaml | ||
atmel,sam0-gpio.yaml | ||
atmel.sam-gpio.yaml | ||
gpio-keys.yaml | ||
gpio-leds.yaml | ||
nxp,imx-gpio.yaml | ||
nxp,kinetis-gpio.yaml | ||
semtech,sx1509b-gpio.yaml | ||
st,stm32-gpio.yaml | ||
ti,cc2650-gpio.yaml |