linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tristan Bastian <tristan-c.bastian@gmx.de>
To: Thierry Reding <thierry.reding@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v2] ARM: tegra: Restore DT ABI on Tegra124 Chromebooks
Date: Mon, 11 Feb 2019 20:44:52 +0000	[thread overview]
Message-ID: <20190211204452.Horde.-B4_UgJoWHc85yxQZVtc9wu@_> (raw)
In-Reply-To: <20190211110919.10388-1-thierry.reding@gmail.com>

Thierry Reding – Mon, 11. February 2019 12:09
> From: Thierry Reding <treding@nvidia.com>
> 
> Commit 482997699ef0 ("ARM: tegra: Fix unit_address_vs_reg DTC warnings
> for /memory") inadventently broke device tree ABI by adding a unit-
> address to the "/memory" node because the device tree compiler flagged
> the missing unit-address as a warning.
> 
> Tegra124 Chromebooks (a.k.a. Nyan) use a bootloader that relies on the
> full name of the memory node in device tree being exactly "/memory". It
> can be argued whether this was a good decision or not, and some other
> bootloaders (such as U-Boot) do accept a unit-address in the name of the
> node, but the device tree is an ABI and we can't break existing setups
> just because the device tree compiler considers it bad practice to omit
> the unit-address nowadays.
> 
> This partially reverts the offending commit and restores device tree ABI
> compatibility.
> 
> Fixes: 482997699ef0 ("ARM: tegra: Fix unit_address_vs_reg DTC warnings for
> /memory")
> Reported-by: Tristan Bastian <tristan-c.bastian@gmx.de>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v2:
> - remove memory@80000000 node pulled in from tegra124.dtsi
> - add device_type = "memory" property
> 
> arch/arm/boot/dts/tegra124-nyan.dtsi | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/tegra124-nyan.dtsi
> b/arch/arm/boot/dts/tegra124-nyan.dtsi
> index d5f11d6d987e..bc85b6a166c7 100644
> --- a/arch/arm/boot/dts/tegra124-nyan.dtsi
> +++ b/arch/arm/boot/dts/tegra124-nyan.dtsi
> @@ -13,10 +13,25 @@
> stdout-path = "serial0:115200n8";
> };
> 
> - memory@80000000 {
> + /*
> + * Note that recent version of the device tree compiler (starting with
> + * version 1.4.2) warn about this node containing a reg property, but
> + * missing a unit-address. However, the bootloader on these Chromebook
> + * devices relies on the full name of this node to be exactly /memory.
> + * Adding the unit-address causes the bootloader to create a /memory
> + * node and write the memory bank configuration to that node, which in
> + * turn leads the kernel to believe that the device has 2 GiB of
> + * memory instead of the amount detected by the bootloader.
> + *
> + * The name of this node is effectively ABI and must not be changed.
> + */
> + memory {
> + device_type = "memory";
> reg = <0x0 0x80000000 0x0 0x80000000>;
> };
> 
> + /delete-node/ memory@80000000;
> +
> host1x@50000000 {
> hdmi@54280000 {
> status = "okay";
> -- 
> 2.19.1

Thanks Thierry

Tristan

Tested-by: Tristan Bastian <tristan-c.bastian@gmx.de>

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

  reply	other threads:[~2019-02-11 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 11:09 [PATCH v2] ARM: tegra: Restore DT ABI on Tegra124 Chromebooks Thierry Reding
2019-02-11 20:44 ` Tristan Bastian [this message]
2019-02-18 15:13   ` Thierry Reding
2019-02-20 15:09     ` Arnd Bergmann

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=20190211204452.Horde.-B4_UgJoWHc85yxQZVtc9wu@_ \
    --to=tristan-c.bastian@gmx.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).