Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp284964img; Mon, 18 Mar 2019 03:07:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqwBuD/CvwigShhExLseqE3UQFAZrGWYVWEoyaqH7RkvtFQaBTtiFt3fTsXMkgoKeKzanIUp X-Received: by 2002:a17:902:14b:: with SMTP id 69mr18782793plb.216.1552903666356; Mon, 18 Mar 2019 03:07:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552903666; cv=none; d=google.com; s=arc-20160816; b=s/mp5M9i1k8+gCxEWHgIgMJlT8wq/aIcOuJOPynDUPIjFzc9bYpc8KYBeMERlHtyjZ JvHhoXzWNNq/3PlW06iyazbkE8aezmjkCqsmiCYDzMYChc9J1omyMtuITRy5KNUOyvJT f1pom2YnO1NNNXs8/3dx81g42x+1wqw/YTzSyT4m+79wLsc/ED6aj0wWBQV34BZGSKJQ wBysN2fKWMiN4jnGTzwgOfRS0vQyvWuBTxXAFwKNZXKA8780k/D71zEtj/yqPEh4s9Xc uMjo2fAYnGhBYoId9SblYxHhZxjlDviPf9JR++w7ogVGFKnUrqEL+qMiYc665//Pox/L F5qA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=gLE1OBL3hXHSdIp1g8xW0K6AfvWVmLCR6aOw/Y/Pt2M=; b=wNkVVWZsirMUKhtX9Et+0G+fP0gg8SZOffi6cs3rGi9z2waMrR432/GJ+lFRdHncDL N+9c1XzvwunN2SgnDSVa34YKtZfnFryiCueGOG+AkGNy3P1dXVmC8I0orntkbIq+QNXq B9xV01wTZUcThw/bztEhDWeyn6KMbEiEYKcGKyiC7gK0Okm1ju4Y3FCFWV1KVEVAv805 tSP1BBUO63e6yaA1fSwF5tEq9yIOF4kNzwVvXMO7LboRY/rSlpn3E7u0+gnzJ8wHxL6W w0RWV0nzWd6L1bM0gIVp3ogiM92y2u6/4G3Crai7FllrXkKDZwd955WVWP/YILH0j+xr cZGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c26si6863055pfd.198.2019.03.18.03.07.31; Mon, 18 Mar 2019 03:07:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727740AbfCRKGu (ORCPT + 99 others); Mon, 18 Mar 2019 06:06:50 -0400 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:46675 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727575AbfCRKGt (ORCPT ); Mon, 18 Mar 2019 06:06:49 -0400 Received: from pps.filterd (m0046037.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x2IA11d5025027; Mon, 18 Mar 2019 11:06:26 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 2r8qsxb4wy-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Mar 2019 11:06:26 +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 1F9AB41; Mon, 18 Mar 2019 10:06:25 +0000 (GMT) Received: from Webmail-eu.st.com (Safex1hubcas23.st.com [10.75.90.46]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id D60D62AAA; Mon, 18 Mar 2019 10:06:24 +0000 (GMT) Received: from SAFEX1HUBCAS24.st.com (10.75.90.95) by SAFEX1HUBCAS23.st.com (10.75.90.46) with Microsoft SMTP Server (TLS) id 14.3.435.0; Mon, 18 Mar 2019 11:06:24 +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.435.0; Mon, 18 Mar 2019 11:06:24 +0100 From: Benjamin Gaignard To: , , , , , CC: , , , , , , , Benjamin Gaignard Subject: [RESEND PATCH 1/7] devicetree: bindings: Document domains controller bindings Date: Mon, 18 Mar 2019 11:05:59 +0100 Message-ID: <20190318100605.29120-2-benjamin.gaignard@st.com> X-Mailer: git-send-email 2.15.0 In-Reply-To: <20190318100605.29120-1-benjamin.gaignard@st.com> References: <20190318100605.29120-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-03-18_07:,, 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 --- .../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..f82e5e11ea64 --- /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