drivers: misc: ethos_u: Create the ethos_u_common for every vendor

[khoa-nguyen-18]

Some vendors require custom procedures to be executed before and after calling the ethosu_init and ethosu_irq_handler APIs from the Ethos-U core driver.

As a solution, I propose separating ethos_u_common for each vendor and ethos_u_arm for specific Arm boards, enabling vendors to self-configure the initialization flow and IRQ handler.

Building sample samples/modules/tflite-micro/tflm_ethosu log:

[307/307] Linking CXX executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       74232 B       512 KB     14.16%
             RAM:       23000 B       512 KB      4.39%
            ITCM:          0 GB       512 KB      0.00%
            SRAM:          0 GB         1 MB      0.00%
            DTCM:          0 GB       512 KB      0.00%
           ISRAM:          0 GB         2 MB      0.00%
 NULL_PTR_DETECT:          0 GB         1 KB      0.00%
            DDR4:      127270 B       256 MB      0.05%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /home/khoanguyen18/zephyrproject/zephyr/build/zephyr/zephyr.elf for board: mps3

[ccli8]

It can support other vendor's ethos-u npu.

[wearyzen]

Some vendors require custom procedures to be executed before and after calling the ethosu_init and ethosu_irq_handler APIs from the Ethos-U core driver.

Could you provide more details on what the custom procedures are? maybe this is something that can be done in one of the CONFIG_SOC_*_HOOK

[khoa-nguyen-18]

Some vendors require custom procedures to be executed before and after calling the ethosu_init and ethosu_irq_handler APIs from the Ethos-U core driver.

Could you provide more details on what the custom procedures are? maybe this is something that can be done in one of the CONFIG_SOC_*_HOOK

From our Renesas MCU side, we need to clear the HW frag when the interrupt is raised, and it definitely can't be cleared in the CONFIG_SOC_*_HOOK. For other vendors, I see they have vendor-specific procedures, such as configuring the clock, enabling power to the module, or resetting the module.

Therefore, I propose this PR to clarify the init function and allow modifying the handler to clear the NPU flag for each vendor, rather than simply covering it within soc_hook_init.

[ccli8]

It helps for other vendors to add their ethos-u driver.

[wearyzen]

ok I understand the reason for the change. Added a few comments to see if we can have a cleaner solution for this.

[dkalowsk]

@khoa-nguyen-18 just a reminder that the feature freeze for 4.2 is rapidly approaching (end of the week) and if this is needed in for 4.2 you'll need to get the reviews from the maintainers.

[ccli8]

Try to rebase #88941 on this reorg, and that's fine.

[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