imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
	linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, imx@lists.linux.dev,
	"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
	"João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>
Subject: Re: [PATCH v1] arm64: defconfig: Enable i.MX95 configs for booting and Ethernet
Date: Thu, 23 Oct 2025 17:53:06 +0200	[thread overview]
Message-ID: <07aba8d4-533d-40f7-bcd3-548704d7d228@mailbox.org> (raw)
In-Reply-To: <00555ed7-1aee-459a-ae60-0242809d7b85@linaro.org>

On 10/23/25 5:32 PM, Krzysztof Kozlowski wrote:
> On 23/10/2025 17:27, Marek Vasut wrote:
>> On 10/23/25 5:22 PM, Krzysztof Kozlowski wrote:
>>> On 23/10/2025 16:03, Alexander Stein wrote:
>>>> Hi,
>>>>
>>>> Am Donnerstag, 23. Oktober 2025, 14:19:15 CEST schrieb João Paulo Gonçalves:
>>>>> From: João Paulo Gonçalves <joao.goncalves@toradex.com>
>>>>>
>>>>> Enable the necessary missing configs for the i.MX95 to boot and also
>>>>> have Ethernet working:
>>>>>
>>>>> * CONFIG_NXP_ENETC4 for the network controller driver
>>>>> * CONFIG_NXP_NETC_BLK_CTRL for the NETC hardware domain controller
>>>>> * CONFIG_PINCTRL_IMX_SCMI for the pinctrl driver
>>>>> * CONFIG_CLK_IMX95_BLK_CTL for the shared hardware domain controller
>>>>>
>>>>> Signed-off-by: João Paulo Gonçalves <joao.goncalves@toradex.com>
>>>>> ---
>>>>>    arch/arm64/configs/defconfig | 4 ++++
>>>>>    1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>>>>> index e3a2d37bd10423b028f59dc40d6e8ee1c610d6b8..787d3ae3f5afeac486a905e0943e7b0e1dcee3a9 100644
>>>>> --- a/arch/arm64/configs/defconfig
>>>>> +++ b/arch/arm64/configs/defconfig
>>>>> @@ -354,8 +354,10 @@ CONFIG_FSL_FMAN=y
>>>>>    CONFIG_FSL_DPAA_ETH=y
>>>>>    CONFIG_FSL_DPAA2_ETH=y
>>>>>    CONFIG_FSL_ENETC=y
>>>>> +CONFIG_NXP_ENETC4=m
>>>>>    CONFIG_FSL_ENETC_VF=y
>>>>>    CONFIG_FSL_ENETC_QOS=y
>>>>> +CONFIG_NXP_NETC_BLK_CTRL=m
>>>>
>>>> Are you sure this should be module? Shouldn't NFS boot be supported by
>>>> default? I might be wring here though.
>>>
>>>
>>> NFS root is supported already with this being module. Yes, it must be a
>>> module, cannot be built in.
>> It seems I am using it as built-in on MX95 Verdin (patch is posted on
>> the ML), and yes, I do boot from NFS root without any initrd/initramfs.
>> It has to be built-in for that use case to work.
> 
> 
> Every arm64 platform is supposed to use initramfs and we already use all
> over the place.

Shouldn't the platform also be at least bootable with the defconfig ? If 
yes, then initramfs is a mandatory requirement for a NFS root boot (not 
a ... supposed to ... optional one), which does not seem to be the case 
until now.

I would argue the ethernet MAC support should be built-in to achieve 
maximum utility with the defconfig.

  reply	other threads:[~2025-10-23 15:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23 12:19 [PATCH v1] arm64: defconfig: Enable i.MX95 configs for booting and Ethernet João Paulo Gonçalves
2025-10-23 12:22 ` Krzysztof Kozlowski
2025-10-23 16:20   ` João Paulo Gonçalves
2025-10-23 14:03 ` Alexander Stein
2025-10-23 15:22   ` Krzysztof Kozlowski
2025-10-23 15:27     ` Marek Vasut
2025-10-23 15:32       ` Krzysztof Kozlowski
2025-10-23 15:53         ` Marek Vasut [this message]
2025-10-23 16:01           ` Krzysztof Kozlowski
2025-10-23 20:05             ` Marek Vasut
2025-10-23 20:16               ` Krzysztof Kozlowski

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=07aba8d4-533d-40f7-bcd3-548704d7d228@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=catalin.marinas@arm.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joao.goncalves@toradex.com \
    --cc=jpaulo.silvagoncalves@gmail.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=shawnguo@kernel.org \
    --cc=will@kernel.org \
    /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).