NXP S32 introduce support PSI5

[congnguyenhuu]

Introduce support Peripheral Sensor Interface (PSI5) driver on S32Z. This driver allows to communication (send, receive) with PSI5 device.
The test result: PSI5-TESTING-RESULT.pptx

RFC: #83982

[zephyrbot]

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

Name	Old Revision	New Revision	Diff
hal_nxp	zephyrproject-rtos/hal_nxp@d0e49d6	zephyrproject-rtos/hal_nxp#451	zephyrproject-rtos/hal_nxp#451/files

⛔ DNM label due to: 1 project with PR revision

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

[congnguyenhuu]

Based on the suggestions from the Architecture WG meeting on March 4th, I have updated to the v1 changes. These updates include:

1. Changed add_rx_callback(dev, channel, serial_cb, data_cb, user_data) to
   register_callback(dev, channel, struct psi5_rx_callback_configs callback_configs)

With the newly defined structure for RX callback configurations in psi5.h

struct psi5_rx_callback_config {
	psi5_rx_frame_callback_t callback;
	struct psi5_frame *frame;
	uint32_t max_num_frame;
	void *user_data;
};
 
struct psi5_rx_callback_configs {
	struct psi5_rx_callback_config *serial_frame;
	struct psi5_rx_callback_config *data_frame;
};

2. RX buffers are allocated by the user to improve throughput:

• Use the API register_callback to register the RX callback and allocate a user-defined RX buffer for each callback.
• Count the number of RX buffer frames and trigger the RX callback when the count reaches the maximum buffer frame limit.
• Reset the count when a RX error occurs or when the count reaches the maximum buffer frame limit.

3. Tests and samples have been updated to demonstrate usage with the new changes

[congnguyenhuu]

New update as Dat's suggestion for PR

New updated PSI5 frame type, separate 2 type serial format 4 bit ID and 8 bit ID

enum psi5_frame_type {
	PSI5_SERIAL_FRAME_4_BIT_ID,
	PSI5_SERIAL_FRAME_8_BIT_ID,
	PSI5_DATA_FRAME
};

New updated PSI5 status, uses the common status RX frame and RX error all type frames

enum psi5_status {
	PSI5_TX_DONE,
	PSI5_TX_ERR,
	PSI5_RX_FRAME,
	PSI5_RX_ERR,
};

[congnguyenhuu]

I have updated to the v2 changes as the suggestion for SENT.
I removed the enum psi5_status.
Tx callback still report the status with changed type to int, status = 0 means tx done else tx error.
Rx callback just report the num_frame, An error frame is received (number received frames != expected amount), only report non-error frame.

[manuargue]

hi @carlescufi , @henrikbrixandersen . Can we remove the arch review label or is there anything else to discuss? Thanks

[sonarqubecloud]

Quality Gate passed

Issues
0 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