From patchwork Mon Jun 12 14:13:59 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Georgi Djakov X-Patchwork-Id: 9781169 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id C080260352 for ; Mon, 12 Jun 2017 14:15:14 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id BE94226E4F for ; Mon, 12 Jun 2017 14:15:14 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B358827D4A; Mon, 12 Jun 2017 14:15:14 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 5460826E4F for ; Mon, 12 Jun 2017 14:15:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752532AbdFLOPM (ORCPT ); Mon, 12 Jun 2017 10:15:12 -0400 Received: from mail-wr0-f170.google.com ([209.85.128.170]:34604 "EHLO mail-wr0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752319AbdFLOOK (ORCPT ); Mon, 12 Jun 2017 10:14:10 -0400 Received: by mail-wr0-f170.google.com with SMTP id g76so97693480wrd.1 for ; Mon, 12 Jun 2017 07:14:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=rY8s3532ufsD/QZ9NHY3Glb0s09VglHhB9TSrvqyMRM=; b=dlrnLlDqsUZ9FyKtHxC422LtrqxQ7y9byrUPIcHjqjvoXOJMVMFa871DIfJQb30SRe hDrtmZtwjrRCOQ8bP4NCspPQguM6UTrjnBKViI9XuQojTl7JqFeFzmElxHgtozlziKBx 5iYLW1oqFGcnRBK3+ePG/uKqztQ3zpnb8xd9s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=rY8s3532ufsD/QZ9NHY3Glb0s09VglHhB9TSrvqyMRM=; b=pxanD23qNkovNL9RMcjfGJ6W9AymdDlYi0fju0ogCLuddi/1svcG1h3n3lc3nV3rXg FtK5tHcK7HxF396HvAQ9mxb4UeITJMJ3McxQ170zN4xL/ul9pYh86joo083fdWTZll1/ b0tRv6GWXa9KaBRsu+cZYEVqMHAxwrkMxfvJLElxZFHKP9ExzTsCFUpb/1cGF3i2M9jE 3zqlv2gk4gGozI6haCHbFluiV0jrSgx2PuErsnvWuudD3Kg6UhF2CFd+qalGv1fAJZbG I2VqTns1gieNZ1nXTKi1FGSIksnCGfFmHS830hi5DopB5/yZUSuvOIz0HMKKJWvexNu8 oRow== X-Gm-Message-State: AKS2vOx/BOj0rlT0VwGjzCDZHb4CzuFq7WPHvKUFBYtRAw5aWRrLFD5u oS//TipjsQmNEoNlOIgV4Q== X-Received: by 10.223.155.214 with SMTP id e22mr7302307wrc.33.1497276848382; Mon, 12 Jun 2017 07:14:08 -0700 (PDT) Received: from mms-0441.qualcomm.mm-sol.com ([212.45.67.2]) by smtp.googlemail.com with ESMTPSA id q77sm265383wmb.4.2017.06.12.07.14.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 12 Jun 2017 07:14:07 -0700 (PDT) From: Georgi Djakov To: linux-pm@vger.kernel.org, rjw@rjwysocki.net Cc: robh+dt@kernel.org, khilman@baylibre.com, mturquette@baylibre.com, gregkh@linuxfoundation.org, vincent.guittot@linaro.org, skannan@codeaurora.org, sboyd@codeaurora.org, andy.gross@linaro.org, seansw@qti.qualcomm.com, davidai@quicinc.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [RFC v2 3/3] dt-binding: Interconnect device-tree bindings draft Date: Mon, 12 Jun 2017 17:13:59 +0300 Message-Id: <20170612141359.26117-4-georgi.djakov@linaro.org> X-Mailer: git-send-email 2.13.0 In-Reply-To: <20170612141359.26117-1-georgi.djakov@linaro.org> References: <20170612141359.26117-1-georgi.djakov@linaro.org> Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP The interconnect API is not yet using DT bindings for expressing the relations between the API consumers and providers. This is posted a separate patch as it needs further discussions on how to represent this with DT. Signed-off-by: Georgi Djakov --- .../bindings/interconnect/interconnect.txt | 75 ++++++++++++++++++++++ 1 file changed, 75 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..e38a29db981e --- /dev/null +++ b/Documentation/devicetree/bindings/interconnect/interconnect.txt @@ -0,0 +1,75 @@ +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 usecase. 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 vendor specific compatible + string +- reg : register space of the interconnect controller hardware +- #interconnect-cells : number of cells in a interconnect specifier needed to + encode the interconnect node id. + +Example: + + snoc: snoc@0580000 { + compatible = "qcom,msm-bus-snoc"; + reg = <0x580000 0x14000>; + #interconnect-cells = <1>; + clock-names = "bus_clk", "bus_a_clk"; + clocks = <&rpmcc RPM_SMD_SNOC_CLK>, <&rpmcc RPM_SMD_SNOC_A_CLK>; + status = "okay"; + }; + bimc: bimc@0400000 { + compatible = "qcom,msm-bus-bimc"; + reg = <0x400000 0x62000>; + #interconnect-cells = <1>; + clock-names = "bus_clk", "bus_a_clk"; + clocks = <&rpmcc RPM_SMD_BIMC_CLK>, <&rpmcc RPM_SMD_BIMC_A_CLK>; + status = "okay"; + }; + pnoc: pnoc@500000 { + compatible = "qcom,msm-bus-pnoc"; + reg = <0x500000 0x11000>; + #interconnect-cells = <1>; + clock-names = "bus_clk", "bus_a_clk"; + clocks = <&rpmcc RPM_SMD_PCNOC_CLK>, <&rpmcc RPM_SMD_PCNOC_A_CLK>; + status = "okay"; + }; + += interconnect consumers = + +The interconnect consumers are device nodes which consume the interconnect +path(s) provided by the interconnect provider. There can be multiple +interconnect providers on a SoC and the consumer may consume multiple paths +from different providers depending on usecase and the components it has to +interact with. + +Required-properties: +interconnect-src : A phandle and interconnect provider specifier as defined by + bindings of the interconnect provider specified by phandle. + This denotes the source device port which will be used, as the + device may have multiple master ports. +interconnect-dst : A phandle and internet provider specifier pointing to the + local port of the target device. + +Example: + + sdhci@07864000 { + ... + interconnect-src = <&pnoc MAS_PNOC_SDCC_2>; + interconnect-dst = <&pnoc SLV_BLSP_1>; + };