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 2/4] soc: qcom: Restrict drivers per ARM/ARM64
Date: Wed, 29 Apr 2026 11:10:24 +0200	[thread overview]
Message-ID: <4f2d364c-6e36-4678-b01d-e5d0924c9a78@oss.qualcomm.com> (raw)
In-Reply-To: <527a434e-5ac6-4a79-91e7-bf8bac4adb84@oss.qualcomm.com>

On 29/04/2026 11:03, Konrad Dybcio wrote:
> On 4/29/26 10:56 AM, Krzysztof Kozlowski wrote:
>> There is no point to allow selecting core SoC drivers for Qualcomm ARMv7
>> SoCs when building ARM64 kernel, and vice versa.
>>
>> This makes kernel configuration more difficult as many do not remember
>> the Qualcomm SoCs model names/numbers and their properties like
>> architecture.  No features should be lost because:
>> 1. There won't be a single image for ARMv7 and ARMv8/9 SoCs.
>> 2. Newer ARMv8/9 SoCs won't be running in arm32 emulation mode.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>> ---
> 
> [...]
> 
>>  drivers/soc/qcom/Kconfig | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
>> index 62ce1c67d684..9a050ba1dbcb 100644
>> --- a/drivers/soc/qcom/Kconfig
>> +++ b/drivers/soc/qcom/Kconfig
>> @@ -19,6 +19,7 @@ config QCOM_AOSS_QMP
>>  	tristate "Qualcomm AOSS Driver"
>>  	depends on MAILBOX
>>  	depends on COMMON_CLK && PM
>> +	depends on ARM64 || COMPILE_TEST
> 
> SDX65

Ack, although not in upstream DTS.

> 
>>  	select PM_GENERIC_DOMAINS
>>  	help
>>  	  This driver provides the means of communicating with and controlling
>> @@ -37,6 +38,7 @@ config QCOM_COMMAND_DB
>>  
>>  config QCOM_GENI_SE
>>  	tristate "QCOM GENI Serial Engine Driver"
>> +	depends on ARM64 || COMPILE_TEST
> 
> OK
> 
>>  	help
>>  	  This driver is used to manage Generic Interface (GENI) firmware based
>>  	  Qualcomm Technologies, Inc. Universal Peripheral (QUP) Wrapper. This
>> @@ -45,6 +47,7 @@ config QCOM_GENI_SE
>>  
>>  config QCOM_GSBI
>>  	tristate "QCOM General Serial Bus Interface"
>> +	depends on ARM || COMPILE_TEST
> 
> OK
> 
>>  	select MFD_SYSCON
>>  	help
>>  	  Say y here to enable GSBI support.  The GSBI provides control
>> @@ -53,6 +56,7 @@ config QCOM_GSBI
>>  
>>  config QCOM_LLCC
>>  	tristate "Qualcomm Technologies, Inc. LLCC driver"
>> +	depends on ARM64 || COMPILE_TEST
> 
> SDX65

Ack

> 
>>  	select REGMAP_MMIO
>>  	help
>>  	  Qualcomm Technologies, Inc. platform specific
>> @@ -108,6 +112,7 @@ config QCOM_PMIC_GLINK
>>  	depends on DRM
>>  	depends on NET
>>  	depends on OF
>> +	depends on ARM64 || COMPILE_TEST
> 
> Probably OK?
> 
>>  	select AUXILIARY_BUS
>>  	select QCOM_PDR_HELPERS
>>  	select DRM_AUX_HPD_BRIDGE
>> @@ -242,6 +247,7 @@ config QCOM_APR
>>  	tristate "Qualcomm APR/GPR Bus (Asynchronous/Generic Packet Router)"
>>  	depends on RPMSG
>>  	depends on NET
>> +	depends on ARM64 || COMPILE_TEST
> 
> This I think goes back to <2012 SoCs

It could, but there is no upstream DTS in arm32. It is however in few
old like 8916 which might be running in arm32 mode, so I guess better to
drop it.

> 
>>  	select QCOM_PDR_HELPERS
>>  	help
>>  	  Enable APR IPC protocol support between
>> @@ -251,6 +257,7 @@ config QCOM_APR
>>  
>>  config QCOM_ICC_BWMON
>>  	tristate "QCOM Interconnect Bandwidth Monitor driver"
>> +	depends on ARM64 || COMPILE_TEST
> 
> This is OK currently, some arm32 targets have an older (unsupported today)
> BWMON, I don't know if they would be using the same driver or not

They would get their own compatible, thus driver would be changed.  The
depends here is for current driver.

> 
>>  	select PM_OPP
>>  	select REGMAP_MMIO
>>  	help
>> @@ -265,6 +272,7 @@ config QCOM_ICC_BWMON
>>  
>>  config QCOM_PBS
>>  	tristate "PBS trigger support for Qualcomm Technologies, Inc. PMICS"
>> +	depends on ARM64 || COMPILE_TEST
> 
> MSM8909+PM660 exists and makes use of that

Well, not in upstream, but I get your point.

> 
> Konrad


Best regards,
Krzysztof


  reply	other threads:[~2026-04-29  9:10 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 [this message]
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
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=4f2d364c-6e36-4678-b01d-e5d0924c9a78@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