From: "나소원/SOWON NA" <sowon.na@samsung.com>
To: "'Alim Akhtar'" <alim.akhtar@samsung.com>, <robh@kernel.org>,
<krzk@kernel.org>, <conor+dt@kernel.org>, <vkoul@kernel.org>,
<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 v3 3/3] arm64: dts: exynosautov920: add ufs phy for ExynosAutov920 SoC
Date: Wed, 27 Nov 2024 15:09:01 +0900 [thread overview]
Message-ID: <005801db4092$db115270$9133f750$@samsung.com> (raw)
In-Reply-To: <000101db4076$ac6b18a0$054149e0$@samsung.com>
Hi Alim,
> -----Original Message-----
> From: Alim Akhtar <alim.akhtar@samsung.com>
> Sent: Wednesday, November 27, 2024 11:47 AM
> To: 'Sowon Na' <sowon.na@samsung.com>; robh@kernel.org; krzk@kernel.org;
> conor+dt@kernel.org; vkoul@kernel.org; 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 v3 3/3] arm64: dts: exynosautov920: add ufs phy for
> ExynosAutov920 SoC
>
>
>
> > -----Original Message-----
> > From: Sowon Na <sowon.na@samsung.com>
> > Sent: Monday, November 18, 2024 7:40 AM
> > To: robh@kernel.org; krzk@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;
> > sowon.na@samsung.com
> > Subject: [PATCH v3 3/3] arm64: dts: exynosautov920: add ufs phy for
> > ExynosAutov920 SoC
> >
> > Add UFS Phy for ExynosAutov920
> >
> > Like ExynosAutov9, this also uses fixed-rate clock nodes until clock
> > driver has been supported. The clock nodes are initialized on
> > bootloader stage thus we don't need to control them so far.
> >
> > Signed-off-by: Sowon Na <sowon.na@samsung.com>
> > ---
> Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
>
> Are you planning to send UFS HCI patches as well?
Yes, I will send UFS HCI patches for ExynosAutov920 after phy patches.
Really thank you for your reviews.
>
> > arch/arm64/boot/dts/exynos/exynosautov920.dtsi | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/exynos/exynosautov920.dtsi
> > b/arch/arm64/boot/dts/exynos/exynosautov920.dtsi
> > index c759134c909e..505ba04722de 100644
> > --- a/arch/arm64/boot/dts/exynos/exynosautov920.dtsi
> > +++ b/arch/arm64/boot/dts/exynos/exynosautov920.dtsi
> > @@ -361,6 +361,17 @@ pinctrl_aud: pinctrl@1a460000 {
> > compatible = "samsung,exynosautov920-pinctrl";
> > reg = <0x1a460000 0x10000>;
> > };
> > +
> > + ufs_0_phy: phy@16e04000 {
> > + compatible = "samsung,exynosautov920-ufs-phy";
> > + reg = <0x16e04000 0x4000>;
> > + reg-names = "phy-pma";
> > + clocks = <&xtcxo>;
> > + clock-names = "ref_clk";
> > + samsung,pmu-syscon = <&pmu_system_controller>;
> > + #phy-cells = <0>;
> > + status = "disabled";
> > + };
> > };
> >
> > timer {
> > --
> > 2.45.2
>
next prev parent reply other threads:[~2024-11-27 6:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241118021011epcas2p397736dd9e5c7d96d799716e09919c136@epcas2p3.samsung.com>
2024-11-18 2:10 ` [PATCH v3 0/3] Support ExynosAutov920 ufs phy driver Sowon Na
2024-11-18 2:10 ` [PATCH v3 1/3] dt-bindings: phy: Add ExynosAutov920 UFS PHY bindings Sowon Na
2024-11-19 5:20 ` Alim Akhtar
2024-11-19 6:36 ` 나소원/SOWON NA
2024-12-18 1:32 ` 나소원/SOWON NA
2024-12-18 7:53 ` Krzysztof Kozlowski
2024-12-24 14:59 ` Vinod Koul
2024-11-19 7:50 ` Krzysztof Kozlowski
2024-11-18 2:10 ` [PATCH v3 2/3] phy: samsung-ufs: support ExynosAutov920 ufs phy driver Sowon Na
2024-11-27 2:46 ` Alim Akhtar
2024-12-24 14:58 ` Vinod Koul
2024-12-26 2:12 ` 나소원/SOWON NA
2024-11-18 2:10 ` [PATCH v3 3/3] arm64: dts: exynosautov920: add ufs phy for ExynosAutov920 SoC Sowon Na
2024-11-27 2:47 ` Alim Akhtar
2024-11-27 6:09 ` 나소원/SOWON NA [this message]
2024-12-17 1:29 ` [PATCH v3 0/3] Support ExynosAutov920 ufs phy driver 나소원/SOWON NA
2024-12-17 5:23 ` Krzysztof Kozlowski
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='005801db4092$db115270$9133f750$@samsung.com' \
--to=sowon.na@samsung.com \
--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=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--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