SPDX-License-Identifier: Apache-2.0
-
4. Device Driver Abstraction UID: ZEP-SYRS-4 STATUS: Draft TYPE: Functional COMPONENT: Device Drivers RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework for managing device drivers and peripherals.
USER_STORY: As a Zephyr RTOS user I want my application to be portable between different MCU architectures (ARM Cortex-M/A, Intel x86, RISCV etc.) and MCU vendors (STM, NXP, Intel, etc.) without having to change the MCU peripherals access.
The Zephyr RTOS shall provide abstraction of device drivers with common functionalities as an intermediate interface between applications and device drivers, where such interface is implemented by individual device drivers.
Proposal for replacement: Zephyr shall provide an interface between application and individual device drivers to provide an abstraction of device drivers with common functionalities.
-
4. Device Driver Abstraction UID: ZEP-SYRS-4 STATUS: Draft TYPE: Functional COMPONENT: Device Drivers RELATIONS (Child): STATEMENT: The Zephyr RTOS shall provide a framework for managing device drivers and peripherals.
USER_STORY: As a Zephyr RTOS user I want my application to be portable between different MCU architectures (ARM Cortex-M/A, Intel x86, RISCV etc.) and MCU vendors (STM, NXP, Intel, etc.) without having to change the MCU peripherals access.
The Zephyr RTOS shall provide an interface for managing a defined set of hardware exceptions (including interrupts) across all systems.
As a Zephyr RTOS user I want hardware exceptions (hardware failures, programming mistakes) to be handled gracefully (no program crashes as far as possible).