Skip to content
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

Closed
2 tasks done
rexut opened this issue Nov 7, 2024 · 0 comments · Fixed by #273
Closed
2 tasks done

[BUG] build all GPIO drivers test runs into devicetree error #271

rexut opened this issue Nov 7, 2024 · 0 comments · Fixed by #273
Assignees
Labels
bug Something isn't working
Milestone

Comments

@rexut
Copy link
Member

rexut commented Nov 7, 2024

Describe the bug
Zephyr upstream has now it's own PCA9554 and PCA9555 driver.

To Reproduce
Steps to reproduce the behavior:

  1. proper Bridle workspace setup from main branch
  2. west twister \
           --jobs 4 \
           --verbose \
           --inline-logs \
           --integration \
           --alt-config-root bridle/zephyr/alt-config/tests/drivers/build_all/gpio \
           --testsuite-root zephyr/tests/drivers/build_all/gpio \
           --tag bridle \
           --tag zephyr
    
  3. See error below…

Expected behavior
Test suite runs properly without any error.

Impact
Showstopper, because the CI pipeline will fail.

Logs and console output

devicetree error: both .../bridle/dts/bindings/gpio/nxp,pca9554.yaml
                   and ../zephyr/dts/bindings/gpio/nxp,pca9554.yaml
                  have 'compatible: nxp,pca9554' and 'on-bus: i2c'

Screenshots
None.

Development Environment (please complete the following information):

  • OS: Linux
  • Toolchain: West v1.3.0, CMake v3.28.1, Sphinx v8.1.3, Doxygen v1.9.8
  • Branch: main, Zephyr v4.0.0-rc2 (upstream main)

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.

  • PCA9554: Rename DTS binding from nxp,pca9554 to nxp,pca9554-regrst.
  • PCA9555: Rename DTS binding from nxp,pca9555 to nxp,pca9555-regrst.
@rexut rexut added the bug Something isn't working label Nov 7, 2024
@rexut rexut self-assigned this Nov 7, 2024
@rexut rexut modified the milestones: v4.0.0, v3.7.99 Nov 7, 2024
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 rexut modified the milestones: v3.7.99, v4.0.0 Nov 18, 2024
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
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant