From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] interconnect: qcom: Make important drivers default
Date: Fri, 15 May 2026 13:11:30 +0200 [thread overview]
Message-ID: <720715a0-eb4f-4083-a67f-aa380e130d6c@oss.qualcomm.com> (raw)
In-Reply-To: <02578386-a492-4342-95aa-9cfb00c8bacd@oss.qualcomm.com>
On 15/05/2026 12:54, Konrad Dybcio wrote:
> On 4/29/26 5:09 PM, Krzysztof Kozlowski wrote:
>> On 29/04/2026 11:23, Konrad Dybcio wrote:
>>> On 4/28/26 7:32 PM, Krzysztof Kozlowski wrote:
>>>> The interconnect drivers for Qualcomm SoC Network-on-Chip are covering a
>>>> basic or fundamental SoC feature: bandwidth management between internal
>>>> SoC blocks. SoC can boot without these, but power management or
>>>> performance will be affected. These drivers do not represent any sort
>>>> of buses visible to the board designers/configurators, thus they should
>>>> be always enabled, regardless how SoC is used in the final board.
>>>>
>>>> Kernel configuration should not ask users choice of drivers when that
>>>> choice is obvious and known to the developers that answer should be
>>>> 'yes' or 'module'.
>>>
>>> I'd say let's make them all `default ARCH_QCOM` - all of these drivers
>>> are required to boot (minus the OSM_L3 driver which is "only" highly
>>> desired, so that your CPU's bus isn't heavily bottlenecked)
>>
>> So the few of them should not be a module? That's what you want to say?
>
> I'm saying that if you only want to shoot yourself in the foot and not
> in the face, you can make them modules
>
> But the L3 driver is required to make the caches run at a reasonable
> speed, so that they don't bottleneck the rest of the system's mem
> bandwidth
okidoki, so I will mark all as default built-in as you said, including
the OSM_L3, based on your explanation.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-15 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 17:32 [PATCH 0/3] interconnect: qcom: Some defconfig/defaults cleanups and improvements Krzysztof Kozlowski
2026-04-28 17:32 ` [PATCH 1/3] interconnect: qcom: Fix indentation Krzysztof Kozlowski
2026-04-28 17:32 ` [PATCH 2/3] interconnect: qcom: Restrict drivers per ARM/ARM64 Krzysztof Kozlowski
2026-04-29 9:21 ` Konrad Dybcio
2026-04-28 17:32 ` [PATCH 3/3] interconnect: qcom: Make important drivers default Krzysztof Kozlowski
2026-04-29 9:23 ` Konrad Dybcio
2026-04-29 15:09 ` Krzysztof Kozlowski
2026-05-15 10:54 ` Konrad Dybcio
2026-05-15 11:11 ` Krzysztof Kozlowski [this message]
2026-05-15 11:12 ` Konrad Dybcio
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=720715a0-eb4f-4083-a67f-aa380e130d6c@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=djakov@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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