From: Rob Herring <robh@kernel.org>
To: Thierry Escande <thierry.escande@collabora.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Olof Johansson <olof@lixom.net>,
Stephen Warren <swarren@nvidia.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Julius Werner <jwerner@chromium.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2 4/5] firmware: Add coreboot device tree binding documentation
Date: Mon, 3 Apr 2017 09:32:42 -0500 [thread overview]
Message-ID: <20170403143242.5f7pqbawk5vcxe5j@rob-hp-laptop> (raw)
In-Reply-To: <1490717489-19218-5-git-send-email-thierry.escande@collabora.com>
On Tue, Mar 28, 2017 at 06:11:28PM +0200, Thierry Escande wrote:
> From: Julius Werner <jwerner@chromium.org>
>
> This patch adds documentation describing a device tree binding for the
> coreboot firmware. It is meant to be dynamically added during boot and
> contains address definitions for the coreboot table (a list of
> variable-sized descriptors providing information about various compile-
> and run-time generated firmware parameters) and the CBMEM area (the
> structure containing most run-time resident memory regions set up by
> coreboot).
>
> These definitions allow kernel drivers to easily access data contained
> in and pointed to by these regions (such as coreboot's in-memory log).
> (An example implementation can be seen in the following patch)
>
> Signed-off-by: Julius Werner <jwerner@chromium.org>
> Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
> ---
> .../devicetree/bindings/firmware/coreboot.txt | 33 ++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/firmware/coreboot.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-04-03 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 16:11 [PATCH v2 0/5] firmware: google memconsole Thierry Escande
2017-03-28 16:11 ` [PATCH v2 1/5] firmware: google memconsole: Remove useless submenu in Kconfig Thierry Escande
2017-03-28 16:11 ` [PATCH v2 2/5] firmware: google memconsole: Move specific EBDA parts Thierry Escande
2017-03-28 16:11 ` [PATCH v2 3/5] firmware: google memconsole: Add coreboot support Thierry Escande
2017-03-28 16:11 ` [PATCH v2 4/5] firmware: Add coreboot device tree binding documentation Thierry Escande
2017-04-03 14:32 ` Rob Herring [this message]
2017-03-28 16:11 ` [PATCH v2 5/5] firmware: google memconsole: Add ARM/ARM64 support Thierry Escande
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=20170403143242.5f7pqbawk5vcxe5j@rob-hp-laptop \
--to=robh@kernel.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
--cc=thierry.escande@collabora.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
all inboxes | Powered by JetHome®