From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>,
mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
trix@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: 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
Date: Mon, 18 Jul 2022 15:58:22 +0200 [thread overview]
Message-ID: <d15fcfa1-91ce-70fa-143f-748ead9a4337@linaro.org> (raw)
In-Reply-To: <20220718114928.22092-3-i.bornyakov@metrotek.ru>
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 <i.bornyakov@metrotek.ru>
> ---
> .../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 <i.bornyakov@metrotek.ru>
> +
> +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).
> +
> +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 <dt-bindings/gpio/gpio.h>
> +
> + 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
next prev parent reply other threads:[~2022-07-18 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 11:49 [PATCH v3 0/2] Lattice ECP5 FPGA manager Ivan Bornyakov
2022-07-18 11:49 ` [PATCH v3 1/2] fpga: ecp5-spi: add " Ivan Bornyakov
2022-07-18 11:49 ` [PATCH v3 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr Ivan Bornyakov
2022-07-18 13:58 ` Krzysztof Kozlowski [this message]
2022-07-18 14:24 ` Ivan Bornyakov
2022-07-18 14:32 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d15fcfa1-91ce-70fa-143f-748ead9a4337@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=i.bornyakov@metrotek.ru \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=robh+dt@kernel.org \
--cc=system@metrotek.ru \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).