Date
1 - 5 of 5
Usage of generated dts *_GPIO_FLAGS
Diego Sueiro
Hello, I'd like to know what is the usage of the *_GPIO_FLAGS macro. For example in "dts/bindings/gpio/nxp,kinetis-gpio.yaml" file: cell_string: GPIO And "boards/arm/frdm_k64f/frdm_k64f.dts" file we have gpios = <&gpioa 4 GPIO_INT_ACTIVE_LOW>; This will generate in "zephyr/include/generated/generated_dts_board.h": #define GPIO_KEYS_1_GPIO_CONTROLLER "GPIO_0" In this example SW0_GPIO_FLAGS is not "consumed" by any source code, but "samples/basic/button/src/main.c" application is using SW0_GPIO_CONTROLLER, SW0_GPIO_PIN and SW0_GPIO_INT_CONF. I think we should name this gpio dts cell as "int_conf" instead of "flags", this way the dts configuration will be used in the button application, for example.
|
|
Erwan Gouriou
Hi Diego, Having direct match between generated FLAGS/INT_CONF aliases and application symbols would be a good idea.INT_CONF (Interrupt configuration I guess) is more restrictive than FLAGS.
On 4 May 2018 at 07:33, Diego Sueiro <diego.sueiro@...> wrote:
|
|
Diego Sueiro
Hi Erwan, Having direct match between generated FLAGS/INT_CONF aliases and application symbols would be a good idea. I agree with you about using a more generic name (FLAGS). So basically we will need to update the "samples/basic/button/src/ Does anyone have a better idea? On 4 May 2018 at 09:34, Erwan Gouriou <erwan.gouriou@...> wrote:
|
|
Erwan Gouriou
That's it!
|
|
Diego Sueiro
Erwan, I submitted a PR to apply these modifications: -- *dS Diego Sueiro sent from mobile
On Mon, 14 May 2018, 8:48 am Erwan Gouriou, <erwan.gouriou@...> wrote:
|
|