zephyr: ra4m1: integrate FSP critical sections with irq_lock

[soburi]

Summary

• include the FSP exception and device headers in soc.h so CMSIS types/macros exist before Zephyr's CMSIS validation runs, priming the RA4M1 core constants for the first include pass
• override the FSP critical section macros to call Zephyr irq_lock/irq_unlock so vendor drivers share the kernel's locking semantics

Testing

• cmake -Bbuild -S samples/hello_world -DBOARD=ek_ra4m1
• cmake --build build

---

https://chatgpt.com/codex/tasks/task_e_68e1e24257ac8322ac3acd8eb5ec8291

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback

[chatgpt-codex-connector]

Override FSP critical macros before including vendor headers

The Zephyr wrappers for FSP_CRITICAL_SECTION_* are defined only after bsp_api.h has been included. Inline helpers in the FSP headers (for example R_BSP_PinAccessEnable in bsp_io.h) expand these macros while the vendor defaults are still in force, so those helpers continue to manipulate PRIMASK/Basepri directly and never use irq_lock. This leaves most FSP code with its original interrupt semantics despite the change. Move the override ahead of the bsp_api.h inclusion so all inline functions pick up the Zephyr-aware macros.

Useful? React with 👍 / 👎.