Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758725AbbLBPP7 (ORCPT ); Wed, 2 Dec 2015 10:15:59 -0500 Received: from mail.kernel.org ([198.145.29.136]:51946 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752494AbbLBPP5 (ORCPT ); Wed, 2 Dec 2015 10:15:57 -0500 Date: Wed, 2 Dec 2015 09:15:52 -0600 From: Rob Herring To: Martyn Welch Cc: Olof Johansson , linux-kernel@vger.kernel.org, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org Subject: Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Message-ID: <20151202151552.GA11101@rob-hp-laptop> References: <1448997171-7064-1-git-send-email-martyn.welch@collabora.co.uk> <1448997171-7064-2-git-send-email-martyn.welch@collabora.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448997171-7064-2-git-send-email-martyn.welch@collabora.co.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2065 Lines: 74 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 > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Ian Campbell > Cc: Kumar Gala > Cc: devicetree@vger.kernel.org > Signed-off-by: Martyn Welch > --- > .../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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/