From: Matthias Brugger <matthias.bgg@gmail.com>
To: Julien Massot <julien.massot@collabora.com>,
kernel@collabora.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8395-nio-12l: Enable UFS
Date: Tue, 9 Sep 2025 14:44:06 +0200 [thread overview]
Message-ID: <4d6fcd11-a724-44ec-a183-cd1afe959bed@gmail.com> (raw)
In-Reply-To: <20250905-radxa-nio-12l-ufs-v1-1-e2468bfd2c69@collabora.com>
On 05/09/2025 15:21, Julien Massot wrote:
> UFS is the primary storage for the Radxa NIO 12L. Enable it
> now that the ufshci and ufsphy nodes are available in the
> common mt8195 dtsi.
>
> Signed-off-by: Julien Massot <julien.massot@collabora.com>
Queued, thanks.
Matthias
> ---
> arch/arm64/boot/dts/mediatek/mt8395-radxa-nio-12l.dts | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8395-radxa-nio-12l.dts b/arch/arm64/boot/dts/mediatek/mt8395-radxa-nio-12l.dts
> index 329c60cc6a6be0b4be8c0b8bb033b32d35302804..4cbd78c126f6b56f1833d220f7a7fbc7e4320cbb 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8395-radxa-nio-12l.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt8395-radxa-nio-12l.dts
> @@ -990,6 +990,16 @@ &uart1 {
> status = "okay";
> };
>
> +&ufshci {
> + vcc-supply = <&mt6359_vemc_1_ldo_reg>;
> + vccq2-supply = <&mt6359_vufs_ldo_reg>;
> + status = "okay";
> +};
> +
> +&ufsphy {
> + status = "okay";
> +};
> +
> &ssusb0 {
> pinctrl-names = "default";
> pinctrl-0 = <&usb3_port0_pins>;
>
> ---
> base-commit: 6c68f4c0a147c025ae0b25fab688c7c47964a02f
> change-id: 20250905-radxa-nio-12l-ufs-c817a864fb42
>
> Best regards,
prev parent reply other threads:[~2025-09-09 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:21 Julien Massot
2025-09-09 12:44 ` 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=4d6fcd11-a724-44ec-a183-cd1afe959bed@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=julien.massot@collabora.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--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
all inboxes | Powered by JetHome®