Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1282265
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware |
| Date | 2015-12-02 19:50 +0100 |
| Message-ID | <qBkDw-2x9-17@gated-at.bofh.it> (permalink) |
| References | <qAYD0-5ha-7@gated-at.bofh.it> <qAYD0-5ha-9@gated-at.bofh.it> <qBhmi-sK-21@gated-at.bofh.it> <qBiV4-1mH-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Dec 2, 2015 at 10:49 AM, Martyn Welch <martyn.welch@collabora.co.uk> wrote: > > > On 02/12/15 15:15, Rob Herring wrote: >> >> 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@kernel.org> >>> Cc: Pawel Moll <pawel.moll@arm.com> >>> Cc: Mark Rutland <mark.rutland@arm.com> >>> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> >>> Cc: Kumar Gala <galak@codeaurora.org> >>> Cc: devicetree@vger.kernel.org >>> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> >>> --- >>> .../devicetree/bindings/misc/chromeos-firmware.txt | 27 >>> ++++++++++++++++++++++ >> >> >> bindings/firmware/ please. >> > > OK. > >>> 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? >> > > With respect to write-protect, this line is the write protection for the > flash which holds the bootloader. What is driving the write-protect? Are trying to assign ownership of the SOC GPIOs to the bootloader/firmware? If so, I think this is all wrong. Rob -- 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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] Device tree binding documentation for chromeos-firmware Martyn Welch <martyn.welch@collabora.co.uk> - 2015-12-01 20:20 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Rob Herring <robh@kernel.org> - 2015-12-02 16:20 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Martyn Welch <martyn.welch@collabora.co.uk> - 2015-12-02 18:00 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Rob Herring <robh@kernel.org> - 2015-12-02 19:50 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Martyn Welch <martyn.welch@collabora.co.uk> - 2015-12-02 22:50 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Martyn Welch <martyn.welch@collabora.co.uk> - 2015-12-03 11:20 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Rob Herring <robh@kernel.org> - 2015-12-03 16:10 +0100
Re: [PATCH 1/3] Device tree binding documentation for chromeos-firmware Martyn Welch <martyn.welch@collabora.co.uk> - 2015-12-03 17:20 +0100
csiph-web