lkml.org 
[lkml]   [2018]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v6 2/8] dt-bindings: Introduce interconnect provider bindings
    Date
    This binding is intended to represent the interconnect hardware present
    in some of the modern SoCs. Currently it consists only of a binding for
    the interconnect hardware devices (provider).

    Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
    ---
    .../bindings/interconnect/interconnect.txt | 33 +++++++++++++++++++
    1 file changed, 33 insertions(+)
    create mode 100644 Documentation/devicetree/bindings/interconnect/interconnect.txt

    diff --git a/Documentation/devicetree/bindings/interconnect/interconnect.txt b/Documentation/devicetree/bindings/interconnect/interconnect.txt
    new file mode 100644
    index 000000000000..6e2b2971b094
    --- /dev/null
    +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt
    @@ -0,0 +1,33 @@
    +Interconnect Provider Device Tree Bindings
    +=========================================
    +
    +The purpose of this document is to define a common set of generic interconnect
    +providers/consumers properties.
    +
    +
    += interconnect providers =
    +
    +The interconnect provider binding is intended to represent the interconnect
    +controllers in the system. Each provider registers a set of interconnect
    +nodes, which expose the interconnect related capabilities of the interconnect
    +to consumer drivers. These capabilities can be throughput, latency, priority
    +etc. The consumer drivers set constraints on interconnect path (or endpoints)
    +depending on the use case. Interconnect providers can also be interconnect
    +consumers, such as in the case where two network-on-chip fabrics interface
    +directly
    +
    +Required properties:
    +- compatible : contains the interconnect provider compatible string
    +- #interconnect-cells : number of cells in a interconnect specifier needed to
    + encode the interconnect node id
    +
    +Example:
    +
    + snoc: snoc@580000 {
    + compatible = "qcom,msm8916-snoc";
    + #interconnect-cells = <1>;
    + reg = <0x580000 0x14000>;
    + clock-names = "bus_clk", "bus_a_clk";
    + clocks = <&rpmcc RPM_SMD_SNOC_CLK>,
    + <&rpmcc RPM_SMD_SNOC_A_CLK>;
    + };
    \
     
     \ /
      Last update: 2018-07-09 17:56    [W:4.545 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site