From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx7ulp: Pass the CPU 'clock-frequency' property
Date: Mon, 16 Nov 2020 15:33:40 +0800 [thread overview]
Message-ID: <20201116073339.GC5849@dragon> (raw)
In-Reply-To: <20201109194640.16680-1-festevam@gmail.com>
On Mon, Nov 09, 2020 at 04:46:40PM -0300, Fabio Estevam wrote:
> The default i.MX7ULP CPU frequency is 500.21 MHz.
As bootloader may configure the frequency as it like, I'm not sure what
the "default" means here.
>
> Pass the 'clock-frequency' property to avoid the following warning
> message during boot:
>
> [ 0.013005] /cpus/cpu@f00 missing clock-frequency property
To me, this looks like as an useful warning message to bootloaders which
do not fill this property based on the actual running frequency.
Shawn
>
> Fixes: 20434dc92c05 ("ARM: dts: imx: add common imx7ulp dtsi support")
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> arch/arm/boot/dts/imx7ulp.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/imx7ulp.dtsi b/arch/arm/boot/dts/imx7ulp.dtsi
> index b7ea37ad4e55..a7fdc2f41afa 100644
> --- a/arch/arm/boot/dts/imx7ulp.dtsi
> +++ b/arch/arm/boot/dts/imx7ulp.dtsi
> @@ -41,6 +41,7 @@
> compatible = "arm,cortex-a7";
> device_type = "cpu";
> reg = <0xf00>;
> + clock-frequency = <500210526>;
> };
> };
>
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-16 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:46 [PATCH] ARM: dts: imx7ulp: Pass the CPU 'clock-frequency' property Fabio Estevam
2020-11-16 7:33 ` 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=20201116073339.GC5849@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@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).