From: Marek Vasut <marek.vasut@mailbox.org>
To: Adam Ford <aford173@gmail.com>
Cc: u-boot@lists.denx.de, aford@beaconembedded.com,
festevam@gmail.com, Tom Rini <trini@konsulko.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Simon Glass <sjg@chromium.org>, Sean Anderson <seanga2@gmail.com>,
Sumit Garg <sumit.garg@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>, Ye Li <ye.li@nxp.com>,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH 1/4] cpu: imx8_cpu: Print Speed grade if IMX_THERMAL or IMX_TMU
Date: Wed, 19 Mar 2025 23:41:29 +0100 [thread overview]
Message-ID: <2ea44bda-b228-464d-8cb4-269e52b33a18@mailbox.org> (raw)
In-Reply-To: <CAHCN7xJUgRZJ6AzXYS1xdf0nVgK0s0t0Y7bRga5miUYxzCYmEg@mail.gmail.com>
On 3/19/25 8:13 PM, Adam Ford wrote:
> On Tue, Mar 18, 2025 at 9:13 PM Marek Vasut <marek.vasut@mailbox.org> wrote:
>>
>> On 3/19/25 2:42 AM, Adam Ford wrote:
>>> Much of the data that is display by imx8_cpu.c is also
>>> displayed from arch/arm/mach-imx/cpu.c, except the
>>> speed grade and temperature unless the SoC is an i.MX9.
>>> Expand this to include checks for IMX_THERMAL or IMX_TMU
>>> in the same way it's done for mach-imx/cpu.c.
>>>
>>> Before:
>>> CPU: NXP i.MX8MP Rev1.1 A53 at 1200 MHz
>>> Model: Beacon EmbeddedWorks i.MX8MPlus Development kit
>>>
>>> After:
>>> CPU: NXP i.MX8MP Rev1.1 A53 at 1200 MHz
>>> CPU: Industrial temperature grade (-40C to 105C) at 28C
>>> Model: Beacon EmbeddedWorks i.MX8MPlus Development kit
>>>
>>> Signed-off-by: Adam Ford <aford173@gmail.com>
>>>
>>> diff --git a/drivers/cpu/imx8_cpu.c b/drivers/cpu/imx8_cpu.c
>>> index 53d31b3c0bf..facd561022f 100644
>>> --- a/drivers/cpu/imx8_cpu.c
>>> +++ b/drivers/cpu/imx8_cpu.c
>>> @@ -177,7 +177,9 @@ static int cpu_imx_get_desc(const struct udevice *dev, char *buf, int size)
>>> ret = snprintf(buf, size, "NXP i.MX%s Rev%s %s at %u MHz",
>>> plat->type, plat->rev, plat->name, plat->freq_mhz);
>>>
>>> - if (IS_ENABLED(CONFIG_IMX9)) {
>>> + if (IS_ENABLED(CONFIG_IMX9) ||
>>> + IS_ENABLED(CONFIG_IMX_THERMAL) ||
>>> + IS_ENABLED(CONFIG_IMX_TMU)) {
>>
>> Can CONFIG_IMX9 instead select CONFIG_IMX_THERMAL or CONFIG_IMX_TMU , so
>> the SoC specific check could be removed from here ?
>
> Any idea which of IMX_THERMAL or IMX_TMU should be selected or
> implied? I don't have an IMX9 to test.
git grep says:
drivers/thermal/imx_tmu.c: { .compatible = "fsl,imx93-tmu", .data =
FLAGS_VER4, },
prev parent reply other threads:[~2025-03-19 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 1:42 [PATCH 1/4] cpu: imx8_cpu: Print Speed grade if IMX_THERMAL or IMX_TMU Adam Ford
2025-03-19 1:42 ` [PATCH 2/4] arm64: imx: imx8mm-beacon: Enable CPU_IMX Adam Ford
2025-03-19 1:42 ` [PATCH 3/4] arm64: imx: imx8mn-beacon: " Adam Ford
2025-03-19 1:42 ` [PATCH 4/4] arm64: imx: imx8mp-beacon: " Adam Ford
2025-03-19 2:13 ` [PATCH 1/4] cpu: imx8_cpu: Print Speed grade if IMX_THERMAL or IMX_TMU Marek Vasut
2025-03-19 19:13 ` Adam Ford
2025-03-19 22:41 ` Marek Vasut [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=2ea44bda-b228-464d-8cb4-269e52b33a18@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=festevam@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michael@amarulasolutions.com \
--cc=peng.fan@nxp.com \
--cc=quentin.schulz@cherry.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ye.li@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