RFC: Introduce Zephyr Driver Support for Peripheral Sensor Interface (PSI5) Protocol #83982
Labels
Architecture Review
Discussion in the Architecture WG required
RFC
Request For Comments: want input from the community
Introduction
This RFC proposes the introduction of a Zephyr driver to support the PSI5 protocol, enhancing the capabilities of the Zephyr RTOS for automotive sensor applications (https://en.wikipedia.org/wiki/Peripheral_Sensor_Interface_5).
Technical document reference: https://www.psi5.org/fileadmin/user_upload/psi5/Specification/V1.3/psi5_specification_v13_080729.pdf
Problem description
The PSI5 protocol is widely used in automotive applications for sensor communication. Adding support for PSI5 in Zephyr will enable developers to integrate automotive sensors more efficiently, leveraging Zephyr’s real-time capabilities.
Proposed change
Introduce new Zephyr driver support for PSI5 protocol: PR #79824.
Detailed RFC
Proposed change (Detailed)
Driver Architecture:
• The driver will be implemented as a new driver Zephyr.
• The driver will include support for PSI5 communication, including initialization, data transmission, and error handling.
• The driver will support both PSI5 transmitters and receivers.
Configuration:
• The driver will be configurable via Kconfig options.
• Device Tree bindings will be provided to specify hardware configurations.
APIs Design:
• sample
samples/boards/nxp/s32/psi5
will validate the driver’s functionality and show how to use the driver.Dependencies
Hardware: New components are required to interface with PSI5 sensors
Concerns and Unresolved Questions
Alternatives
Adding support for PSI5 in Zephyr will significantly benefit automotive applications, providing a robust and real-time solution for sensor communication.
The text was updated successfully, but these errors were encountered: