[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80dc35dc-45e5-4f2c-83a8-ffa8c430eecf@kernel.org>
Date: Thu, 9 Oct 2025 17:20:56 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Abhinaba Rakshit <abhinaba.rakshit@....qualcomm.com>,
Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>
Cc: linux-arm-msm@...r.kernel.org, linux-mmc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: mmc: add qcom,ice phandle to mmc
On 09/10/2025 15:18, Abhinaba Rakshit wrote:
> Add the 'qcom,ice' phandle to the MMC device tree binding to support
> reference to an Inline Crypto Engine (ICE) device node.
>
> ICE hardware is now represented as a separate device node, and its
> clock and frequency configuration are managed independently by
> the ICE driver.
>
> Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@....qualcomm.com>
> ---
> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
It is duplicating the ICE address space, so you need the same code as
other existing bindings.
Best regards,
Krzysztof
Powered by blists - more mailing lists