Add Zephyr module metadata

[wearyzen]

Add zephyr/module.yml to allow CMSIS_6 to be consumed as a Zephyr module.

This enables Zephyr to use CMSIS_6 directly from upstream without requiring downstream changes in this repository, allowing straightforward synchronization with future updates (e.g. via standard GitHub fork sync workflows).

Use external CMake and Kconfig integration so that all Zephyr-specific build logic remains in the Zephyr repository. This keeps CMSIS_6 independent of any particular build system and preserves portability for non-Zephyr users.

The change is minimal and does not affect existing CMSIS_6 users or workflows.

For more details on Zephyr modules, see:
https://docs.zephyrproject.org/latest/develop/modules.html

[christophe0606]

Wouldn't it be better if the KConfig and CMakeLists.txt were inside the zephyr folder ?

With the current zephyr folder, one can use this repo directly as a module but it would still rely on the cmake and kconfig inside Zephyr that may not be up to date with the latest version of this repository.

[wearyzen]

Wouldn't it be better if the KConfig and CMakeLists.txt were inside the zephyr folder ?

With the current zephyr folder, one can use this repo directly as a module but it would still rely on the cmake and kconfig inside Zephyr that may not be up to date with the latest version of this repository.

Hi @christophe0606 ,
IIUC, just adding a CMakeLists.txt under zephyr/ isn’t enough. Zephyr’s module system expects a top-level CMakeLists.txt (or equivalent module entry) to include that directory, so this change alone wouldn’t make the module self-contained. Users would still need a compatible Zephyr version anyway, so it likely doesn’t help much on its own.

Thanks.