public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sowon Na <sowon.na@samsung.com>,
	robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
	alim.akhtar@samsung.com, kishon@kernel.org
Cc: krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: exynosautov920: enable support for ufs device
Date: Wed, 2 Jul 2025 08:08:06 +0200	[thread overview]
Message-ID: <1f24f1d3-b28d-4cbf-a165-d857a581032c@kernel.org> (raw)
In-Reply-To: <20250702013316.2837427-6-sowon.na@samsung.com>

On 02/07/2025 03:33, Sowon Na wrote:
> The exynosautov920 uses v3.1 UFS device.
> Add ufs node for ExynosAutov920 SoC.
> And enable ufs_phy and ufs devices with ufs_fixed_vcc_reg regulator for
> ExynosAutov920 SADK.
> 
> Signed-off-by: Sowon Na <sowon.na@samsung.com>
> ---
>  .../boot/dts/exynos/exynosautov920-sadk.dts   | 17 ++++++++++++
>  .../arm64/boot/dts/exynos/exynosautov920.dtsi | 27 +++++++++++++++++++
>  2 files changed, 44 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/exynos/exynosautov920-sadk.dts b/arch/arm64/boot/dts/exynos/exynosautov920-sadk.dts
> index a397f068ed53..f979cc1ae6a1 100644
> --- a/arch/arm64/boot/dts/exynos/exynosautov920-sadk.dts
> +++ b/arch/arm64/boot/dts/exynos/exynosautov920-sadk.dts
> @@ -52,6 +52,14 @@ memory@80000000 {
>  		      <0x8 0x80000000 0x1 0xfba00000>,
>  		      <0xa 0x00000000 0x2 0x00000000>;
>  	};
> +
> +	ufs_fixed_vcc_reg: regulator-0 {


This should be somehow related to real name. Schematics don't call
regulators "fixed" or "non-fixed", which makes me think that you forgot
to implement PMIC.

Best regards,
Krzysztof

  reply	other threads:[~2025-07-02  6:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250702013332epcas2p168d0293f0b7385b0cca88c649fe9c813@epcas2p1.samsung.com>
2025-07-02  1:33 ` [PATCH 0/5] ufs-exynos support for ExynosAutov920 Sowon Na
2025-07-02  1:33   ` [PATCH 1/5] phy: samsung-ufs: update calibration settings for EVT2 Sowon Na
2025-07-17  3:32     ` Alim Akhtar
2025-07-02  1:33   ` [PATCH 2/5] dt-bindings: ufs: exynos: add ExynosAutov920 compatible string Sowon Na
2025-07-16  8:39     ` Krzysztof Kozlowski
2025-07-17  3:34     ` Alim Akhtar
2025-07-02  1:33   ` [PATCH 3/5] dt-bindings: soc: samsung: exynos-sysreg: add hsi2 for ExynosAutov920 Sowon Na
2025-07-16  8:41     ` Krzysztof Kozlowski
2025-07-16  8:42     ` (subset) " Krzysztof Kozlowski
2025-07-02  1:33   ` [PATCH 4/5] scsi: ufs: exynos: add support for ExynosAutov920 SoC Sowon Na
2025-07-17  4:26     ` Alim Akhtar
2025-07-02  1:33   ` [PATCH 5/5] arm64: dts: exynosautov920: enable support for ufs device Sowon Na
2025-07-02  6:08     ` Krzysztof Kozlowski [this message]
2025-07-02  1:33   ` [PATCH 0/5] ufs-exynos support for ExynosAutov920 Sowon Na
2026-04-01  5:29   ` Alim Akhtar

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=1f24f1d3-b28d-4cbf-a165-d857a581032c@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sowon.na@samsung.com \
    --cc=vkoul@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