Re: [PATCH 3/4] soc: qcom: Make important drivers default

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 4/29/26 6:10 PM, Krzysztof Kozlowski wrote:
> 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.

There will be a couple arm64 ones too, but due to their age they're on the
back burner.. Whenever Dmitry can get some time for the museum pieces

Konrad