Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christopher Obbard <christopher.obbard@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: 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 09:54:14 +0100	[thread overview]
Message-ID: <78f6091c-1630-48c2-93e6-71f2cdbe63c5@kernel.org> (raw)
In-Reply-To: <20250311-wip-obbardc-qcom-defconfig-interconnects-builtin-v1-1-675b6bc57176@linaro.org>

On 11/03/2025 19:02, 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).
> 
> Be consistent and enable all of the Qualcomm interconnect
> drivers as built-in to the kernel image.


I don't agree. If you want consistency, fix booting process and make
everything module. We switch them to builtin on exception, so come with
reasoning for given exceptions instead of making exceptions the new normal.

Best regards,
Krzysztof

      parent reply	other threads:[~2025-03-12  8:54 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
2025-03-12  8:54 ` Krzysztof Kozlowski [this message]

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=78f6091c-1630-48c2-93e6-71f2cdbe63c5@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christopher.obbard@linaro.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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