From: Krzysztof Kozlowski <krzk@kernel.org>
To: iansdannapel@gmail.com, mdf@kernel.org, hao.wu@intel.com,
yilun.xu@intel.com, trix@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, heiko.stuebner@cherry.de,
rafal@milecki.pl, linus.walleij@linaro.org,
linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: fpga: Add Efinix serial SPI programming bindings
Date: Fri, 27 Sep 2024 16:26:11 +0200 [thread overview]
Message-ID: <dd9ae106-3c39-423b-9413-5a7ca57f7aec@kernel.org> (raw)
In-Reply-To: <20240927141445.157234-2-iansdannapel@gmail.com>
On 27/09/2024 16:14, iansdannapel@gmail.com wrote:
> From: Ian Dannapel <iansdannapel@gmail.com>
>
> Add device tree binding documentation for configuring Efinix FPGA
> using serial SPI passive programming mode.
>
> Signed-off-by: Ian Dannapel <iansdannapel@gmail.com>
> ---
> .../fpga/efinix,trion-spi-passive.yaml | 85 +++++++++++++++++++
> 1 file changed, 85 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/fpga/efinix,trion-spi-passive.yaml
>
> diff --git a/Documentation/devicetree/bindings/fpga/efinix,trion-spi-passive.yaml b/Documentation/devicetree/bindings/fpga/efinix,trion-spi-passive.yaml
> new file mode 100644
> index 000000000000..ec6697fa6f44
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/fpga/efinix,trion-spi-passive.yaml
> @@ -0,0 +1,85 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/fpga/efinix,trion-spi-passive.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Efinix SPI FPGA Manager
> +
> +maintainers:
> + - Ian Dannapel <iansdannapel@gmail.com>
> +
> +description: |
> + Efinix Trion and Titanium Series FPGAs support a method of loading the
> + bitstream over what is referred to as "SPI Passive Programming".
> + Only serial (1x bus width) is supported, setting the programming mode
> + is not in the scope the this manager and must be done elsewhere.
> +
> + Warning: The slave serial link is not technically SPI and therefore it is
> + not recommended to have other devices on the same bus since it might
> + interfere or be interfered by other transmissions.
> +
> + References:
> + - https://www.efinixinc.com/docs/an033-configuring-titanium-fpgas-v2.6.pdf
> + - https://www.efinixinc.com/docs/an006-configuring-trion-fpgas-v6.0.pdf
> +
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - efinix,trion-spi-passive
> + - efinix,titanium-spi-passive
1. Your driver suggests these are compatible, so make them compatible
with using fallback.
2. What is "spi-passive"? Compatible is supposed to be the name of the
device, so I assume this is "trion"? Can trion be anything else than fpga?
> +
> + spi-cpha: true
> +
> + spi-cpol: true
> +
> + spi-max-frequency:
> + maximum: 25000000
> +
> + reg:
> + maxItems: 1
> +
> + creset-gpios:
reset-gpios
Do not invent own properties.
> + description:
> + reset and re-configuration trigger pin (low active)
> + maxItems: 1
> +
> + cs-gpios:
> + description:
> + chip-select pin (low active)
Eee? That's a property of controller, not child. Aren't you duplicating
existing controller property?
> + maxItems: 1
> +
> + cdone-gpios:
> + description:
> + optional configuration done status pin (high active)
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - creset-gpios
> + - cs-gpios
> +
> +additionalProperties: false
unevaluatedProperties instead
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-27 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 14:14 [PATCH 1/3] fpga: Add Efinix Trion & Titanium serial SPI programming driver iansdannapel
2024-09-27 14:14 ` [PATCH 2/3] dt-bindings: fpga: Add Efinix serial SPI programming bindings iansdannapel
2024-09-27 14:26 ` Krzysztof Kozlowski [this message]
2024-09-27 15:34 ` Ian Dannapel
2024-09-28 7:31 ` Krzysztof Kozlowski
2024-09-28 12:33 ` Ian Dannapel
2024-09-28 12:53 ` Krzysztof Kozlowski
2024-09-28 14:26 ` Ian Dannapel
2024-09-29 19:49 ` Krzysztof Kozlowski
2024-09-27 14:14 ` [PATCH 3/3] dt-bindings: vendor-prefix: Add prefix for Efinix, Inc iansdannapel
2024-09-27 14:26 ` Krzysztof Kozlowski
2024-09-30 6:23 ` Alexander Dahl
2024-09-27 14:14 ` [PATCH v3 0/3] Summary of changes iansdannapel
2024-09-27 14:27 ` Krzysztof Kozlowski
2024-09-27 14:22 ` [PATCH 1/3] fpga: Add Efinix Trion & Titanium serial SPI programming driver Krzysztof Kozlowski
2024-10-18 1:22 ` Xu Yilun
2024-10-18 1:37 ` Xu Yilun
2024-10-18 16:58 ` Conor Dooley
2024-10-21 2:10 ` Xu Yilun
2024-10-21 12:18 ` Conor Dooley
2024-10-21 13:23 ` Ian Dannapel
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=dd9ae106-3c39-423b-9413-5a7ca57f7aec@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=heiko.stuebner@cherry.de \
--cc=iansdannapel@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.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).