From: Marek Vasut <marex@denx.de>
To: Joel Holdsworth <joel@airwebreathe.org.uk>,
atull@opensource.altera.com, moritz.fischer@ettus.com,
geert@linux-m68k.org, robh@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, clifford@clifford.at
Subject: Re: [PATCH v8 2/3] Documentation: Add binding document for Lattice iCE40 FPGA manager
Date: Mon, 7 Nov 2016 18:53:39 +0100 [thread overview]
Message-ID: <7876f66a-f8c2-409b-0f18-e8055ddc7784@denx.de> (raw)
In-Reply-To: <1478486962-26794-2-git-send-email-joel@airwebreathe.org.uk>
On 11/07/2016 03:49 AM, Joel Holdsworth wrote:
> This adds documentation of the device tree bindings of the Lattice iCE40
> FPGA driver for the FPGA manager framework.
>
> Signed-off-by: Joel Holdsworth <joel@airwebreathe.org.uk>
> ---
> .../bindings/fpga/lattice-ice40-fpga-mgr.txt | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/fpga/lattice-ice40-fpga-mgr.txt
>
> diff --git a/Documentation/devicetree/bindings/fpga/lattice-ice40-fpga-mgr.txt b/Documentation/devicetree/bindings/fpga/lattice-ice40-fpga-mgr.txt
> new file mode 100644
> index 0000000..7e7a78b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/fpga/lattice-ice40-fpga-mgr.txt
> @@ -0,0 +1,21 @@
> +Lattice iCE40 FPGA Manager
> +
> +Required properties:
> +- compatible: Should contain "lattice,ice40-fpga-mgr"
> +- reg: SPI chip select
> +- spi-max-frequency: Maximum SPI frequency (>=1000000, <=25000000)
> +- cdone-gpios: GPIO input connected to CDONE pin
> +- reset-gpios: Active-low GPIO output connected to CRESET_B pin. Note
> + that unless the GPIO is held low during startup, the
> + FPGA will enter Master SPI mode and drive SCK with a
> + clock signal potentially jamming other devices on the
> + bus until the firmware is loaded.
> +
> +Example:
> + ice40: ice40@0 {
> + compatible = "lattice,ice40-fpga-mgr";
> + reg = <0>;
> + spi-max-frequency = <1000000>;
> + cdone-gpios = <&gpio 24 GPIO_ACTIVE_HIGH>;
> + reset-gpios = <&gpio 22 GPIO_ACTIVE_LOW>;
Wouldn't it make more sense to have "gpios" and "gpio-names" ? That
scales better imo, although in this case we cannot really talk about
scaling.
> + };
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-11-07 18:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:49 [PATCH v8 1/3] of: Add vendor prefix for Lattice Semiconductor Joel Holdsworth
2016-11-07 2:49 ` [PATCH v8 2/3] Documentation: Add binding document for Lattice iCE40 FPGA manager Joel Holdsworth
2016-11-07 17:53 ` Marek Vasut [this message]
2016-11-07 18:57 ` Joel Holdsworth
2016-11-14 16:11 ` Rob Herring
2016-11-18 18:56 ` atull
2016-11-18 19:17 ` Moritz Fischer
2016-11-18 19:28 ` Marek Vasut
2016-11-07 2:49 ` [PATCH v8 3/3] fpga: Add support for Lattice iCE40 FPGAs Joel Holdsworth
2016-11-07 18:01 ` Marek Vasut
2016-11-07 18:49 ` Joel Holdsworth
2016-11-07 18:53 ` Marek Vasut
2016-11-08 17:06 ` Moritz Fischer
2016-11-08 17:30 ` Joel Holdsworth
2016-11-09 12:01 ` Marek Vasut
2016-11-09 18:37 ` Joel Holdsworth
2016-11-09 18:39 ` Marek Vasut
2016-11-09 18:54 ` Joel Holdsworth
2016-11-10 12:11 ` Marek Vasut
2016-11-08 17:13 ` Joel Holdsworth
2016-11-07 18:26 ` Moritz Fischer
2016-11-07 19:02 ` Joel Holdsworth
2016-11-07 21:41 ` Moritz Fischer
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=7876f66a-f8c2-409b-0f18-e8055ddc7784@denx.de \
--to=marex@denx.de \
--cc=atull@opensource.altera.com \
--cc=clifford@clifford.at \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=joel@airwebreathe.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=robh@kernel.org \
/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).