From: Conor Dooley <conor@kernel.org>
To: iansdannapel@gmail.com
Cc: linux-fpga@vger.kernel.org, "Moritz Fischer" <mdf@kernel.org>,
"Wu Hao" <hao.wu@intel.com>, "Xu Yilun" <yilun.xu@intel.com>,
"Tom Rix" <trix@redhat.com>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Aradhya Bhatia" <a-bhatia1@ti.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [v4 2/3] dt-bindings: fpga: Add Efinix SPI programming bindings
Date: Fri, 28 Feb 2025 18:28:27 +0000 [thread overview]
Message-ID: <20250228-copilot-trekker-72a20709e9f7@spud> (raw)
In-Reply-To: <20250228094732.54642-3-iansdannapel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3361 bytes --]
On Fri, Feb 28, 2025 at 10:47:31AM +0100, iansdannapel@gmail.com wrote:
> From: Ian Dannapel <iansdannapel@gmail.com>
>
> Add device tree bindings documentation for configuring Efinix FPGA
> using serial SPI passive programming mode.
>
> Signed-off-by: Ian Dannapel <iansdannapel@gmail.com>
> ---
> .../devicetree/bindings/fpga/efinix,spi.yaml | 81 +++++++++++++++++++
> 1 file changed, 81 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/fpga/efinix,spi.yaml
>
> diff --git a/Documentation/devicetree/bindings/fpga/efinix,spi.yaml b/Documentation/devicetree/bindings/fpga/efinix,spi.yaml
> new file mode 100644
> index 000000000000..145c96f38e45
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/fpga/efinix,spi.yaml
Filename matching a compatible please.
> @@ -0,0 +1,81 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/fpga/efinix,spi.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Efinix SPI FPGA Manager
> +
> +maintainers:
> + - Ian Dannapel <iansdannapel@gmail.com>
> +
> +description: |
> + Efinix FPGAs (Trion, Topaz, and Titanium families) support loading bitstreams
> + through "SPI Passive Mode".
> + Note 1: Only bus width 1x is supported.
> + Note 2: Additional pins hogs for bus width configuration must be set
> + elsewhere, if necessary.
> + Note 3: Topaz and Titanium support is based on documentation but remains
> + untested.
Points 1 and 3 here seem to be driver limitations, and shouldn't really
be present in a document describing the hardware?
> +
> + References:
> + - https://www.efinixinc.com/docs/an006-configuring-trion-fpgas-v6.3.pdf
> + - https://www.efinixinc.com/docs/an033-configuring-titanium-fpgas-v2.8.pdf
> + - https://www.efinixinc.com/docs/an061-configuring-topaz-fpgas-v1.1.pdf
> +
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - efinix,trion-spi
> + - efinix,titanium-spi
> + - efinix,topaz-spi
> + - efinix,fpga-spi
What hardware does this device represent? Other ones are obvious matches
to the families you mention, but what is this one?
Cheers,
Conor.
> +
> + spi-cpha: true
> +
> + spi-cpol: true
> +
> + spi-max-frequency:
> + maximum: 25000000
> +
> + reg:
> + maxItems: 1
> +
> + reset-gpios:
> + description:
> + reset and re-configuration trigger pin (low active)
> + maxItems: 1
> +
> + cdone-gpios:
> + description:
> + optional configuration done status pin (high active)
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - reset-gpios
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + cs-gpios = <&gpio5 13 GPIO_ACTIVE_LOW>;
> + fpga-mgr@0 {
> + compatible = "efinix,trion-spi";
> + reg = <0>;
> + spi-max-frequency = <25000000>;
> + spi-cpha;
> + spi-cpol;
> + reset-gpios = <&gpio4 17 GPIO_ACTIVE_LOW>;
> + cdone-gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +...
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-28 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:47 [v4 0/3] Add Efinix FPGA SPI programming support iansdannapel
2025-02-28 9:47 ` [v4 1/3] dt-bindings: vendor-prefix: Add prefix for Efinix, Inc iansdannapel
2025-02-28 18:29 ` Conor Dooley
2025-03-01 13:10 ` Krzysztof Kozlowski
2025-03-04 11:24 ` Alexander Dahl
2025-02-28 9:47 ` [v4 2/3] dt-bindings: fpga: Add Efinix SPI programming bindings iansdannapel
2025-02-28 18:28 ` Conor Dooley [this message]
2025-03-03 10:10 ` Ian Dannapel
2025-03-03 10:29 ` Ian Dannapel
2025-03-03 10:33 ` Krzysztof Kozlowski
2025-03-03 10:31 ` Conor Dooley
2025-03-03 10:34 ` Krzysztof Kozlowski
2025-03-01 13:13 ` Krzysztof Kozlowski
2025-02-28 9:47 ` [v4 3/3] fpga-mgr: Add Efinix SPI programming driver iansdannapel
2025-03-03 11:57 ` Manne, Nava kishore
2025-03-03 12:16 ` Ian Dannapel
2025-03-16 15:03 ` Xu Yilun
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=20250228-copilot-trekker-72a20709e9f7@spud \
--to=conor@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=a-bhatia1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=iansdannapel@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--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).