From: Matthias Brugger <matthias.bgg@gmail.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
hsinyi@chromium.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8186: Add crypto support for eMMC controller
Date: Wed, 21 Dec 2022 14:09:29 +0100 [thread overview]
Message-ID: <6b650bcd-d063-9998-442a-3705c0654d73@gmail.com> (raw)
In-Reply-To: <20221221104856.28770-1-allen-kh.cheng@mediatek.com>
On 21/12/2022 11:48, Allen-KH Cheng wrote:
> For crypto support, add a crypto clock of the inline crypto engine and
> expand the register size in the eMMC controller.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Applied, thanks!
> ---
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8186.dtsi b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> index c326aeb33a10..88b6191e1aa0 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> @@ -662,12 +662,13 @@
> mmc0: mmc@11230000 {
> compatible = "mediatek,mt8186-mmc",
> "mediatek,mt8183-mmc";
> - reg = <0 0x11230000 0 0x1000>,
> + reg = <0 0x11230000 0 0x10000>,
> <0 0x11cd0000 0 0x1000>;
> clocks = <&topckgen CLK_TOP_MSDC50_0>,
> <&infracfg_ao CLK_INFRA_AO_MSDC0>,
> - <&infracfg_ao CLK_INFRA_AO_MSDC0_SRC>;
> - clock-names = "source", "hclk", "source_cg";
> + <&infracfg_ao CLK_INFRA_AO_MSDC0_SRC>,
> + <&infracfg_ao CLK_INFRA_AO_MSDCFDE>;
> + clock-names = "source", "hclk", "source_cg", "crypto";
> interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH 0>;
> assigned-clocks = <&topckgen CLK_TOP_MSDC50_0>;
> assigned-clock-parents = <&apmixedsys CLK_APMIXED_MSDCPLL>;
prev parent reply other threads:[~2022-12-21 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:48 Allen-KH Cheng
2022-12-21 13:09 ` Matthias Brugger [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=6b650bcd-d063-9998-442a-3705c0654d73@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®