-
Notifications
You must be signed in to change notification settings - Fork 3
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 GPIO drivers test runs into devicetree error
#271
Comments
rexut
added a commit
that referenced
this issue
Nov 10, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter. Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <[email protected]>
rexut
added a commit
that referenced
this issue
Nov 10, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter. Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <[email protected]>
rexut
added a commit
that referenced
this issue
Nov 14, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter. Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <[email protected]>
rexut
added a commit
that referenced
this issue
Nov 14, 2024
Add statement about the copy-and-own of Sphinx extension warnings_filter. Add GitHub issues #270, #271 and #272. Signed-off-by: Stephan Linz <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Zephyr upstream has now it's own PCA9554 and PCA9555 driver.
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
Remove the Bridle driver and replace usage by Zephyr upstream driver or if not applicable then rename the Bridle driver.
Procedure
Since zephyrproject-rtos/zephyr@5253eb1 Zephyr upstream presents the original drivers by NXP Semiconductors, but without the reset register to defaults feature. Therefore Bridle will keep its own drivers, but from now on with the suffix
-regrst
to the DTS compatibility string.nxp,pca9554
tonxp,pca9554-regrst
.nxp,pca9555
tonxp,pca9555-regrst
.The text was updated successfully, but these errors were encountered: