From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: Bjorn Andersson <quic_bjorande@quicinc.com>,
Mukesh Ojha <quic_mojha@quicinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Enable secure QFPROM driver
Date: Thu, 20 Jun 2024 15:13:51 +0530 [thread overview]
Message-ID: <c23f9f69-d095-233e-c20e-b99e6f3921e5@quicinc.com> (raw)
In-Reply-To: <ZnMKh5X+Bm11L/T4@hu-bjorande-lv.qualcomm.com>
On 6/19/2024 10:12 PM, Bjorn Andersson wrote:
> On Wed, Jun 19, 2024 at 05:40:42PM +0530, Mukesh Ojha wrote:
>> On Wed, Jun 19, 2024 at 01:08:48PM +0200, Krzysztof Kozlowski wrote:
>>> On 19/06/2024 12:56, Komal Bajaj wrote:
>>>> Enable the secure QFPROM driver which is used by QDU1000
>>>
>>> Qualcomm QDU1000. You are changing kernel-wide defconfig, not some
>>> Qualcomm downstream stuff.
>>>
>>>> platform for reading the secure qfprom region to get the
>>>> DDR channel configuration.
>>>>
>>>> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
>>>> ---
>>>> arch/arm64/configs/defconfig | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>>>> index 838b4466d6f6..c940437ae1b3 100644
>>>> --- a/arch/arm64/configs/defconfig
>>>> +++ b/arch/arm64/configs/defconfig
>>>> @@ -1575,6 +1575,7 @@ CONFIG_NVMEM_LAYERSCAPE_SFP=m
>>>> CONFIG_NVMEM_MESON_EFUSE=m
>>>> CONFIG_NVMEM_MTK_EFUSE=y
>>>> CONFIG_NVMEM_QCOM_QFPROM=y
>>>> +CONFIG_NVMEM_QCOM_SEC_QFPROM=y
>>>
>>> Module
>>
>> Should not this be inline with what CONFIG_NVMEM_QCOM_QFPROM is having ?
>> Either both CONFIG_NVMEM_QCOM_QFPROM and CONFIG_NVMEM_QCOM_SEC_QFPROM
>> should be m or both y
>>
>
> While that would be a convenient guideline, you're adding runtime
> overhead to all other targets (Qualcomm and non-Qualcomm) so the desire
> to keep anything that can module outweigh such convenience.
>
> Based on the recent addition of llcc and qfprom nodes I'm _guessing_
> that LLCC is the one user of this today, and it is =m, so therefore
> SEC_QFPROM can be =m as well.
>
>
> By expanding the commit message slightly, we could have avoided the
> "why?" questions and the need for me to "guess" the actual dependency.
>
Thanks Bjorn for the suggestion.
I will incorporate the suggested changes in the next patch.
Thanks
Komal
> Regards,
> Bjorn
>
>> -Mukesh
>>>
>>>> CONFIG_NVMEM_RMEM=m
>>>> CONFIG_NVMEM_ROCKCHIP_EFUSE=y
>>>> CONFIG_NVMEM_ROCKCHIP_OTP=y
>>>> --
>>>> 2.42.0
>>>>
>>>
>>> Best regards,
>>> Krzysztof
>>>
prev parent reply other threads:[~2024-06-20 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:56 [PATCH] arm64: defconfig: Enable secure QFPROM driver Komal Bajaj
2024-06-19 10:57 ` Dmitry Baryshkov
2024-06-19 11:08 ` Krzysztof Kozlowski
2024-06-19 12:10 ` Mukesh Ojha
2024-06-19 12:23 ` Krzysztof Kozlowski
2024-06-19 13:14 ` Dmitry Baryshkov
2024-06-19 16:38 ` Mukesh Ojha
2024-06-19 16:51 ` Bjorn Andersson
2024-06-19 18:46 ` Mukesh Ojha
2024-06-19 16:42 ` Bjorn Andersson
2024-06-20 9:43 ` Komal Bajaj [this message]
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=c23f9f69-d095-233e-c20e-b99e6f3921e5@quicinc.com \
--to=quic_kbajaj@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--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=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_mojha@quicinc.com \
--cc=srinivas.kandagatla@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;
as well as URLs for NNTP newsgroup(s).