From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <lumag@kernel.org>,
Christopher Obbard <christopher.obbard@linaro.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
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: Tue, 11 Mar 2025 21:41:17 +0100 [thread overview]
Message-ID: <827ca00b-a895-4aab-bd1e-7866df730fef@oss.qualcomm.com> (raw)
In-Reply-To: <vjkdwjudqsgcq2leabscnb2r5dbtztgfq3jlkfowcauslaymkp@qsxnpis3ksp6>
On 3/11/25 7:52 PM, Dmitry Baryshkov wrote:
> On Tue, Mar 11, 2025 at 07:02:56PM +0100, Christopher Obbard wrote:
>> Currently some Qualcomm interconnect drivers are enabled
>> as modules which isn't overly useful since the interconnects
>> are required to be loaded during early boot.
>>
>> Loading the interconnects late (e.g. in initrd or as module)
>> can cause boot issues, such as slowdown or even not booting
>> at all (since the interconnect would be required for storage
>> devices).
>
> This is not a good justification. It should be perfectly fine to load
> block drivers (including their dependencies) from the initramfs.
>
> Up to now we have been enabling only those interconnect (and pinctrl,
> btw) drivers, which are required to be able to open the consoe (thanks,
> systemd).
(non-earlycon) console is a better argument here, though
Konrad
next prev parent reply other threads:[~2025-03-11 20:41 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
2025-03-13 17:34 ` Christopher Obbard
2025-03-11 18:52 ` Dmitry Baryshkov
2025-03-11 20:41 ` Konrad Dybcio [this message]
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=827ca00b-a895-4aab-bd1e-7866df730fef@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christopher.obbard@linaro.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