From: Kevin Hilman <khilman@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] Documentation: ARM: EXYNOS: Describe boot loaders interface
Date: Tue, 16 Jun 2015 16:12:49 -0700 [thread overview]
Message-ID: <7hlhfjw8lq.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1433585151-3627-1-git-send-email-k.kozlowski.k@gmail.com> (Krzysztof Kozlowski's message of "Sat, 6 Jun 2015 19:05:51 +0900")
Krzysztof Kozlowski <k.kozlowski.k@gmail.com> writes:
> Various boot loaders for Exynos based boards use certain memory
> addresses during booting for different purposes. Mostly this is one of
> following :
> 1. as a CPU boot address,
> 2. for storing magic cookie related to low power mode (AFTR, sleep).
>
> The document, based solely on kernel source code, tries to group the
> information scattered over different files. This would help in the
> future when adding support for new SoC or when extending features
> related to low power modes.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Very nice, thank you for taking the time to pull all of this together
into one location.
Kevin
prev parent reply other threads:[~2015-06-16 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 10:05 [PATCH] Documentation: ARM: EXYNOS: Describe boot loaders interface Krzysztof Kozlowski
2015-06-06 11:01 ` Peter Chubb
2015-06-06 11:43 ` Krzysztof Kozłowski
2015-06-08 22:40 ` Jonathan Corbet
2015-06-16 23:12 ` Kevin Hilman [this message]
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=7hlhfjw8lq.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
/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