dt-bindings: interconnect: Document the support of optional path tag

Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT property. This info

dt-bindings: interconnect: Document the support of optional path tag

Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT property. This information would be
populated when the xlate_extended() callback is used.

Specifying the tag in DT will allow the interconnect framework to do the
aggregation based on the tag automatically. The users can still use the
icc_set_tag() API if/when needed.

Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20200903133134.17201-3-georgi.djakov@linaro.org
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>

show more ...

dt-bindings: interconnect: Add a dma interconnect name

The current DT bindings assume that the DMA will be performed by the
devices through their parent DT node, and rely on that assumption for the

dt-bindings: interconnect: Add a dma interconnect name

The current DT bindings assume that the DMA will be performed by the
devices through their parent DT node, and rely on that assumption for the
address translation using dma-ranges.

However, some SoCs have devices that will perform DMA through another bus,
with separate address translation rules. We therefore need to express that
relationship, through the special interconnect name "dma-mem".

Acked-by: Georgi Djakov <georgi.djakov@linaro.org>
Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Rob Herring <robh@kernel.org>

show more ...

dt-bindings: Introduce interconnect binding

This binding is intended to represent the relations between interconnect
controllers (providers) and consumer device nodes. It will allow creating
links b

dt-bindings: Introduce interconnect binding

This binding is intended to represent the relations between interconnect
controllers (providers) and consumer device nodes. It will allow creating
links between consumers and interconnect paths (exposed by interconnect
providers).

Reviewed-by: Evan Green <evgreen@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

show more ...

dt-bindings: interconnect: Document the support of optional path tag

Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT propert

dt-bindings: interconnect: Document the support of optional path tag

Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT property. This information would be
populated when the xlate_extended() callback is used.

Specifying the tag in DT will allow the interconnect framework to do the
aggregation based on the tag automatically. The users can still use the
icc_set_tag() API if/when needed.

Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20200903133134.17201-3-georgi.djakov@linaro.org
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>

show more ...

dt-bindings: interconnect: Add a dma interconnect name

The current DT bindings assume that the DMA will be performed by the
devices through their parent DT node, and rely on that assumpt

dt-bindings: interconnect: Add a dma interconnect name

The current DT bindings assume that the DMA will be performed by the
devices through their parent DT node, and rely on that assumption for the
address translation using dma-ranges.

However, some SoCs have devices that will perform DMA through another bus,
with separate address translation rules. We therefore need to express that
relationship, through the special interconnect name "dma-mem".

Acked-by: Georgi Djakov <georgi.djakov@linaro.org>
Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Rob Herring <robh@kernel.org>

show more ...

dt-bindings: Introduce interconnect binding

This binding is intended to represent the relations between interconnect
controllers (providers) and consumer device nodes. It will allow crea

dt-bindings: Introduce interconnect binding

This binding is intended to represent the relations between interconnect
controllers (providers) and consumer device nodes. It will allow creating
links between consumers and interconnect paths (exposed by interconnect
providers).

Reviewed-by: Evan Green <evgreen@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

show more ...