All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>,
	Furkan Kardame <furkan@fkardame.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson: add BL32 reserved region to Beelink g12b devices
Date: Mon, 24 Jan 2022 12:02:28 -0800	[thread overview]
Message-ID: <7h7daoyka3.fsf@baylibre.com> (raw)
In-Reply-To: <20220122073221.2398-1-christianshewitt@gmail.com>

Christian Hewitt <christianshewitt@gmail.com> writes:

> This resolves a long-running issue where Beelink GT-King/Pro and
> GS-King-X wedge on boot or shortly after when booting from vendor
> u-boot. In some distros the issue is often reported as triggered
> by large file transfers to/from USB or SD cards. Reserving the
> BL32 memory region prevents the issue.

The BL32 is typically common for the SoC family, so this change should
probably go into the g12b.dtsi.  Or probably even
meson-g12-common.dtsi, which is where the BL31 reserved-memory is
described.

Kevin



_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>,
	Furkan Kardame <furkan@fkardame.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson: add BL32 reserved region to Beelink g12b devices
Date: Mon, 24 Jan 2022 12:02:28 -0800	[thread overview]
Message-ID: <7h7daoyka3.fsf@baylibre.com> (raw)
In-Reply-To: <20220122073221.2398-1-christianshewitt@gmail.com>

Christian Hewitt <christianshewitt@gmail.com> writes:

> This resolves a long-running issue where Beelink GT-King/Pro and
> GS-King-X wedge on boot or shortly after when booting from vendor
> u-boot. In some distros the issue is often reported as triggered
> by large file transfers to/from USB or SD cards. Reserving the
> BL32 memory region prevents the issue.

The BL32 is typically common for the SoC family, so this change should
probably go into the g12b.dtsi.  Or probably even
meson-g12-common.dtsi, which is where the BL31 reserved-memory is
described.

Kevin



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>,
	Furkan Kardame <furkan@fkardame.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson: add BL32 reserved region to Beelink g12b devices
Date: Mon, 24 Jan 2022 12:02:28 -0800	[thread overview]
Message-ID: <7h7daoyka3.fsf@baylibre.com> (raw)
In-Reply-To: <20220122073221.2398-1-christianshewitt@gmail.com>

Christian Hewitt <christianshewitt@gmail.com> writes:

> This resolves a long-running issue where Beelink GT-King/Pro and
> GS-King-X wedge on boot or shortly after when booting from vendor
> u-boot. In some distros the issue is often reported as triggered
> by large file transfers to/from USB or SD cards. Reserving the
> BL32 memory region prevents the issue.

The BL32 is typically common for the SoC family, so this change should
probably go into the g12b.dtsi.  Or probably even
meson-g12-common.dtsi, which is where the BL31 reserved-memory is
described.

Kevin



  parent reply	other threads:[~2022-01-24 20:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  7:32 [PATCH 0/3] arm64: dts: meson: add BL32 reserved region to Beelink g12b devices Christian Hewitt
2022-01-22  7:32 ` Christian Hewitt
2022-01-22  7:32 ` Christian Hewitt
2022-01-22  7:32 ` [PATCH 1/3] arm64: dts: meson: add BL32 reserved-memory region to GT-King Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-22  7:32 ` [PATCH 2/3] arm64: dts: meson: add BL32 reserved-memory region to GT-King Pro Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-22  7:32 ` [PATCH 3/3] arm64: dts: meson: add BL32 reserved-memory region to GS-King-X Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-22  7:32   ` Christian Hewitt
2022-01-24 20:02 ` Kevin Hilman [this message]
2022-01-24 20:02   ` [PATCH 0/3] arm64: dts: meson: add BL32 reserved region to Beelink g12b devices Kevin Hilman
2022-01-24 20:02   ` Kevin Hilman
2022-01-25  4:03   ` Christian Hewitt
2022-01-25  4:03     ` Christian Hewitt
2022-01-25  4:03     ` Christian Hewitt
     [not found]   ` <C8B4EA0E-6593-4C42-B116-F9C043D29452@gmail.com>
2022-01-25 15:01     ` Neil Armstrong
2022-01-25 15:01       ` Neil Armstrong
2022-01-25 15:01       ` Neil Armstrong

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=7h7daoyka3.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=christianshewitt@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=furkan@fkardame.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=narmstrong@baylibre.com \
    --cc=robh+dt@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.