From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Georgi Djakov <djakov@kernel.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Tengfei Fan <quic_tengfan@quicinc.com>,
will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, catalin.marinas@arm.com
Cc: geert+renesas@glider.be, arnd@arndb.de,
neil.armstrong@linaro.org, nfraprado@collabora.com,
rafal@milecki.pl, peng.fan@nxp.com,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_shashim@quicinc.com,
quic_kaushalk@quicinc.com, quic_tdas@quicinc.com,
quic_tingweiz@quicinc.com, quic_aiquny@quicinc.com,
kernel@quicinc.com
Subject: Re: [PATCH v2 8/8] arm64: defconfig: enable interconnect and pinctrl for SM4450
Date: Sat, 16 Sep 2023 22:32:04 +0200 [thread overview]
Message-ID: <accb4814-4826-ff97-3527-4e3fbadcd4ff@linaro.org> (raw)
In-Reply-To: <e30870d5-a0cc-4210-a2b0-c7621ea5ecfa@kernel.org>
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
next prev parent reply other threads:[~2023-09-16 20:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 2:15 [PATCH v2 0/8] soc: qcom: Add uart console support for SM4450 Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 1/8] dt-bindings: firmware: document Qualcomm SM4450 SCM Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 4/8] dt-bindings: arm-smmu: Add compatible for SM4450 SoC Tengfei Fan
2023-09-15 7:11 ` Krzysztof Kozlowski
2023-09-15 7:15 ` Tengfei Fan
2023-09-15 9:10 ` Krzysztof Kozlowski
2023-09-15 8:52 ` Tengfei Fan
2023-09-15 9:10 ` Krzysztof Kozlowski
2023-09-15 2:15 ` [PATCH v2 2/8] dt-bindings: mfd: qcom,tcsr: Add compatible for sm4450 Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 3/8] dt-bindings: interrupt-controller: qcom,pdc: document qcom,sm4450-pdc Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 4/8] dt-bindings: arm-smmu: Add compatible for SM4450 SoC Tengfei Fan
2023-09-15 7:12 ` Krzysztof Kozlowski
2023-09-15 2:15 ` [PATCH v2 5/8] arm64: dts: qcom: sm4450: Add apps_rsc and cmd_db node Tengfei Fan
2023-09-20 3:49 ` Bjorn Andersson
2023-09-22 1:16 ` Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 6/8] arm64: dts: qcom: sm4450: Add RPMH and Global clock controller Tengfei Fan
2023-09-15 7:22 ` Krzysztof Kozlowski
2023-09-18 10:34 ` Tengfei Fan
2023-09-18 11:54 ` Krzysztof Kozlowski
2023-09-15 2:15 ` [PATCH v2 7/8] arm64: dts: qcom: add uart console support for SM4450 Tengfei Fan
2023-09-15 7:14 ` Krzysztof Kozlowski
2023-09-15 12:12 ` Konrad Dybcio
2023-09-18 10:40 ` Tengfei Fan
2023-09-20 3:47 ` Bjorn Andersson
2023-09-20 5:46 ` Tengfei Fan
2023-09-15 2:15 ` [PATCH v2 8/8] arm64: defconfig: enable interconnect and pinctrl " Tengfei Fan
2023-09-15 7:21 ` Krzysztof Kozlowski
2023-09-15 9:12 ` Tengfei Fan
2023-09-15 9:16 ` Krzysztof Kozlowski
2023-09-15 11:18 ` Tengfei Fan
2023-09-15 11:29 ` Krzysztof Kozlowski
2023-09-16 2:21 ` Trilok Soni
2023-09-16 2:25 ` Trilok Soni
2023-09-16 15:13 ` Georgi Djakov
2023-09-16 20:32 ` Krzysztof Kozlowski [this message]
2023-09-16 22:55 ` Georgi Djakov
2023-09-17 7:35 ` Krzysztof Kozlowski
2023-09-18 0:53 ` Tengfei Fan
2023-09-16 20:30 ` 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=accb4814-4826-ff97-3527-4e3fbadcd4ff@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=geert+renesas@glider.be \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=peng.fan@nxp.com \
--cc=quic_aiquny@quicinc.com \
--cc=quic_kaushalk@quicinc.com \
--cc=quic_shashim@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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