[RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Manivannan Sadhasivam]

These drivers will allow using the crypto functionalities of the UFS
device, like Inline Crypto Encryption. Both of these drivers are of type
'bool', so they cannot be built as modules.

Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
---

Compile tested only

 arch/arm64/configs/defconfig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e3a2d37bd104..9f89b3ce1262 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -1230,6 +1230,8 @@ CONFIG_SCSI_UFS_RENESAS=m
 CONFIG_SCSI_UFS_TI_J721E=m
 CONFIG_SCSI_UFS_EXYNOS=y
 CONFIG_SCSI_UFS_ROCKCHIP=y
+CONFIG_BLK_INLINE_ENCRYPTION=y
+CONFIG_SCSI_UFS_CRYPTO=y
 CONFIG_NEW_LEDS=y
 CONFIG_LEDS_CLASS=y
 CONFIG_LEDS_CLASS_MULTICOLOR=m
-- 
2.48.1

Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Bjorn Andersson]

On Thu, 30 Oct 2025 15:25:09 +0530, Manivannan Sadhasivam wrote:
> These drivers will allow using the crypto functionalities of the UFS
> device, like Inline Crypto Encryption. Both of these drivers are of type
> 'bool', so they cannot be built as modules.
> 
> 

Applied, thanks!

[1/1] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers
      commit: 5f37788adedd2da5475d6b1786295c07faf3d718

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Krzysztof Kozlowski]

On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
> These drivers will allow using the crypto functionalities of the UFS
> device, like Inline Crypto Encryption. Both of these drivers are of type
> 'bool', so they cannot be built as modules.

Is there any device benefiting from these? Which board?

> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>

You do not need the second tag. You send it via oss.qualcomm.com which
is still valid.

Best regards,
Krzysztof

Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Manivannan Sadhasivam]

On Thu, Oct 30, 2025 at 08:48:48PM +0100, Krzysztof Kozlowski wrote:
> On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
> > These drivers will allow using the crypto functionalities of the UFS
> > device, like Inline Crypto Encryption. Both of these drivers are of type
> > 'bool', so they cannot be built as modules.
> 
> Is there any device benefiting from these? Which board?
> 

All ICE capable Qcom UFS based boards.

> > 
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> > Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
> 
> You do not need the second tag. You send it via oss.qualcomm.com which
> is still valid.
> 

Yes, I know. But I was having some issue in sending email through
oss.qualcomm.com. Now it got fixed in the RESEND patch, but forgot to remove my
korg s-o-b.

- Mani

-- 
மணிவண்ணன் சதாசிவம்

Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Krzysztof Kozlowski]

On 31/10/2025 07:24, Manivannan Sadhasivam wrote:
> On Thu, Oct 30, 2025 at 08:48:48PM +0100, Krzysztof Kozlowski wrote:
>> On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
>>> These drivers will allow using the crypto functionalities of the UFS
>>> device, like Inline Crypto Encryption. Both of these drivers are of type
>>> 'bool', so they cannot be built as modules.
>>
>> Is there any device benefiting from these? Which board?
>>
> 
> All ICE capable Qcom UFS based boards.
> 
>>>
>>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>>> Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
>>
>> You do not need the second tag. You send it via oss.qualcomm.com which
>> is still valid.
>>
> 
> Yes, I know. But I was having some issue in sending email through
> oss.qualcomm.com. Now it got fixed in the RESEND patch, but forgot to remove my
> korg s-o-b.


You do not need second sob when sending through korg. Your previous
identity was still valid. It's used only when old identity is considered
revoked.


Best regards,
Krzysztof

Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers

[Manivannan Sadhasivam]

On Fri, Oct 31, 2025 at 08:45:38AM +0100, Krzysztof Kozlowski wrote:
> On 31/10/2025 07:24, Manivannan Sadhasivam wrote:
> > On Thu, Oct 30, 2025 at 08:48:48PM +0100, Krzysztof Kozlowski wrote:
> >> On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
> >>> These drivers will allow using the crypto functionalities of the UFS
> >>> device, like Inline Crypto Encryption. Both of these drivers are of type
> >>> 'bool', so they cannot be built as modules.
> >>
> >> Is there any device benefiting from these? Which board?
> >>
> > 
> > All ICE capable Qcom UFS based boards.
> > 
> >>>
> >>> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> >>> Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
> >>
> >> You do not need the second tag. You send it via oss.qualcomm.com which
> >> is still valid.
> >>
> > 
> > Yes, I know. But I was having some issue in sending email through
> > oss.qualcomm.com. Now it got fixed in the RESEND patch, but forgot to remove my
> > korg s-o-b.
> 
> 
> You do not need second sob when sending through korg. Your previous
> identity was still valid. It's used only when old identity is considered
> revoked.
> 

Hmm. I thought the s-o-b should always match the maildomain from which the patch
was sent.

Thanks for clarifying.

- Mani

-- 
மணிவண்ணன் சதாசிவம்