From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2BDCC282CD for ; Mon, 28 Jan 2019 14:23:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CF221214DA for ; Mon, 28 Jan 2019 14:23:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726980AbfA1OXt (ORCPT ); Mon, 28 Jan 2019 09:23:49 -0500 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:59403 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726735AbfA1OXr (ORCPT ); Mon, 28 Jan 2019 09:23:47 -0500 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0SELTnn011304; Mon, 28 Jan 2019 15:23:31 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2q8famd3m7-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Jan 2019 15:23:31 +0100 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 5BF9841; Mon, 28 Jan 2019 14:23:30 +0000 (GMT) Received: from Webmail-eu.st.com (Safex1hubcas21.st.com [10.75.90.44]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 33BAA2D37; Mon, 28 Jan 2019 14:23:30 +0000 (GMT) Received: from SAFEX1HUBCAS24.st.com (10.75.90.95) by SAFEX1HUBCAS21.st.com (10.75.90.44) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 28 Jan 2019 15:23:29 +0100 Received: from localhost (10.201.20.122) by webmail-ga.st.com (10.75.90.48) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 28 Jan 2019 15:23:28 +0100 From: Benjamin Gaignard To: , , , , , CC: , , , , , , Benjamin Gaignard Subject: [RFC v2 1/7] devicetree: bindings: Document domains controller bindings Date: Mon, 28 Jan 2019 15:23:07 +0100 Message-ID: <20190128142313.17036-2-benjamin.gaignard@st.com> X-Mailer: git-send-email 2.15.0 In-Reply-To: <20190128142313.17036-1-benjamin.gaignard@st.com> References: <20190128142313.17036-1-benjamin.gaignard@st.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.201.20.122] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-28_08:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Document commons domains controller bindings for controller and client devices. Signed-off-by: Benjamin Gaignard --- version 2: - complete rework of bindings description to try to give a better definition of what bus domains could be. .../bindings/bus/domains/domainsctrl.txt | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 Documentation/devicetree/bindings/bus/domains/domainsctrl.txt diff --git a/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt b/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt new file mode 100644 index 000000000000..a3fced91842d --- /dev/null +++ b/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt @@ -0,0 +1,55 @@ +Common Domains Controller bindings properties + +Bus domains controllers allow to divided system on chip into multiple domains +that can be used to select by who hardware blocks could be accessed. +A domain could be a cluster of CPUs (or coprocessors), a range of addresses or +a group of hardware blocks. + +This device tree bindings can be used to bind bus domain consumer devices with +their bus domains provided by bus domains controllers. A bus domain provider +can be represented by any node in the device tree and can provide one or more +bus domains. A consumer node can refer to the provider by a phandle and a set +of phandle arguments of length specified by the #domainctrl-cells property in +the bus domain provider node. + +==Bus domain provider== + +Required properties: +- #domainctrl-cells : Number of cells in a bus domain specifier; + Can be any value as specified by device tree binding + documentation of a particular provider. + +==Bus domain consumer== + +Required properties: +- domainsctrl-X : A list of bus domain specifiers, as defined by + bindings of the bus domain controller that is the + bus domain provider. + +Optional properties: +- domainsctrl-names : A list of bus domain name string sorted in the same + order as the domainsctrl-X proprerties. Consumer + drivers will use domainsctrl-names to match bus + domains with bus domains specifiers. + Note that "default" and "unbind" are reserved names + used by the framework. + +Example of usage with: +- a domains controller with a 2 parameters cell +- a domains controller with a 3 parameters cell +- a client device node using the both controllers and 2 configurations + named "default" and "unbind" + +ctrl0: ctrl@0 { + #domainctrl-cells = <2>; +}; + +ctrl1: ctrl@1 { + #domainctrl-cells = <3>; +}; + +foo@0 { + domains-names = "default", "unbind"; + domainctrl-0 = <&ctrl0 1 2>, <&ctrl1 3 4 5>; + domainctrl-1 = <&ctrl0 6 7>, <&ctrl1 8 9 0>; +}; -- 2.15.0