boards: adafruit_feather_m0: don't throw compiler warnings on using custom sercom config #23133
Labels
RFC
Request For Comments: want input from the community
Comments
KubaFYI
changed the title
|
What do you think @henrikbrixandersen ? |
|
Sounds like an okay solution to me. |
KubaFYI
added a commit
to KubaFYI/zephyr
that referenced
this issue
Mar 5, 2020
In order to use its serial peripheral SERCOMs SAMD socs require their pins to be configured with pinmux. Currently pins are muxed only for the boards' default serial interfaces. The pinmux code is written to throw a compiler error if a user tries to use any sercom in a way it wasn't pre-defined to be used. This commit changes compiler errors to warnings so that user can provide custom pinmuxing code in their app. Fixes zephyrproject-rtos#23133 Signed-off-by: Kuba Sanak <contact@kuba.fyi>
galak
pushed a commit
that referenced
this issue
Apr 17, 2020
In order to use its serial peripheral SERCOMs SAMD socs require their pins to be configured with pinmux. Currently pins are muxed only for the boards' default serial interfaces. The pinmux code is written to throw a compiler error if a user tries to use any sercom in a way it wasn't pre-defined to be used. This commit changes compiler errors to warnings so that user can provide custom pinmuxing code in their app. Fixes #23133 Signed-off-by: Kuba Sanak <contact@kuba.fyi>
hakehuang
pushed a commit
to hakehuang/zephyr
that referenced
this issue
Jun 20, 2020
In order to use its serial peripheral SERCOMs SAMD socs require their pins to be configured with pinmux. Currently pins are muxed only for the boards' default serial interfaces. The pinmux code is written to throw a compiler error if a user tries to use any sercom in a way it wasn't pre-defined to be used. This commit changes compiler errors to warnings so that user can provide custom pinmuxing code in their app. Fixes zephyrproject-rtos#23133 Signed-off-by: Kuba Sanak <contact@kuba.fyi>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to use it's serial peripheral SERCOMs SAD1 requires their pins to be configured with pinmux. Currently that's enabled only for the board default serial interfaces: the USART TX/RX on sercom0, an SPI interface on sercom4, and the USB port. The pinmux code currently is written to throw a compiler error if a user app tries to use any sercom in a way it wasn't pre-defined to be used. The error claims the pin mapping have not been configured but at the same time it doesn't give a chance for this configuration to take place in app code.
I propose that those errors are changed to warnings which would allow users to proceed with compilation and configure the pin mappings themselves should they wish to use sercom1-sercom3.
The relevant file is pinmux.c
The text was updated successfully, but these errors were encountered: