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, Stefano Babic <sbabic@denx.de>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Tom Rini <trini@konsulko.com>,
Enrico Leto <enrico.leto@siemens.com>,
Heiko Schocher <hs@denx.de>, Peng Fan <peng.fan@nxp.com>,
Yannic Moog <y.moog@phytec.de>,
Gilles Talis <gilles.talis@gmail.com>,
Patrick Barsanti <patrick.barsanti@amarulasolutions.com>,
Ye Li <ye.li@nxp.com>, Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH V3 5/6] imx: imx8: Imply CPU_IMX by default
Date: Sun, 23 Mar 2025 06:09:00 +0100 [thread overview]
Message-ID: <fca93a21-adc9-4261-9756-e88fcf5fc5ce@mailbox.org> (raw)
In-Reply-To: <CAHCN7xLJ0dB3Du62A5pOrAYFjSXnaf=CG-SdLKn4Kfi5csUXpw@mail.gmail.com>
On 3/23/25 1:00 AM, Adam Ford wrote:
> On Sat, Mar 22, 2025 at 6:31 PM Marek Vasut <marek.vasut@mailbox.org> wrote:
>>
>> On 3/22/25 7:38 PM, Adam Ford wrote:
>>> The imx8_cpu driver is a CPU Driver that supports the i.MX8Q
>>> family. When it is enabled, it acts as an alternative to
>>> arch/arm/mach-imx/cpu.c, but the imx8_cpu supports the driver
>>> model where cpu.c does not. Imply this newer driver by default.
>>>
>>> Signed-off-by: Adam Ford <aford173@gmail.com>
>>> ---
>>> arch/arm/mach-imx/imx8/Kconfig | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/arch/arm/mach-imx/imx8/Kconfig b/arch/arm/mach-imx/imx8/Kconfig
>>> index 9a43beda6fa..257c14e61b6 100644
>>> --- a/arch/arm/mach-imx/imx8/Kconfig
>>> +++ b/arch/arm/mach-imx/imx8/Kconfig
>>> @@ -9,6 +9,8 @@ config AHAB_BOOT
>>> config IMX8
>>> bool
>>> select HAS_CAAM
>>> + imply CPU
>>> + imply CPU_IMX
>> Shouldn't CPU_IMX select CPU ?
>
> It does not currently. Right now, it depends on CPU being set. There
> is another Kconfig option for CPU_ARMV8 that also depends on CPU, and
> I would prefer not to change both of them.
Hum, OK, thanks for clarifying.
next prev parent reply other threads:[~2025-03-23 5:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 18:38 [PATCH V3 0/6] Migrate IMX8, IMX8M and IMX9 to use imx8_cpu Adam Ford
2025-03-22 18:38 ` [PATCH V3 1/6] imx: imx9: Imply IMX_TMU Adam Ford
2025-03-22 23:29 ` Marek Vasut
2025-03-22 18:38 ` [PATCH V3 2/6] imx: imx8m: " Adam Ford
2025-03-22 23:29 ` Marek Vasut
2025-03-22 18:38 ` [PATCH V3 3/6] cpu: imx8_cpu: Print Speed grade if IMX_THERMAL or IMX_TMU Adam Ford
2025-03-22 23:30 ` Marek Vasut
2025-03-23 0:03 ` Adam Ford
2025-03-23 5:08 ` Marek Vasut
2025-03-22 18:38 ` [PATCH V3 4/6] imx: imx8m: Imply CPU_IMX by default Adam Ford
2025-03-22 23:30 ` Marek Vasut
2025-03-22 18:38 ` [PATCH V3 5/6] imx: imx8: " Adam Ford
2025-03-22 23:30 ` Marek Vasut
2025-03-23 0:00 ` Adam Ford
2025-03-23 5:09 ` Marek Vasut [this message]
2025-03-22 18:38 ` [PATCH V3 6/6] imx: imx9: " Adam Ford
2025-03-22 23:30 ` Marek Vasut
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=fca93a21-adc9-4261-9756-e88fcf5fc5ce@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=c.stoidner@phytec.de \
--cc=enrico.leto@siemens.com \
--cc=festevam@gmail.com \
--cc=gilles.talis@gmail.com \
--cc=hs@denx.de \
--cc=michael@amarulasolutions.com \
--cc=patrick.barsanti@amarulasolutions.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=w.egorov@phytec.de \
--cc=y.moog@phytec.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