Port — Requirements
Normative
Defines what a conformant Port driver MUST do. Keywords per Requirement Keywords; conformance per Conformance. Requirements do not carry individual status — the set-level status applies to all of them. Signatures, error codes, and configuration properties are in the API Reference, Errors, and Configuration Reference pages. Cross-module rules (types, error model, naming, memory mapping) are in General.
Mandatory (MUST) - 13 Requirements
The conformance contract — an implementation MUST satisfy every requirement here.
CHI-PORT-MUST-01 — State machine
|
After reset the driver MUST be in |
CHI-PORT-MUST-02 — Initialization
|
|
CHI-PORT-MUST-03 — Read pin and port values
|
|
CHI-PORT-MUST-04 — Direction semantics of access APIs
|
The Get APIs MUST work for both input and output pins. The behavior of a Set API on an input pin is implementation-defined and MUST NOT be relied upon by portable callers. |
CHI-PORT-MUST-05 — Write and toggle pins
|
|
CHI-PORT-MUST-06 — Masked port write
|
|
CHI-PORT-MUST-07 — Edge-detection configuration
|
|
CHI-PORT-MUST-08 — Edge event notification
|
On a configured pin edge the driver MUST call |
CHI-PORT-MUST-09 — Poll function
|
|
CHI-PORT-MUST-10 — Port and pin id symbols
|
A pin id MUST be a |
CHI-PORT-MUST-11 — Development error detection
|
When development error reporting is enabled, each API MUST detect the conditions listed in
Errors and report them via |
CHI-PORT-MUST-12 — Public types and error identifiers
|
The driver MUST provide |
CHI-PORT-MUST-13 — Configuration model
|
The driver MUST support the configuration model in Configuration Reference — a
|
Recommended (SHOULD) - 1 Requirement
CHI-PORT-SHOULD-01 — Simultaneous masked update
|
Where the hardware imposes no limitation, |