From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Subject: Re: [PATCH v9 2/2] arm64: dts: qcom: monaco: enable inline crypto engine for SDHC
Date: Wed, 29 Jul 2026 16:16:33 +0200 [thread overview]
Message-ID: <470d18cf-ec29-4f45-aee8-64c5bf492599@oss.qualcomm.com> (raw)
In-Reply-To: <20260707-ice_emmc_support-v9-2-701c86f3c25b@oss.qualcomm.com>
On 7/7/26 9:11 AM, Kuldeep Singh wrote:
> From: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
>
> Add the dedicated ICE node for monaco and reference it from the SDHC
> controller via qcom,ice.
>
> Also, define power-domains and clocks properties similar to the UFS
> node.
>
> Signed-off-by: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
> Co-developed-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
> Signed-off-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-07-29 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 7:11 [PATCH v9 0/2] Enable sdhc inline crypto engine for kodiak and monaco Kuldeep Singh
2026-07-07 7:11 ` [PATCH v9 1/2] arm64: dts: qcom: kodiak: enable inline crypto engine for SDHC Kuldeep Singh
2026-07-07 7:55 ` sashiko-bot
2026-07-07 8:41 ` Kuldeep Singh
2026-07-29 14:16 ` Konrad Dybcio
2026-07-07 7:11 ` [PATCH v9 2/2] arm64: dts: qcom: monaco: " Kuldeep Singh
2026-07-07 8:05 ` sashiko-bot
2026-07-29 14:16 ` Konrad Dybcio [this message]
2026-07-21 7:13 ` [PATCH v9 0/2] Enable sdhc inline crypto engine for kodiak and monaco Kuldeep Singh
2026-08-24 8:43 ` Kuldeep Singh
2026-08-24 9:21 ` Konrad Dybcio
2026-08-24 10:18 ` Kuldeep Singh
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=470d18cf-ec29-4f45-aee8-64c5bf492599@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=robh@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