From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Fabio Estevam" <festevam@gmail.com>,
"Marek Vasut" <marex@denx.de>, "Peng Fan" <peng.fan@nxp.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
"João Paulo Gonçalves" <joao.goncalves@toradex.com>
Subject: Re: [PATCH v1] arm64: defconfig: Enable i.MX95 configs for booting and Ethernet
Date: Thu, 23 Oct 2025 14:22:40 +0200 [thread overview]
Message-ID: <cacc9439-2cf0-42bd-b6c5-13d1e75642d8@linaro.org> (raw)
In-Reply-To: <20251023-upstream-imx95-smarc-defconfig-v1-1-62c6e6f5b315@toradex.com>
On 23/10/2025 14:19, João Paulo Gonçalves wrote:
> 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
These do not carry any IMX95 compatibles, so I have doubts you described
the issue correctly. You claim that SoC needs them, not the board.
> * CONFIG_PINCTRL_IMX_SCMI for the pinctrl driver> * CONFIG_CLK_IMX95_BLK_CTL for the shared hardware domain controller
BTW standard comment applies - explain which upstream boards have all these.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-23 12:22 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 [this message]
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
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=cacc9439-2cf0-42bd-b6c5-13d1e75642d8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--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).