Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3420523imw; Mon, 18 Jul 2022 07:49:48 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s/qD+95p6nsOwrLO/d9hL6w5k8JpEdTXP227wh5c3JwJOQTtqUsRZpj1Su8I2hRXXZ/Fzo X-Received: by 2002:a17:907:2d25:b0:72b:83c2:ab90 with SMTP id gs37-20020a1709072d2500b0072b83c2ab90mr25972209ejc.373.1658155788643; Mon, 18 Jul 2022 07:49:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658155788; cv=none; d=google.com; s=arc-20160816; b=bsYhrd9RVdUWovU0JoOSrNfbQ6kltZCLAQk97AENADsyXQZJPJmehAgytLhAwPBAIv G6NdnAW0ZzrBTfaeEMb1dlHpU//nHSprEGLi7qJXPT7ujI5fWzdStsVIpq6qu6iJ0GH8 0IfwE7wQkZpGnqJI/cx7gmlOR32rIquM4ZMtus7Q8khITM0Et4Qv4KQLiYp/MntVdsfo LgSjJL69KFR22AKnJdFch2ExVVN7MCmoolXWkFZaiT9ALQJgaMWX5jF9GNhC4f/OW2n0 UUN76eA5o44rFsWY7uonTFHAh8Sprqyn1AWlpZ/LOJT25Rk+TK/r2dC7oW58G05D/xMo rrRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=LSYby1v0XqbSGLS7Fs337BwKNJGgrx+PFQuHCnfhTQc=; b=UakfufHj6jkxayspB1nMJG8Yt3TpJk28B5i/umGdnrqXAXHrtCPVPSQNbc9YdJcZMw CVl9+zB3osMbp5WsaqJRSJ9+dEZY7dT50Npf8t0rKLDLyWZ3RrgRur3C/9ycRdYecqW0 1AqWzBd3XeTEqiArqS5isohkXWh1z/3Qf8XttOwk9z51voFOmHeoBt1y6d38rZQ8uvbe N6khsCBM24hpjKhb/OPTvOy636VhVBbAqAkY+CdCQ74M4OjROYhnTRM4TOIM0/sI0KP5 /rquP3/0RpHptOQLMlejT9YQm85GF1qKyineEXGIQxGFfp8r5pgt7ajXJSsfzMqzPhCR faRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@metrotek.ru header.s=mail header.b=C1tF3Rok; 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 i11-20020a0564020f0b00b0043a7b67ce42si14228338eda.102.2022.07.18.07.49.23; Mon, 18 Jul 2022 07:49:48 -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=C1tF3Rok; 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 S234366AbiGROZH (ORCPT + 99 others); Mon, 18 Jul 2022 10:25:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231416AbiGROZE (ORCPT ); Mon, 18 Jul 2022 10:25:04 -0400 Received: from mail.pr-group.ru (mail.pr-group.ru [178.18.215.3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4893B487; Mon, 18 Jul 2022 07:25:00 -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-type:in-reply-to: references; bh=Rl8pC9UcnSTeUcI1LkcNsRHcFxoGaPb3eZk6TNA2rpI=; b=C1tF3RokzigG7wsUY2VEHj4B/CjylCnyXlCfLB3oq9uUulFrP1sIY5t0FgDfb2+6IMLXtRGbG2Z5b RB8RJsI9OA1DlRUUPr5hZS2DoFTaEMZQmXBwutyqHvMM/2TnFfLNZEcPKodbUnT+JGVoQfdM0vsbiO eOevfS3VWW9SADyfNkJZqyjDvAV9mLfG+UuZzXWFCQiLtqXOliAMw7UuK+Uh6OERKam7feVAPg10DY nS63bGAb52A7a3Hi91os81ExsEslpWQ81DsdISnf6lchWjpn8ZA6ASM2oPypxOnN3gANTXI6O0vbNc j7rABmGWKJ9Lg15ojsYt46pQq+GtUZQ== X-Kerio-Anti-Spam: Build: [Engines: 2.16.3.1424, Stamp: 3], Multi: [Enabled, t: (0.000008,0.012603)], BW: [Enabled, t: (0.000025,0.000002)], RTDA: [Enabled, t: (0.114981), Hit: No, Details: v2.40.0; Id: 15.52kbog.1g88r530o.3bqi8; 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 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)); Mon, 18 Jul 2022 17:24:48 +0300 Date: Mon, 18 Jul 2022 17:24:27 +0300 From: Ivan Bornyakov To: Krzysztof Kozlowski Cc: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com, trix@redhat.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-fpga@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, system@metrotek.ru Subject: Re: [PATCH v3 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr Message-ID: <20220718142427.vhwswafw7sa5ec6v@h-e2.ddg> References: <20220718114928.22092-1-i.bornyakov@metrotek.ru> <20220718114928.22092-3-i.bornyakov@metrotek.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Mon, Jul 18, 2022 at 03:58:22PM +0200, Krzysztof Kozlowski wrote: > On 18/07/2022 13:49, Ivan Bornyakov wrote: > > Add Device Tree Binding doc for Lattice ECP5 FPGA manager using slave > > SPI to load .bit formatted uncompressed bitstream image. > > > > Signed-off-by: Ivan Bornyakov > > --- > > .../bindings/fpga/lattice,ecp5-fpga-mgr.yaml | 73 +++++++++++++++++++ > > 1 file changed, 73 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/fpga/lattice,ecp5-fpga-mgr.yaml > > > > diff --git a/Documentation/devicetree/bindings/fpga/lattice,ecp5-fpga-mgr.yaml b/Documentation/devicetree/bindings/fpga/lattice,ecp5-fpga-mgr.yaml > > new file mode 100644 > > index 000000000000..bb10fd316f94 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/fpga/lattice,ecp5-fpga-mgr.yaml > > @@ -0,0 +1,73 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/fpga/lattice,ecp5-fpga-mgr.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Lattice ECP5 Slave SPI FPGA manager. > > + > > +maintainers: > > + - Ivan Bornyakov > > + > > +description: > > + FPGA Manager capable to program Lattice ECP5 with uncompressed bitstream > > + image in .bit format over SPI. > > The same question as before - you need to explain what is the hardware > (not Linux API or Linux subsystem). > I really don't know what to say aside from "thing that capable to program FPGA". Is there a good exmple of proper wording in Documentation/devicetree/bindings/fpga/? Otherwise I would ask FPGA Manager framework maintainers assistance on how to describe a FPGA Manager driver. > > + > > +allOf: > > + - $ref: /schemas/spi/spi-peripheral-props.yaml > > + > > +properties: > > + reg: > > + maxItems: 1 > > + > > + spi-max-frequency: > > + maximum: 60000000 > > + > > + compatible: > > + enum: > > + - lattice,ecp5-fpga-mgr > > Compatible goes first in the list of properties. Change here was not > requested, so I am surprised to see different coding style. > > > + > > + 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 > > + - program-gpios > > + - init-gpios > > + - done-gpios > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include > > + > > + spi { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + fpga-mgr@0 { > > + compatible = "lattice,ecp5-fpga-mgr"; > > + spi-max-frequency = <20000000>; > > + reg = <0>; > > compatible then reg, then rest of properties. > > > > Best regards, > Krzysztof