All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: stable@vger.kernel.org
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone
Date: Mon, 27 Nov 2017 15:33:25 -0800	[thread overview]
Message-ID: <7h8tere1q2.fsf@baylibre.com> (raw)
In-Reply-To: <1507735392-20005-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Wed, 11 Oct 2017 17:23:12 +0200")

Greg,

Neil Armstrong <narmstrong@baylibre.com> writes:

> This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping
> for Meson GXL SoCs and products sold since May 2017 uses this alternate
> reserved memory mapping.
> But products had been sold using the previous mapping.
>
> This issue has been explained in [1] and a dynamic solution is yet to be
> found to avoid loosing another 3Mbytes of reservable memory.
>
> In the meantime, this patch adds this alternate memory zone only for
> the GXL and GXM SoCs since GXBB based new products stopped earlier.
>
> [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004860.html
>
> Fixes: bba8e3f42736 ("ARM64: dts: meson-gx: Add firmware reserved memory zones")
> Reported-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>

I missed the Fixes tag on this one, but it's now commit 4ee8e51b9edf upstream.

Please apply to stable v4.10+

Thanks,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone
Date: Mon, 27 Nov 2017 15:33:25 -0800	[thread overview]
Message-ID: <7h8tere1q2.fsf@baylibre.com> (raw)
In-Reply-To: <1507735392-20005-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Wed, 11 Oct 2017 17:23:12 +0200")

Greg,

Neil Armstrong <narmstrong@baylibre.com> writes:

> This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping
> for Meson GXL SoCs and products sold since May 2017 uses this alternate
> reserved memory mapping.
> But products had been sold using the previous mapping.
>
> This issue has been explained in [1] and a dynamic solution is yet to be
> found to avoid loosing another 3Mbytes of reservable memory.
>
> In the meantime, this patch adds this alternate memory zone only for
> the GXL and GXM SoCs since GXBB based new products stopped earlier.
>
> [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004860.html
>
> Fixes: bba8e3f42736 ("ARM64: dts: meson-gx: Add firmware reserved memory zones")
> Reported-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>

I missed the Fixes tag on this one, but it's now commit 4ee8e51b9edf upstream.

Please apply to stable v4.10+

Thanks,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone
Date: Mon, 27 Nov 2017 15:33:25 -0800	[thread overview]
Message-ID: <7h8tere1q2.fsf@baylibre.com> (raw)
In-Reply-To: <1507735392-20005-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Wed, 11 Oct 2017 17:23:12 +0200")

Greg,

Neil Armstrong <narmstrong@baylibre.com> writes:

> This year, Amlogic updated the ARM Trusted Firmware reserved memory mapping
> for Meson GXL SoCs and products sold since May 2017 uses this alternate
> reserved memory mapping.
> But products had been sold using the previous mapping.
>
> This issue has been explained in [1] and a dynamic solution is yet to be
> found to avoid loosing another 3Mbytes of reservable memory.
>
> In the meantime, this patch adds this alternate memory zone only for
> the GXL and GXM SoCs since GXBB based new products stopped earlier.
>
> [1] http://lists.infradead.org/pipermail/linux-amlogic/2017-October/004860.html
>
> Fixes: bba8e3f42736 ("ARM64: dts: meson-gx: Add firmware reserved memory zones")
> Reported-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>

I missed the Fixes tag on this one, but it's now commit 4ee8e51b9edf upstream.

Please apply to stable v4.10+

Thanks,

Kevin

  parent reply	other threads:[~2017-11-27 23:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 15:23 [PATCH] ARM64: dts: meson-gxl: Add alternate ARM Trusted Firmware reserved memory zone Neil Armstrong
2017-10-11 15:23 ` Neil Armstrong
2017-10-11 15:23 ` Neil Armstrong
2017-10-12  0:24 ` Kevin Hilman
2017-10-12  0:24   ` Kevin Hilman
2017-10-12  0:24   ` Kevin Hilman
2017-10-26 13:50 ` Will Deacon
2017-10-26 13:50   ` Will Deacon
2017-10-26 13:50   ` Will Deacon
2017-11-27 23:33 ` Kevin Hilman [this message]
2017-11-27 23:33   ` Kevin Hilman
2017-11-27 23:33   ` Kevin Hilman
2017-11-28  8:39   ` Greg KH
2017-11-28  8:39     ` Greg KH
2017-11-28  8:39     ` Greg KH

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=7h8tere1q2.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=carlo@caione.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.