Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Bjorn Andersson <quic_bjorande@quicinc.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Will Deacon <will@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: defconfig: Build interconnect driver for QCM2290
Date: Wed, 24 May 2023 00:11:32 +0300	[thread overview]
Message-ID: <bacae75a-6030-ff8b-179f-7d662140bae7@linaro.org> (raw)
In-Reply-To: <21baf481-347f-d4b1-87df-833ed16cb729@linaro.org>

On 23/05/2023 20:30, Konrad Dybcio wrote:
> 
> 
> On 23.05.2023 18:54, Vladimir Zapolskiy wrote:
>> Build Qualcomm QCM2290 interconnect driver.
>>
>> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
>> ---
> Do we know why some are =y and some are =m?
> 
> I'm for =y either way, if we can.

I think this might change from platform to platform. What is the 
condition for selecting 'y' or 'm' for the core drivers? Is it 'should 
boot to rootfs without modules' or 'should boot to UART and load initrd 
without modules' ?

> 
> Konrad
>>   arch/arm64/configs/defconfig | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>> index e2f6a352a0ad..ec9b828b14e2 100644
>> --- a/arch/arm64/configs/defconfig
>> +++ b/arch/arm64/configs/defconfig
>> @@ -1415,6 +1415,7 @@ CONFIG_INTERCONNECT_QCOM=y
>>   CONFIG_INTERCONNECT_QCOM_MSM8916=m
>>   CONFIG_INTERCONNECT_QCOM_MSM8996=m
>>   CONFIG_INTERCONNECT_QCOM_OSM_L3=m
>> +CONFIG_INTERCONNECT_QCOM_QCM2290=y
>>   CONFIG_INTERCONNECT_QCOM_QCS404=m
>>   CONFIG_INTERCONNECT_QCOM_SA8775P=y
>>   CONFIG_INTERCONNECT_QCOM_SC7180=y

-- 
With best wishes
Dmitry


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-05-23 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 16:54 [PATCH 0/5] arm64: defconfig: build some essential Qualcomm platform drivers Vladimir Zapolskiy
2023-05-23 16:54 ` [PATCH 1/5] arm64: defconfig: Build MSM power manager driver Vladimir Zapolskiy
2023-05-23 17:29   ` Konrad Dybcio
2023-05-23 16:54 ` [PATCH 2/5] arm64: defconfig: Build Global Clock Controller driver for QCM2290 Vladimir Zapolskiy
2023-05-23 17:30   ` Konrad Dybcio
2023-05-23 16:54 ` [PATCH 3/5] arm64: defconfig: Build interconnect " Vladimir Zapolskiy
2023-05-23 17:30   ` Konrad Dybcio
2023-05-23 21:11     ` Dmitry Baryshkov [this message]
2023-05-24  6:36       ` Arnd Bergmann
2023-05-24 23:14         ` Bjorn Andersson
2023-05-25  4:28   ` Bjorn Andersson
2023-05-23 16:54 ` [PATCH 4/5] arm64: defconfig: Build display clock controller " Vladimir Zapolskiy
2023-05-23 17:30   ` Konrad Dybcio
2023-05-23 16:54 ` [PATCH 5/5] arm64: defconfig: Build SM6115 display and GPU clock controller drivers Vladimir Zapolskiy

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=bacae75a-6030-ff8b-179f-7d662140bae7@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=arnd@arndb.de \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_bjorande@quicinc.com \
    --cc=vladimir.zapolskiy@linaro.org \
    --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