Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1952565ybg; Fri, 5 Jun 2020 01:38:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyzMrhtonhP8t5LKRm62w6i9Secern4aV8vFiFvvKFHrD7Q6rbBNGXcjazTXZuxDl1pIIeG X-Received: by 2002:a17:906:2e81:: with SMTP id o1mr7276392eji.362.1591346315661; Fri, 05 Jun 2020 01:38:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591346315; cv=none; d=google.com; s=arc-20160816; b=lcTycTlbhPcggouqMC6KBy/v49CGw0qOM/fvrWwIRcorlQLas9FF6nhaemB0/3Khn3 mnY010HRxD+XN06uvCP3Hf+Jzw1bFliuTNHIy4ZaBo/qrO+Vwj3RzrDgUDA0HN+V9z8o 9kMmJHkqhO2qewT+5TOsZaBNyMSUxyI9YyAsMj001/IPUfpJhckHG7d2LnW3MHHnIMWc x+JoYXhlzYRu7cjyoy+n56O2/RNqGE+7gN88BpjGRL1Z1qPJnXmBQtbWUwzpODya8zdJ 7tHSUC74vCBY2lxfkUIqNdBQQ2821IjMkHs0oOQUC2L1K2AtIhTStuhXmbHA1BApzSSF ZTZg== 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:dkim-signature; bh=7+MnleNJkiEaO/P1tUZdrf9rpTSD5jzSpmCxlBfmTnI=; b=ZcBuIK5mMTc1l/W3TXSGHGMFPfaEnAcUuzpL7CPrcnTXXsFls96kxnGP19CmOcUDx9 TqUziBb37YdfFE9QyeioM0mOHTw10n+3FcHcuYGk1apII7/qSe6SpalvFmYcQDmJpwfE U5Wb9F6SkSoK6JvLrC5AMMVWXuGhIrZDHdL6uXfAsYVNHKOXgoIVEGFrvFcotNDOUdXV 9nsbO5CR1HdCLouYCYRzDxuqeFXjrzYXC3fanpmA+eaAbVyyIdneQ5cz8uwQwf2iES4k H0/tveVvHRY3UlWDYGQfXu5P7XzoFAD+UrKIaEF3PvQeIbhpL4E4vPQBjx+OiRYRsESH NIyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=giXx+qn2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id pk21si3377396ejb.696.2020.06.05.01.38.12; Fri, 05 Jun 2020 01:38:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@st.com header.s=STMicroelectronics header.b=giXx+qn2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=st.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726179AbgFEIeR (ORCPT + 99 others); Fri, 5 Jun 2020 04:34:17 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:4662 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726096AbgFEIeP (ORCPT ); Fri, 5 Jun 2020 04:34:15 -0400 Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 0558Wf3B029843; Fri, 5 Jun 2020 10:33:53 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=st.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=STMicroelectronics; bh=7+MnleNJkiEaO/P1tUZdrf9rpTSD5jzSpmCxlBfmTnI=; b=giXx+qn2MJVw97M8A3ITV3iPXJykZsf/gyxFedRPDkio8UuQ3+jj59T43IW3jIUSsuUm QMrH51YrYRMMbNPr9IaFKq0uUj7JUvqXLezzmvwiltic2Ad9wrL/1EhBParyMZuBUc/E /GVrMJVbj+HTaKAntn3RoAKZO9oOMrLERnefxSngfrOu2M2bXpyH3cZN0E98EdTrMDt+ YT99L6Al9dQjyHnTolgtbfZe+CQ12MzKXO1zlE+GaM6gzzGcbRwMMZpOY1Qg1ziwL5V8 GpFiBqFq7ko+hEBhSg8cuUzP5EXMDUhQMW+i1jLOHURzCQn/4hMGZwhWJCw8AKG4CKU5 /w== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 31fasma4ex-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 05 Jun 2020 10:33:53 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 3D65010002A; Fri, 5 Jun 2020 10:33:52 +0200 (CEST) Received: from Webmail-eu.st.com (sfhdag3node3.st.com [10.75.127.9]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 2C5852B21C0; Fri, 5 Jun 2020 10:33:52 +0200 (CEST) Received: from localhost (10.75.127.44) by SFHDAG3NODE3.st.com (10.75.127.9) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 5 Jun 2020 10:33:51 +0200 From: Benjamin Gaignard To: , , , , CC: , , , , , Benjamin Gaignard Subject: [PATCH v4 1/5] dt-bindings: bus: Add firewall bindings Date: Fri, 5 Jun 2020 10:33:44 +0200 Message-ID: <20200605083348.13880-2-benjamin.gaignard@st.com> X-Mailer: git-send-email 2.15.0 In-Reply-To: <20200605083348.13880-1-benjamin.gaignard@st.com> References: <20200605083348.13880-1-benjamin.gaignard@st.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.75.127.44] X-ClientProxiedBy: SFHDAG5NODE1.st.com (10.75.127.13) To SFHDAG3NODE3.st.com (10.75.127.9) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216,18.0.687 definitions=2020-06-05_01:2020-06-04,2020-06-05 signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add schemas for firewall consumer and provider. Signed-off-by: Benjamin Gaignard Reviewed-by: Linus Walleij --- .../bindings/bus/stm32/firewall-consumer.yaml | 36 ++++++++++++++++++++++ .../bindings/bus/stm32/firewall-provider.yaml | 18 +++++++++++ 2 files changed, 54 insertions(+) create mode 100644 Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml create mode 100644 Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml diff --git a/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml b/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml new file mode 100644 index 000000000000..d3d76f99b38d --- /dev/null +++ b/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml @@ -0,0 +1,36 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/bus/stm32/firewall-consumer.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Common Bus Firewall consumer binding + +description: | + Firewall properties provide the possible firewall bus controller + configurations for a device. + Bus firewall controllers are typically used to control if a hardware + block can perform read or write operations on bus. + The contents of the firewall bus configuration properties are defined by + the binding for the individual firewall controller device. + + The first configuration 'firewall-0' or the one named 'default' is + applied before probing the device itself. + +maintainers: + - Benjamin Gaignard + +# always select the core schema +select: true + +properties: + firewall-0: true + + firewall-names: true + +patternProperties: + "firewall-[0-9]": + $ref: "/schemas/types.yaml#/definitions/phandle-array" + +dependencies: + firewall-names: [ firewall-0 ] diff --git a/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml b/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml new file mode 100644 index 000000000000..299824c620ea --- /dev/null +++ b/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml @@ -0,0 +1,18 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/bus/stm32/firewall-provider.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Common Bus Firewall provider binding + +maintainers: + - Benjamin Gaignard + +properties: + '#firewall-cells': + $ref: /schemas/types.yaml#/definitions/uint32 + description: Number of cells in a bus firewall specifier + +required: + - '#firewall-cells' -- 2.15.0