public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] soc: qcom: Make important drivers default
Date: Wed, 29 Apr 2026 18:10:59 +0200	[thread overview]
Message-ID: <bf37cdd6-b863-4e59-9459-3247080955a9@oss.qualcomm.com> (raw)
In-Reply-To: <48c84ad0-7d6b-4e2e-8bd3-511ec679462e@oss.qualcomm.com>

On 29/04/2026 11:06, Konrad Dybcio wrote:
> On 4/29/26 10:56 AM, Krzysztof Kozlowski wrote:
>> The drivers for Qualcomm SoC components are covering a basic or
>> fundamental SoC blocks.  Usually they are required for booting or to
>> achieve basic expected functionality when running Linux.  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'.
>>
>> Switch most of the Qualcomm SoC drivers to a default 'yes' or
>> 'module' for ARCH_QCOM, to match existing defconfig usage.
>>
>> This has no impact on arm64 defconfig, arm qcom_defconfig and arm
>> multi_v7_defconfig.
>>
>> The change will however enable by default all drivers for arm or arm64
>> COMPILE_TEST builds, whenever ARCH_QCOM is selected, which feels
>> logical: if one selects ARCH_QCOM then probably by default wants to
>> build test it entirely.  Kernels with COMPILE_TEST are not supposed to
>> be used for booting.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>> ---
> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> 
> Please also add:
> 
> QCOM_RMTFS_MEM (required for modem)

It's in the patch.

> QCOM_SPM (cpufreq-adjacent on some platforms)

I assume only for arm, because none of arm64 compatibles are present in
upstream DTS.

> 
> Konrad


Best regards,
Krzysztof


  reply	other threads:[~2026-04-29 16:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  8:56 [PATCH 0/4] soc: qcom: Kconfig improvements Krzysztof Kozlowski
2026-04-29  8:56 ` [PATCH 1/4] soc: qcom: Hide all drivers behind selectable menu Krzysztof Kozlowski
2026-04-29  9:28   ` Konrad Dybcio
2026-04-29 15:30     ` Krzysztof Kozlowski
2026-04-29  8:56 ` [PATCH 2/4] soc: qcom: Restrict drivers per ARM/ARM64 Krzysztof Kozlowski
2026-04-29  9:03   ` Konrad Dybcio
2026-04-29  9:10     ` Krzysztof Kozlowski
2026-04-29  8:56 ` [PATCH 3/4] soc: qcom: Make important drivers default Krzysztof Kozlowski
2026-04-29  9:06   ` Konrad Dybcio
2026-04-29 16:10     ` Krzysztof Kozlowski [this message]
2026-04-29  8:56 ` [PATCH 4/4] ARM: defconfig: qcom: Drop Qualcomm SoC drivers with defaults 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=bf37cdd6-b863-4e59-9459-3247080955a9@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=andersson@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 \
    /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