Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp505625ybk; Wed, 13 May 2020 05:58:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyX2iigLSyk8lvRVgje8pYc1uyTUH4Z6en9weyl860qt0wa6V8ianqcal6+nORJUB8rLy3/ X-Received: by 2002:a17:906:298a:: with SMTP id x10mr11481847eje.238.1589374734391; Wed, 13 May 2020 05:58:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589374734; cv=none; d=google.com; s=arc-20160816; b=hkmYpbe6Xk0r6JDOkNIpJKMs1hSRVMtK1egd8gt4Oke/Fkla9wlxdzOLALdoo1YToB S2GNtDzpURvdaXoBXY5tmfhkIDvvJIh+vvA/DXfT4eOaRZisKv4+vA9Ij1oKtxpVqb2c SAXU+nkBqPcVFGB6qosyQbJ56YEZEvq9t+FfN2TRNqOhZg0FcdmUz+IsuTqq5viMNXHJ Wp8C3P0VwkkxDEspMrU6xAIhnzaRZ3dc7BDTghDQva2EoaaHQv1jL3QlK3nza/c0zzzn wb/X63UTmDsGxmOi/BeYjF/pSHmfmo94srXcmsFOWNaR7lQAs1/wgSyMqQcOYhNF0jEO zURA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :ironport-sdr:dkim-signature; bh=VgbKaduJ+GyHESrmH1xVm/Vd0EqDKmZq970dv3i3kn0=; b=TqEQjBBwWBNKbLzvITx0gAsAoGMC1A95WJbOIfwndmb69IoqkfI6fHYLX4w+XHyAfb PeYWXT51RLT0qmyzzeAV76rxFS8mi7J8HN2Eb2rHGlGAdffVQrEfL0XgWn2UMSmu/SgC UJg46/ednibN6d7s2GfZqhsvWtRxHzYMg7o+mJV4S+5Mqd9QtG/BESpYH+EKnYLFQyDz FWkeVesr7yVib5OO3Ob/2DXRrRMx2126QhJSp5PTI30pThesRfl/2tZYpJmI+coIRzrt XK+f8LsQdu0+QZwjxWw/GBEJmE78FMahnL7Gr8XXHqIYrabQ/T/dZFLfveoWcLxyTSUa Oa5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@microchip.com header.s=mchp header.b="19ZI/nOy"; 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=fail (p=NONE sp=NONE dis=NONE) header.from=microchip.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h21si1555095ejq.372.2020.05.13.05.58.31; Wed, 13 May 2020 05:58:54 -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=fail header.i=@microchip.com header.s=mchp header.b="19ZI/nOy"; 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=fail (p=NONE sp=NONE dis=NONE) header.from=microchip.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733167AbgEMM4s (ORCPT + 99 others); Wed, 13 May 2020 08:56:48 -0400 Received: from esa3.microchip.iphmx.com ([68.232.153.233]:29570 "EHLO esa3.microchip.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731644AbgEMM4r (ORCPT ); Wed, 13 May 2020 08:56:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1589374606; x=1620910606; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=poBPrhT3w6QbThTNX7WMhvl6ITRtWZafa6qFqSWWJSM=; b=19ZI/nOyOQ1yISZ95HqFgMsJfoNCP1o6QilIEtkIeFZzP6oG9MO4HE5w rOBhuWvbYAux5N5aRp4TWCfH/Yi42QtY/cluJgoyEHkfDpogrc9cIQAQo UVQ1qA9Pl4+ZCgF76ZbBKjJKzyKmhGm/uEd85/w8U8zOTfGAQbueVRMY8 dWRgqWMjgNdYgX2Pna0+jRD8X5bw5scDxL9YEIqbR61saMANjdUh1RvNH BQ0XcLWKEq0ZntWc75NVPB3XqacRdUeFaH6I//O7VAFBjwXpytvbi+QV5 x5dWvmDIho3dMWtMQEsueqnKi5A8OzS+1XtEsgbRAaOloKxmP1T7g0dJF g==; IronPort-SDR: xxJdrEOxoKFUoLTD14Tc43OvYgZ/knJ6/cbfPW9+CoTHjCaaQ1u/jmYup6A6CbZQhwERynlnod rFRLF3M/WkpD1TVTYVAN1fmXQV9PmBKBpdq21AnRDX3Htw4lER5Hn6WV0fZ3Q+Z5l/HVaEko8p DE3WRmiUUiLPbP3U1bNAyP2RpFCyQlU7/Vwwl2No0MeKdcrk8QFbonZJpZzCpkVPeGL0+z01xE s/CVAdnli96L3/nH5bHtKt61tiSbkEh+u8NbFYaWRLA9pYgSkO3cTnj7eVdZV4Lvewn6indXai sFM= X-IronPort-AV: E=Sophos;i="5.73,387,1583218800"; d="scan'208";a="76494614" Received: from smtpout.microchip.com (HELO email.microchip.com) ([198.175.253.82]) by esa3.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 13 May 2020 05:56:45 -0700 Received: from chn-vm-ex04.mchp-main.com (10.10.85.152) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 13 May 2020 05:56:48 -0700 Received: from soft-dev15.microsemi.net (10.10.115.15) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server id 15.1.1713.5 via Frontend Transport; Wed, 13 May 2020 05:56:42 -0700 From: Lars Povlsen To: SoC Team , Arnd Bergmann , Stephen Boyd , Linus Walleij , Rob Herring CC: Lars Povlsen , Steen Hegelund , Microchip Linux Driver Support , Olof Johansson , "Michael Turquette" , , , , , , Alexandre Belloni Subject: [PATCH 05/14] dt-bindings: arm: sparx5: Add documentation for Microchip Sparx5 SoC Date: Wed, 13 May 2020 14:55:23 +0200 Message-ID: <20200513125532.24585-6-lars.povlsen@microchip.com> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200513125532.24585-1-lars.povlsen@microchip.com> References: <20200513125532.24585-1-lars.povlsen@microchip.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This adds the main Sparx5 SoC DT documentation file, with information abut the supported board types. Reviewed-by: Alexandre Belloni Signed-off-by: Lars Povlsen --- .../bindings/arm/microchip,sparx5.yaml | 87 +++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/microchip,sparx5.yaml diff --git a/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml b/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml new file mode 100644 index 0000000000000..83b36d1217988 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml @@ -0,0 +1,87 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/microchip,sparx5.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Microchip Sparx5 Boards Device Tree Bindings + +maintainers: + - Lars Povlsen + +description: |+ + The Microchip Sparx5 SoC is a ARMv8-based used in a family of + gigabit TSN-capable gigabit switches. + + The SparX-5 Ethernet switch family provides a rich set of switching + features such as advanced TCAM-based VLAN and QoS processing + enabling delivery of differentiated services, and security through + TCAM-based frame processing using versatile content aware processor + (VCAP) + +properties: + $nodename: + const: '/' + compatible: + oneOf: + - description: The Sparx5 pcb125 board is a modular board, + which has both spi-nor and eMMC storage. The modular design + allows for connection of different network ports. + items: + - const: microchip,sparx5-pcb125 + - const: microchip,sparx5 + + - description: The Sparx5 pcb134 is a pizzabox form factor + gigabit switch with 20 SFP ports. It features spi-nor and + either spi-nand or eMMC storage (mount option). + items: + - const: microchip,sparx5-pcb134 + - const: microchip,sparx5 + + - description: The Sparx5 pcb135 is a pizzabox form factor + gigabit switch with 48+4 Cu ports. It features spi-nor and + either spi-nand or eMMC storage (mount option). + items: + - const: microchip,sparx5-pcb135 + - const: microchip,sparx5 + + axi@600000000: + type: object + description: the root node in the Sparx5 platforms must contain + an axi bus child node. They are always at physical address + 0x600000000 in all the Sparx5 variants. + properties: + compatible: + items: + - const: simple-bus + reg: + maxItems: 1 + + required: + - compatible + - reg + +patternProperties: + "^syscon@[0-9a-f]+$": + description: All Sparx5 boards must provide a system controller, + typically under the axi bus node. It contain reset registers and + other system control. + type: object + properties: + compatible: + items: + - const: microchip,sparx5-cpu-syscon + - const: syscon + reg: + maxItems: 1 + + required: + - compatible + - reg + +required: + - compatible + - axi@600000000 + - syscon@600000000 + +... -- 2.26.2