Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp4006252rwe; Tue, 30 Aug 2022 02:58:52 -0700 (PDT) X-Google-Smtp-Source: AA6agR6WAvs/EuZkszS6/pDQyAEkbB6IMfdX1bZ7koPIsnwZk9bWAKv0wUHUB5SKyg34I0Vb8WQw X-Received: by 2002:a63:fb57:0:b0:429:5505:4f40 with SMTP id w23-20020a63fb57000000b0042955054f40mr17272554pgj.405.1661853532412; Tue, 30 Aug 2022 02:58:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661853532; cv=none; d=google.com; s=arc-20160816; b=jl6gT4GODIgOUlraYOiQr9rc0vA2wdsHOOrM+Mtmv7cAKFY/36taN9le+r60Rh1v7G JmQ3ToJiTHDqKEIEVdlcbLwNRd1mZKbtkT1Rf40jIoq448nt1QVJmky8Gq757XhQHdMh OJ76wQDH+R2gZdQ2qkCpq1fgyHxh+g1Nzob445PcjxpzGIduyboM6il1v/VyGCBstBhp kzptBlRHfYI51I3qlI/8Y32ZzNcp4iPqIUQ3nHvSRHHW4kPFo3DD2+6fObrOb3h1DFi8 lHiDmcElKQkTAP32/AxbX2vyHXHbx/203l9NmPThmRVq7UUsddoe9uE7atLAMyrGsRZ5 Hkrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=dcPFl8sGJB4/ldQtH02VQ+oFaE004ATpQC+EF0u8Q/4=; b=iJwSFylFIx3xbQDD+LVQY0nJeK2yjrVUC1klCSKZ6Zy3U/xzF7wUN0bT2TMqyaxOib 1JBbjzHDY0T3g63FG/pG8sZ72FL/fjbNx+TrhyHRP50o6i8cvTwyFVoprceuvPWdo0Km 1zrc54dpP/597rur+qONcp9rAHbgLTNa3wv9YLA1yMZjRLGzZpRZQ5bL2L+ae24QLK2p bKA5Ecv9dD8mL6UT9kte7OTXZw1x3JGvxNovrljaoCmgh96BRc7AB1I9dy+bwrzuH68N eWqfmJJCBkRxLFaR+KNX2gWeG6NpwAUXrVF8KBEwvixYgh3gnyO3NAZpk5ckuhz08izO zdGA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@metrotek.ru header.s=mail header.b=KCTwvVi6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x138-20020a633190000000b0042ad0333df1si1697841pgx.479.2022.08.30.02.58.40; Tue, 30 Aug 2022 02:58:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@metrotek.ru header.s=mail header.b=KCTwvVi6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229749AbiH3Jzh (ORCPT + 99 others); Tue, 30 Aug 2022 05:55:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36146 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229746AbiH3Jza (ORCPT ); Tue, 30 Aug 2022 05:55:30 -0400 Received: from mail.pr-group.ru (mail.pr-group.ru [178.18.215.3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB54724BD5; Tue, 30 Aug 2022 02:55:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=metrotek.ru; s=mail; h=from:subject:date:message-id:to:cc:mime-version:content-transfer-encoding: in-reply-to:references; bh=yvMCirHtcm1R7nZRNEcEPzTLj99Z8YgRXzvWBLcx31Q=; b=KCTwvVi6COde+fLN/aTkDRDYNTOU55leKMcdmIwU005cFrlOBl9Wv55RYTKPGvsMT3WamLu2lTuI5 N33v6dX+aZ/UPC/wd39ZL52bpqWPylXEIYh1jtJ7ek+cEccVKyrq3DpIBUvs1DAtlat7nGb3Gmqnc5 f1/Ypra//3AC/NA65gJ7OfpAq+dpv9CCJyLXEiJ+/8EF0qWr+NsF3debPJ6gfPqTUhuxJmWu85DhzC 4nuR+bOut4GAA+H6D6Ieo9V6HtK6DeRPZ8oEsr+HBAFEXNdgdXYEuWUVRJuttL3aNQfdkZJ2p7Qx9R 8s8wuu/b4Epyo4TGwCJq7HnT34HJuRQ== X-Kerio-Anti-Spam: Build: [Engines: 2.16.4.1445, Stamp: 3], Multi: [Enabled, t: (0.000011,0.014225)], BW: [Enabled, t: (0.000017,0.000001)], RTDA: [Enabled, t: (0.091416), Hit: No, Details: v2.41.0; Id: 15.52kal2.1gbn2qfhd.1182; mclb], total: 0(700) X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Level: X-Footer: bWV0cm90ZWsucnU= Received: from h-e2.ddg ([85.143.252.66]) (authenticated user i.bornyakov@metrotek.ru) by mail.pr-group.ru with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Tue, 30 Aug 2022 12:55:14 +0300 From: Ivan Bornyakov To: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com, trix@redhat.com, dg@emlix.com, j.zink@pengutronix.de, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: Ivan Bornyakov , linux-fpga@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@pengutronix.de, system@metrotek.ru Subject: [PATCH v9 2/2] dt-bindings: fpga: document Lattice sysCONFIG FPGA manager Date: Tue, 30 Aug 2022 12:54:05 +0300 Message-Id: <20220830095405.31609-3-i.bornyakov@metrotek.ru> X-Mailer: git-send-email 2.37.2 In-Reply-To: <20220830095405.31609-1-i.bornyakov@metrotek.ru> References: <20220830095405.31609-1-i.bornyakov@metrotek.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add Device Tree Binding doc for configuring Lattice ECP5 and MachXO2 FPGAs over Slave SPI sysCONFIG interface. Signed-off-by: Ivan Bornyakov --- .../bindings/fpga/lattice,sysconfig.yaml | 102 ++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml diff --git a/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml b/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml new file mode 100644 index 000000000000..17f1e0c50bc4 --- /dev/null +++ b/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml @@ -0,0 +1,102 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/fpga/lattice,sysconfig.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Lattice Slave SPI sysCONFIG FPGA manager + +maintainers: + - Ivan Bornyakov + +description: | + Lattice sysCONFIG port, which is used for FPGA configuration, among others, + have Slave Serial Peripheral Interface. Only full reconfiguration is + supported. + + Programming of ECP5 is done by writing uncompressed bitstream image in .bit + format into FPGA's SRAM configuration memory. + + Programming of MachXO2 is done by writing configuration data into device's + internal non-volatile Flash memory, then Self-Download of data from Flash + into SRAM is issued. + +properties: + compatible: + enum: + - lattice,ecp5-fpga-mgr + - lattice,machxo2-fpga-mgr + + reg: + maxItems: 1 + + program-gpios: + description: + A GPIO line connected to PROGRAMN (active low) pin of the device. + Initiates configuration sequence. + maxItems: 1 + + init-gpios: + description: + A GPIO line connected to INITN (active low) pin of the device. + Indicates that the FPGA is ready to be configured. + maxItems: 1 + + done-gpios: + description: + A GPIO line connected to DONE (active high) pin of the device. + Indicates that the configuration sequence is complete. + maxItems: 1 + +required: + - compatible + - reg + +allOf: + - $ref: /schemas/spi/spi-peripheral-props.yaml + + - if: + properties: + compatible: + contains: + const: lattice,machxo2-fpga-mgr + then: + properties: + spi-max-frequency: + maximum: 66000000 + + - if: + properties: + compatible: + contains: + const: lattice,ecp5-fpga-mgr + then: + properties: + spi-max-frequency: + maximum: 60000000 + +unevaluatedProperties: false + +examples: + - | + #include + + spi { + #address-cells = <1>; + #size-cells = <0>; + + fpga-mgr@0 { + compatible = "lattice,ecp5-fpga-mgr"; + reg = <0>; + spi-max-frequency = <20000000>; + program-gpios = <&gpio3 4 GPIO_ACTIVE_LOW>; + init-gpios = <&gpio3 3 GPIO_ACTIVE_LOW>; + done-gpios = <&gpio3 2 GPIO_ACTIVE_HIGH>; + }; + + fpga-mgr@1 { + compatible = "lattice,machxo2-fpga-mgr"; + reg = <1>; + spi-max-frequency = <20000000>; + }; + }; -- 2.37.2