diff options
| author | Pierre Gondois <pierre.gondois@arm.com> | 2026-06-09 09:58:51 +0300 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2026-09-11 12:05:39 +0300 |
| commit | 767340edee7a48cc45b8f98384b0686d590ad3d5 (patch) | |
| tree | 85df6405ce20194633a037e121230da40b0df50f /BaseTools/Source/Python/Workspace/MetaFileCommentParser.py | |
| parent | 66d3983c387d679cc44dc70033304a67ecd3a5ec (diff) | |
| download | edk2-767340edee7a48cc45b8f98384b0686d590ad3d5.tar.xz | |
DynamicTablesPkg/HwInfoParser: Split FdtGetIntcParentNode()
The Devicetree Specification [1] defines the concept of interrupt
mapping, interrupt domain, interrupt nexus and interrupt controller.
The "interrupt-controller" property defines a node as an interrupt
controller. The "interrupt-map" property defines a node as an
interrupt nexus. Both node types are defined as the root of an
interrupt domain.
A GIC (Generic Interrupt Controller) is an interrupt controller. The
GIC version should be fetched to the matching device tree node. A
node defining an interrupt domain might not necessarily be an
interrupt controller and contain this information.
Introduce 2 functions:
- FdtGetIntControllerNode()
- FdtGetIntDomainNode()`
to distinguish the 2 concepts.
As the presence of interrupt nexus/domains is currently not supported,
replace FdtGetIntcParentNode() calls with FdtGetIntControllerNode().
The distinction will be useful in following patches.
Also, update the detection of an interrupt domain to the presence
of one of these properties:
- interrupt-controller
- interrupt-map
instead of relying on the presence of the #interrupt-cells property,
which is not a guarantee.
[1] Spec. v0.4, s2.4 Interrupts and Interrupt Mapping
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/MetaFileCommentParser.py')
0 files changed, 0 insertions, 0 deletions
