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@6b11d19	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.

[JarmouniA]

A test is needed as well, samples are not a replacement for tests.

[JarmouniA]

DeviceTree binding for

[congnguyenhuu]

I updated

[rruuaanng]

@congnguyenhuu They are redundant and do not need to be prefixed. Putting them in dts/bindings already indicates that they are a binding. E.g. other bindings description.

Renesas RA ADC node

Static Battery Characteristics

Description of pre-defined file systems.

ADI MAX32 compatible Counter RTC

PL330 DMA Controller

[congnguyenhuu]

I updated

[JarmouniA]

Since this is a vendor-agnostic API, I don't see why this sample is placed in the NXP folder.

[rruuaanng]

Because this is the smallest sample it provides that can run, I guess its prototype is developed based on nxp soc.

[JarmouniA]

Except the device node name (added a comment about it below), I don't see anything vendor-specific in the sample's code, that would justify placing it in the vendor's folder.

[congnguyenhuu]

I moved this sample to a generic driver sample.
And also created a test API driver .

[JarmouniA]

A vendor-agnostic alias, that will be defined in board overlay, should be used here, instead of the IP DT node name.

[congnguyenhuu]

I updated

[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