[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <accb4814-4826-ff97-3527-4e3fbadcd4ff@linaro.org>
Date: Sat, 16 Sep 2023 22:32:04 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Georgi Djakov <djakov@...nel.org>,
Trilok Soni <quic_tsoni@...cinc.com>,
Tengfei Fan <quic_tengfan@...cinc.com>, will@...nel.org,
robin.murphy@....com, joro@...tes.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
catalin.marinas@....com
Cc: geert+renesas@...der.be, arnd@...db.de, neil.armstrong@...aro.org,
nfraprado@...labora.com, rafal@...ecki.pl, peng.fan@....com,
linux-arm-kernel@...ts.infradead.org, iommu@...ts.linux.dev,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, quic_shashim@...cinc.com,
quic_kaushalk@...cinc.com, quic_tdas@...cinc.com,
quic_tingweiz@...cinc.com, quic_aiquny@...cinc.com,
kernel@...cinc.com
Subject: Re: [PATCH v2 8/8] arm64: defconfig: enable interconnect and pinctrl
for SM4450
On 16/09/2023 17:13, Georgi Djakov wrote:
>
>>
>> Complete list here, and it is inconsistent. Latest 8550 is also =y. Do we document
>> the reasons somewhere on why they are added as =y?
>>
>> CONFIG_INTERCONNECT_QCOM=y
>> CONFIG_INTERCONNECT_QCOM_MSM8916=m
>> CONFIG_INTERCONNECT_QCOM_MSM8996=m
>> CONFIG_INTERCONNECT_QCOM_OSM_L3=m
>> CONFIG_INTERCONNECT_QCOM_QCM2290=m
>> CONFIG_INTERCONNECT_QCOM_QCS404=m
>> CONFIG_INTERCONNECT_QCOM_SA8775P=y
>> CONFIG_INTERCONNECT_QCOM_SC7180=y
>> CONFIG_INTERCONNECT_QCOM_SC7280=y
>> CONFIG_INTERCONNECT_QCOM_SC8180X=y
>> CONFIG_INTERCONNECT_QCOM_SC8280XP=y
>> CONFIG_INTERCONNECT_QCOM_SDM845=y
>> CONFIG_INTERCONNECT_QCOM_SM8150=m
>> CONFIG_INTERCONNECT_QCOM_SM8250=m
>> CONFIG_INTERCONNECT_QCOM_SM8350=m
>> CONFIG_INTERCONNECT_QCOM_SM8450=y
>> CONFIG_INTERCONNECT_QCOM_SM8550=y
>
> If the device can boot (to console/initramfs) with =m, we go with that.
> But if something critical like the UART depends on the interconnect
> provider, then we make it built-in.
>
> On SM8550 for example, we have enabled bandwidth scaling support for QUP
> and that's why it needs to be =y.
>
> It looks like on SM4450 this should be =y too.
I asked why SM4450 has to be =y and there was no answer. The argument
that SM8450 is a module, is not applicable.
Best regards,
Krzysztof
Powered by blists - more mailing lists