[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151202151552.GA11101@rob-hp-laptop>
Date: Wed, 2 Dec 2015 09:15:52 -0600
From: Rob Herring <robh@...nel.org>
To: Martyn Welch <martyn.welch@...labora.co.uk>
Cc: Olof Johansson <olof@...om.net>, linux-kernel@...r.kernel.org,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/3] Device tree binding documentation for
chromeos-firmware
On Tue, Dec 01, 2015 at 07:12:49PM +0000, Martyn Welch wrote:
> This patch adds documentation for the chromeos-firmware binding.
>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Pawel Moll <pawel.moll@....com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Ian Campbell <ijc+devicetree@...lion.org.uk>
> Cc: Kumar Gala <galak@...eaurora.org>
> Cc: devicetree@...r.kernel.org
> Signed-off-by: Martyn Welch <martyn.welch@...labora.co.uk>
> ---
> .../devicetree/bindings/misc/chromeos-firmware.txt | 27 ++++++++++++++++++++++
bindings/firmware/ please.
> 1 file changed, 27 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/chromeos-firmware.txt
>
> diff --git a/Documentation/devicetree/bindings/misc/chromeos-firmware.txt b/Documentation/devicetree/bindings/misc/chromeos-firmware.txt
> new file mode 100644
> index 0000000..8240611
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/chromeos-firmware.txt
> @@ -0,0 +1,27 @@
> +Device-Tree bindings for chromeos-firmware.c.
Perhaps a bit more description what this is.
What aspect of this is firmware? How does this relate to the EC?
> +
> +Required properties:
> + - compatible = "google,gpio-firmware";
No versions?
> +
> +Each signal is represented as a sub-node of "chromeos_firmware":
> +Subnode properties:
> +
> + - gpios: OF device-tree gpio specification.
> +
> +Example nodes:
> +
> + chromeos_firmware {
This should go under /firmware
> + compatible = "google,gpio-firmware";
> +
> + write-protect {
You need to define what are valid sub nodes. The example is not
documentation.
> + gpios = <&gpx3 0 GPIO_ACTIVE_LOW>;
> + };
> +
> + developer-switch {
> + gpios = <&gpx1 3 GPIO_ACTIVE_HIGH>;
> + };
> +
> + recovery-switch {
> + gpios = <&gpx0 7 GPIO_ACTIVE_LOW>;
> + };
> + };
> --
> 2.1.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists