drivers: sensor: wsen_pdms_25131308XXX05: add sensor driver

[wm-eisos]

Add wsen_pdms_25131308XXX05 driver.

@mah-eiSmart

[github-actions]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_wurthelektronik	zephyrproject-rtos/hal_wurthelektronik@e3e2797	zephyrproject-rtos/hal_wurthelektronik@7c1297e (zephyr)	zephyrproject-rtos/[email protected]

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[wm-eisos]

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

[kartben]

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

Some of the issues are yours, I think, now that I re-ran the CI on top of main where the BT issue has been fixed:)

[Copilot]

Pull Request Overview

This PR adds a new sensor driver for the Würth Elektronik WSEN-PDMS-25131308XXX05 differential pressure sensor, supporting both I2C and SPI interfaces with optional CRC functionality.

• Adds complete driver implementation with initialization, sampling, and channel reading functions
• Supports multiple sensor variants with different pressure ranges through device tree configuration
• Updates HAL module revision and includes necessary device tree bindings and build configurations

Reviewed Changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
west.yml	Updates hal_wurthelektronik revision to include new sensor support
tests/drivers/build_all/sensor/i2c.dtsi	Adds test device tree entry for build verification
dts/bindings/sensor/we,wsen-pdms-25131308XXX05-*.yaml	Device tree binding files for I2C, SPI, and common properties
drivers/sensor/wsen/wsen_pdms_25131308XXX05/*	Complete driver implementation with header, source, Kconfig, and CMakeLists
drivers/sensor/wsen/wsen_*/*.h	Updates header includes to use new HAL structure
drivers/sensor/wsen/{Kconfig,CMakeLists.txt}	Integrates new driver into build system

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[wm-eisos]

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

Some of the issues are yours, I think, now that I re-ran the CI on top of main where the BT issue has been fixed:)

im not sure the test that just failed was regarding a bash script which couldnt run. unless im messing something if yes do you mind pointing it out.

I will check the review from copilot now.

[kartben]

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

Some of the issues are yours, I think, now that I re-ran the CI on top of main where the BT issue has been fixed:)

im not sure the test that just failed was regarding a bash script which couldnt run. unless im messing something if yes do you mind pointing it out.

I will check the review from copilot now.

...

devicetree error: 'sensor-type' is marked as required in 'properties:' in /__w/zephyr/zephyr/dts/bindings/sensor/we,wsen-pdms-25131308XXX05-i2c.yaml, but does not appear in <Node /test/i2c@11112222/wsen_pdms_25131308XXX05@bc in /__w/zephyr/zephyr/tests/drivers/build_all/sensor/i2c.dtsi:1409>
CMake Error at /__w/zephyr/zephyr/cmake/modules/dts.cmake:306 (execute_process):
  execute_process failed command indexes:

...

[wm-eisos]

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

Some of the issues are yours, I think, now that I re-ran the CI on top of main where the BT issue has been fixed:)

im not sure the test that just failed was regarding a bash script which couldnt run. unless im messing something if yes do you mind pointing it out.

I will check the review from copilot now.

@kartben the tests are failing due to some issues in bluetooth. Can you please check it out ?

Some of the issues are yours, I think, now that I re-ran the CI on top of main where the BT issue has been fixed:)

im not sure the test that just failed was regarding a bash script which couldnt run. unless im messing something if yes do you mind pointing it out.
I will check the review from copilot now.

...

devicetree error: 'sensor-type' is marked as required in 'properties:' in /__w/zephyr/zephyr/dts/bindings/sensor/we,wsen-pdms-25131308XXX05-i2c.yaml, but does not appear in <Node /test/i2c@11112222/wsen_pdms_25131308XXX05@bc in /__w/zephyr/zephyr/tests/drivers/build_all/sensor/i2c.dtsi:1409>
CMake Error at /__w/zephyr/zephyr/cmake/modules/dts.cmake:306 (execute_process):
  execute_process failed command indexes:

...

perfect thank you very much

[MaureenHelm]

Needs to be rebased, but otherwise LGTM

[wm-eisos]

@MaureenHelm @kartben ready to be merged

[wm-eisos]

@MaureenHelm @kartben needs another approval because of the i2c test conflict. Is there a way we can resolve the issue with this should i start using the last I2C address+5 or should i keep them contiguous?

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[MaureenHelm]

@MaureenHelm @kartben needs another approval because of the i2c test conflict. Is there a way we can resolve the issue with this should i start using the last I2C address+5 or should i keep them contiguous?

No, please don't do that. It might help for one PR, but if everyone starts doing that then we'll just shift the address conflict by 5. I've thought about trying to extract the nodes into separate buses for each vendor, but haven't gotten around to doing it and you're welcome to take a stab at it if you like.