From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v2 12/12] arm64: defconfig: build in OCOTP ELE
Date: Fri, 19 Apr 2024 15:43:04 +0200 [thread overview]
Message-ID: <0dfc402a-ee31-404f-9dc2-8828d7a6b337@kernel.org> (raw)
In-Reply-To: <20240419-imx93-dts-4-13-v2-12-9076e1d7d399@nxp.com>
On 19/04/2024 05:37, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> The FEC network driver is built in, with OCOTP ELE built as module,
> the FEC drive will defer probe because nvmem provider not ready and
> nfsboot not work. So build in OCOTP ELE driver.
That's not an explanation. FEC can defer and probe immediately, that's
not a problem. Just use ramdisk.
No, this stays as module. Fix your system instead.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-19 13:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 3:36 [PATCH v2 00/12] arm64: dts: imx93: various update Peng Fan (OSS)
2024-04-19 3:36 ` [PATCH v2 01/12] arm64: dts: imx93: use FSL_EDMA_RX for rx channel Peng Fan (OSS)
2024-04-19 14:26 ` Frank Li
2024-04-19 3:36 ` [PATCH v2 02/12] arm64: dts: imx93: add dma support for lpi2c[1..8] Peng Fan (OSS)
2024-04-19 14:27 ` Frank Li
2024-04-19 3:36 ` [PATCH v2 03/12] arm64: dts: imx93: add dma support for lpspi[1..8] Peng Fan (OSS)
2024-04-19 14:28 ` Frank Li
2024-04-19 3:36 ` [PATCH v2 04/12] arm64: dts: imx93: assign usdhc[1..3] root clock to 400MHz Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 05/12] arm64: dts: imx93: add nvmem property for fec1 Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 06/12] arm64: dts: imx93: add nvmem property for eqos Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 07/12] arm64: dts: imx93-11x11-evk: update resource table address Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 08/12] arm64: dts: imx93-11x11-evk: add sleep pinctrl for eqos and fec Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 09/12] arm64: dts: imx93-11x11-evk: add different usdhc pinctrl for different timing usage Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 10/12] arm64: dts: imx93-11x11-evk: add sleep pinctrl for sdhc2 Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 11/12] arm64: dts: imx93-11x11-evk: add reset gpios for ethernet PHYs Peng Fan (OSS)
2024-04-19 3:37 ` [PATCH v2 12/12] arm64: defconfig: build in OCOTP ELE Peng Fan (OSS)
2024-04-19 13:43 ` Krzysztof Kozlowski [this message]
2024-04-22 2:07 ` Peng Fan
2024-04-22 6:17 ` [PATCH v2 00/12] arm64: dts: imx93: various update Peng Fan
2024-04-25 7:03 ` Shawn Guo
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=0dfc402a-ee31-404f-9dc2-8828d7a6b337@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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