From 0c7325e3ef955af08321fa2a561a5132525da834 Mon Sep 17 00:00:00 2001 From: Declan Snyder Date: Fri, 22 Mar 2024 17:41:18 -0500 Subject: [PATCH] doc: board_porting: Update hierarchy presentation Update the presentation of the hardware hierarchy description so that it does not appear to have missing words at the end of the bullet points, by using a paragraph instead. And tweak the wording slightly. Signed-off-by: Declan Snyder --- doc/hardware/porting/board_porting.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/doc/hardware/porting/board_porting.rst b/doc/hardware/porting/board_porting.rst index 0008ef91340..d7ff4569524 100644 --- a/doc/hardware/porting/board_porting.rst +++ b/doc/hardware/porting/board_porting.rst @@ -70,16 +70,10 @@ complete conversion reference. Hardware support hierarchy ************************** -Zephyr's hardware support hierarchy has the following levels, from most to least -specific: - -- :term:`board`, which has one or more -- :term:`SoC`, each of which optionally belong to a -- :term:`SoC series`, which in turn may optionally belong to an -- :term:`SoC family`. Each SoC has one or more -- :term:`CPU cluster`, each containing one or more -- :term:`CPU core`, of a particular -- :term:`architecture` +Zephyr's hardware support is based on a series of hierarchical abstractions. +Primarily, each :term:`board` has one or more :term:`SoC`. +Each SoC can be optionally classed into an :term:`SoC series`, which in turn may optionally belong to an :term:`SoC family`. +Each SoC has one or more :term:`CPU cluster`, each containing one or more :term:`CPU core` of a particular :term:`architecture`. You can visualize the hierarchy in the diagram below: