From: Kukjin Kim <kgene@kernel.org>
To: "Emilio López" <emilio.lopez@collabora.co.uk>
Cc: gregkh@linuxfoundation.org, olof@lixom.net, kgene@kernel.org,
k.kozlowski@samsung.com, linux@roeck-us.net,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v3 4/4] ARM: dts: Enable EC vboot context support on Peach boards
Date: Thu, 08 Oct 2015 07:31:05 +0900 [thread overview]
Message-ID: <56159D29.3090801@kernel.org> (raw)
In-Reply-To: <1442842703-5309-5-git-send-email-emilio.lopez@collabora.co.uk>
On 09/21/15 22:38, Emilio López wrote:
> The Peach boards use the EC to store the vboot context information,
> so add the corresponding properties on the EC node to indicate so.
>
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Acked-by: Javier Martinez Canillas <javier@osg.samsung.com>
> Signed-off-by: Emilio López <emilio.lopez@collabora.co.uk>
> ---
>
> Changes from v1:
> - none
>
> Changes from v2:
> - collect tags from Krzysztof & Javier
>
> arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> index 8f4d76c..ac02fb4 100644
> --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts
> +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> @@ -935,6 +935,7 @@
> pinctrl-0 = <&ec_spi_cs &ec_irq>;
> reg = <0>;
> spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>
> controller-data {
> samsung,spi-feedback-delay = <1>;
> diff --git a/arch/arm/boot/dts/exynos5800-peach-pi.dts b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> index 7d5b386..b60dec0 100644
> --- a/arch/arm/boot/dts/exynos5800-peach-pi.dts
> +++ b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> @@ -898,6 +898,7 @@
> pinctrl-0 = <&ec_spi_cs &ec_irq>;
> reg = <0>;
> spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>
> controller-data {
> samsung,spi-feedback-delay = <1>;
Applied, thanks.
- Kukjin
prev parent reply other threads:[~2015-10-07 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 13:38 [PATCH v3 0/4] platform/chrome: vboot context support Emilio López
2015-09-21 13:38 ` [PATCH 1/4] sysfs: Support is_visible() on binary attributes Emilio López
2015-09-21 13:41 ` Emilio López
2015-10-04 18:33 ` Greg KH
2015-10-07 22:08 ` Olof Johansson
2015-09-21 13:38 ` [PATCH v3 2/4] Documentation: bindings: mfd: cros ec: document vbc EC property Emilio López
2015-09-21 15:01 ` Javier Martinez Canillas
2015-09-23 0:34 ` Lee Jones
2015-09-23 14:31 ` Emilio López
2015-09-24 17:21 ` Lee Jones
2015-09-21 13:38 ` [PATCH v3 3/4] platform/chrome: Support reading/writing the vboot context Emilio López
2015-10-07 22:08 ` Olof Johansson
2015-09-21 13:38 ` [PATCH v3 4/4] ARM: dts: Enable EC vboot context support on Peach boards Emilio López
2015-10-07 22:31 ` Kukjin Kim [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=56159D29.3090801@kernel.org \
--to=kgene@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emilio.lopez@collabora.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).