From: Ivan Bornyakov <i.bornyakov@metrotek.ru>
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: linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
system@metrotek.ru
Subject: Re: [PATCH v9 2/2] dt-bindings: fpga: document Lattice sysCONFIG FPGA manager
Date: Tue, 30 Aug 2022 13:32:01 +0300 [thread overview]
Message-ID: <20220830103201.dmtvotiq43g742v5@h-e2.ddg> (raw)
In-Reply-To: <20220830095405.31609-3-i.bornyakov@metrotek.ru>
On Tue, Aug 30, 2022 at 12:54:05PM +0300, Ivan Bornyakov wrote:
> Add Device Tree Binding doc for configuring Lattice ECP5 and MachXO2
> FPGAs over Slave SPI sysCONFIG interface.
>
> Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
> ---
> .../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 <i.bornyakov@metrotek.ru>
> +
> +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 <dt-bindings/gpio/gpio.h>
> +
> + 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
>
Sorry, I forgot to add a tag from Krzysztof. Since there is not much
change here, I think the tag is still valid.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
prev parent reply other threads:[~2022-08-30 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:54 [PATCH v9 0/2] Lattice sysCONFIG SPI FPGA manager Ivan Bornyakov
2022-08-30 9:54 ` [PATCH v9 1/2] fpga: lattice-sysconfig-spi: add Lattice sysCONFIG " Ivan Bornyakov
2022-09-03 16:53 ` Xu Yilun
2022-09-04 9:04 ` Ivan Bornyakov
2022-08-30 9:54 ` [PATCH v9 2/2] dt-bindings: fpga: document " Ivan Bornyakov
2022-08-30 10:32 ` Ivan Bornyakov [this message]
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=20220830103201.dmtvotiq43g742v5@h-e2.ddg \
--to=i.bornyakov@metrotek.ru \
--cc=devicetree@vger.kernel.org \
--cc=dg@emlix.com \
--cc=hao.wu@intel.com \
--cc=j.zink@pengutronix.de \
--cc=kernel@pengutronix.de \
--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).