From: Shawn Guo <shawnguo@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: devicetree@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH] arm64: dts: fix node name for the sysclk
Date: Wed, 14 Jul 2021 10:29:44 +0800 [thread overview]
Message-ID: <20210714022943.GC31370@dragon> (raw)
In-Reply-To: <20210608112658.4087235-1-olteanv@gmail.com>
On Tue, Jun 08, 2021 at 02:26:58PM +0300, Vladimir Oltean wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> U-Boot attempts to fix up the "clock-frequency" property of the "/sysclk" node:
> https://elixir.bootlin.com/u-boot/v2021.04/source/arch/arm/cpu/armv8/fsl-layerscape/fdt.c#L512
>
> but fails to do so:
>
> ## Booting kernel from Legacy Image at a1000000 ...
> Image Name:
> Created: 2021-06-08 10:31:38 UTC
> Image Type: AArch64 Linux Kernel Image (gzip compressed)
> Data Size: 15431370 Bytes = 14.7 MiB
> Load Address: 80080000
> Entry Point: 80080000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at a0000000
> Booting using the fdt blob at 0xa0000000
> Uncompressing Kernel Image
> Loading Device Tree to 00000000fbb19000, end 00000000fbb22717 ... OK
> Unable to update property /sysclk:clock-frequency, err=FDT_ERR_NOTFOUND
>
> Starting kernel ...
>
> All Layerscape SoCs except LS1028A use "sysclk" as the node name, and
> not "clock-sysclk". So change the node name of LS1028A accordingly.
>
> Fixes: 8897f3255c9c ("arm64: dts: Add support for NXP LS1028A SoC")
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2021-07-14 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 11:26 [PATCH] arm64: dts: fix node name for the sysclk Vladimir Oltean
2021-06-08 11:31 ` Vladimir Oltean
2021-06-12 7:53 ` Shawn Guo
2021-06-14 14:51 ` Vladimir Oltean
2021-07-14 2:29 ` Shawn Guo [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=20210714022943.GC31370@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vladimir.oltean@nxp.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).