Signed-off-by: Stefano Stabellini stefano.stabellini@xilinx.com --- source/device-bindings.rst | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+)
diff --git a/source/device-bindings.rst b/source/device-bindings.rst index 5cdee09..f3df006 100644 --- a/source/device-bindings.rst +++ b/source/device-bindings.rst @@ -436,3 +436,30 @@ represented as a node with a compatible value of "simple-bus". ranges). Usage legend: R=Required, O=Optional, OR=Optional but Recommended, SD=See Definition ==================================================================================================== + + +.. _sect-bindings-indirect-bus: + +``indirect-bus`` Compatible Value +--------------------------------- + +``indirect-bus`` specifies a type of bus that can be accessed directly +without additional configuration required. However, it does not +automatically map to the parent address space. As a consequence, CPUs +represented by cpu nodes either under ``/cpus`` or under a +"cpus,cluster" compatible node will not have a mapping of it, unless +they also have an ``address-map`` property mapping it. In fact, +``address-map`` can be used to specify a mapping of an ``indirect-bus`` +into the address space of the cluster, see section +:ref:`sect-address-map` for a complete description of the property. + + +.. tabularcolumns:: | p{4cm} p{0.75cm} p{4cm} p{6.5cm} | +.. table:: ``indirect-bus`` Compatible Node Properties + + ======================== ===== ===================== =============================================== + Property Name Usage Value Type Definition + ======================== ===== ===================== =============================================== + ``compatible`` R ``<string>`` Value shall include "indirect-bus". + Usage legend: R=Required, O=Optional, OR=Optional but Recommended, SD=See Definition + ====================================================================================================