-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] build all Bridle samples test runs into devicetree error
#272
Comments
rexut
added a commit
that referenced
this issue
Nov 15, 2024
Add statement about: * the CI workflow changes * the standalone 'stm32f777xx' SoC support by Bridle * the DTS binding and Kconfig changes for the two I2C-based GPIO expander 'PCA9554' and 'PCA9555' * the copy-and-own of Sphinx extension 'warnings_filter' * the changes on documentation level: Sphinx v8.1, Sphinx copy button, inter-Sphinx links with valid official syntax and update output messages Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <linz@li-pro.net>
rexut
added a commit
that referenced
this issue
Nov 15, 2024
Add statement about: * the CI workflow changes * the standalone 'stm32f777xx' SoC support by Bridle * the DTS binding and Kconfig changes for the two I2C-based GPIO expander 'PCA9554' and 'PCA9555' * the copy-and-own of Sphinx extension 'warnings_filter' * the changes on documentation level: Sphinx v8.1, Sphinx copy button, inter-Sphinx links with valid official syntax and update output messages Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <linz@li-pro.net>
rexut
added a commit
that referenced
this issue
Nov 18, 2024
Add statement about: * the CI workflow changes * the standalone 'stm32f777xx' SoC support by Bridle * the DTS binding and Kconfig changes for the two I2C-based GPIO expander 'PCA9554' and 'PCA9555' * the copy-and-own of Sphinx extension 'warnings_filter' * the changes on documentation level: Sphinx v8.1, Sphinx copy button, inter-Sphinx links with valid official syntax and update output messages Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <linz@li-pro.net>
rexut
added a commit
that referenced
this issue
Nov 18, 2024
Add statement about: * the CI workflow changes * the standalone 'stm32f777xx' SoC support by Bridle * the DTS binding and Kconfig changes for the two I2C-based GPIO expander 'PCA9554' and 'PCA9555' * the copy-and-own of Sphinx extension 'warnings_filter' * the changes on documentation level: Sphinx v8.1, Sphinx copy button, inter-Sphinx links with valid official syntax and update output messages Add GitHub issues #270, #271, #272 and #274. Signed-off-by: Stephan Linz <linz@li-pro.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Zephyr upstream no longer supports the inflexible Kconfig object
SDMMC_VOLUME_NAME
and requires a proper name setup on Device tree level by the new propertydisk-name
.To Reproduce
Steps to reproduce the behavior:
main
branchExpected behavior
Test suite runs properly without any error.
Impact
Showstopper, because the CI pipeline will fail.
Logs and console output
Screenshots
None.
Development Environment (please complete the following information):
main
, Zephyr v4.0.0-rc2 (upstreammain
)Additional context
Add the missing property in Bridle's Devicetree includes.
Procedure
See: zephyrproject-rtos/zephyr#80709 – SDMMC and MMC subsystem disk drivers rework
Since zephyrproject-rtos/zephyr@a1dc0b8 Zephyr upstream has removed
CONFIG_SDMMC_VOLUME_NAME
, and set the disk name based on thedisk-name
property. This aligns with other disk drivers, and allows for multiple instances of thesdmmc_subsys
disk driver to be registered.Bridle uses the
sdmmc_subsys
disk driver in following boards and shields:bridle/boards/waveshare/rp2040/rpigeek_mmc_sdcard.dtsi
Lines 25 to 29 in d4da4c7
bridle/boards/shields/rpi_pico_lcd/boards/waveshare_pico_restouch_lcd_2_8/sdhc_spi_sdmmc.dtsi
Lines 15 to 19 in d4da4c7
bridle/boards/shields/rpi_pico_lcd/boards/waveshare_pico_restouch_lcd_3_5/sdhc_spi_sdmmc.dtsi
Lines 15 to 19 in d4da4c7
The text was updated successfully, but these errors were encountered: