tiacsys / bridle

Bridle and kite line for embedded systems based on Zephyr.
https://bridle.tiac-systems.net
Apache License 2.0
15 stars 3 forks source link

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

Closed rexut closed 1 hour ago

rexut commented 1 week ago

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):

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@5253eb1692500fb7aa01f47b454742023699f034 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.