From: Brian Masney <bmasney@redhat.com>
To: Christopher Obbard <christopher.obbard@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm interconnects as built-in
Date: Wed, 12 Mar 2025 15:40:35 -0400 [thread overview]
Message-ID: <Z9HjMyjzE9XlqrEj@x1> (raw)
In-Reply-To: <CACr-zFCYWEFPO8yExp_8hOQdVtC9Zwu1ZOZNksSeyyS6Ht0e9A@mail.gmail.com>
Hi Christopher,
On Wed, Mar 12, 2025 at 12:10:56PM +0100, Christopher Obbard wrote:
> For reference, I am working on updating initramfs generation tools in
> Debian/Fedora to include the required interconnect modules. Currently
> the interconnect drivers are built as modules in these distros, but
> are not included in the initrd. That is where my confusion initially
> stemmed from.
From a Fedora and centos-stream-9/10 perspective, we have dracut
updated so that the interconnect modules are included in the initramfs
by default.
https://github.com/dracutdevs/dracut/blob/master/modules.d/90kernel-modules/module-setup.sh#L74
Let me know if you are seeing a specific issue with the initramfs on
Fedora and I can help you.
We also configured all of the QC pinctrl drivers to be modules in
Fedora, and this causes a large number of probe deferrals on boot up.
One of the boots I measured was about a half second:
https://lore.kernel.org/linux-embedded/Z6J3WpeJKIKENC81@x13s/
Everything eventually loads and works as expected though. The upstream
defconfig configures most of the pinctrl drivers to be built in for
Qualcomm.
Brian
next prev parent reply other threads:[~2025-03-12 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 18:02 [PATCH] arm64: defconfig: Enable Qualcomm interconnects as built-in Christopher Obbard
2025-03-11 18:10 ` Christopher Obbard
2025-03-11 18:57 ` Dmitry Baryshkov
2025-03-11 19:15 ` Christopher Obbard
2025-03-12 8:56 ` Krzysztof Kozlowski
2025-03-12 11:10 ` Christopher Obbard
2025-03-12 11:34 ` Krzysztof Kozlowski
2025-03-12 15:28 ` Christopher Obbard
2025-03-12 19:40 ` Brian Masney [this message]
2025-03-13 17:34 ` Christopher Obbard
2025-03-11 18:52 ` Dmitry Baryshkov
2025-03-11 20:41 ` Konrad Dybcio
2025-03-12 8:54 ` 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=Z9HjMyjzE9XlqrEj@x1 \
--to=bmasney@redhat.com \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christopher.obbard@linaro.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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