From: Vignesh Raghavendra <vigneshr@ti.com>
To: Udit Kumar <u-kumar1@ti.com>, <nm@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Chai Wenle <Wenle.Chai@windriver.com>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-j784s4-main: Add DT node for UFS
Date: Tue, 25 Jul 2023 16:06:47 +0530 [thread overview]
Message-ID: <c5b7564c-ca49-4c13-8da0-ea8149f24ce3@ti.com> (raw)
In-Reply-To: <20230725053843.1721028-2-u-kumar1@ti.com>
Hi Udit
Minor nits inline:
On 25/07/23 11:08, Udit Kumar wrote:
> This patch adds UFS support present in J784S4 SOC.
"This patch" perhaps is redundant
>
> UFS is documentend in J784S4 TRM[1]
s/documentend/documented
> Section 12.3.7 'Universal Flash Storage (UFS) Interface'
>
> [1] http://www.ti.com/lit/zip/spruj52
>
> Cc: Chai Wenle <Wenle.Chai@windriver.com>
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 24 ++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> index 11f163e5cadf..f1db1ca5d6b1 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi
> @@ -1370,6 +1370,30 @@ main_spi7: spi@2170000 {
> status = "disabled";
> };
>
> + ufs_wrapper: ufs-wrapper@4e80000 {
> + compatible = "ti,j721e-ufs";
> + reg = <0x0 0x4e80000 0x0 0x100>;
Inline with rest of the file please use 0x00
reg = <0x00 0x4e80000 0x00 0x100>;
> + power-domains = <&k3_pds 387 TI_SCI_PD_EXCLUSIVE>;
> + clocks = <&k3_clks 387 3>;
> + assigned-clocks = <&k3_clks 387 3>;
> + assigned-clock-parents = <&k3_clks 387 6>;
> + ranges;
> + #address-cells = <2>;
> + #size-cells = <2>;
> + status = "disabled";
> +
> + ufs@4e84000 {
> + compatible = "cdns,ufshc-m31-16nm", "jedec,ufs-2.0";
> + reg = <0x0 0x4e84000 0x0 0x10000>;
Same here or perhaps use ranges in the parent node?
> + interrupts = <GIC_SPI 17 IRQ_TYPE_LEVEL_HIGH>;
> + freq-table-hz = <250000000 250000000>, <19200000 19200000>,
> + <19200000 19200000>;
> + clocks = <&k3_clks 387 1>, <&k3_clks 387 3>, <&k3_clks 387 3>;
> + clock-names = "core_clk", "phy_clk", "ref_clk";
> + dma-coherent;
> + };
> + };
> +
> main_r5fss0: r5fss@5c00000 {
> compatible = "ti,j721s2-r5fss";
> ti,cluster-mode = <1>;
--
Regards
Vignesh
next prev parent reply other threads:[~2023-07-25 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 5:38 [PATCH 0/2] arm64: dts: ti: k3-j784s4: Add UFS support Udit Kumar
2023-07-25 5:38 ` [PATCH 1/2] arm64: dts: ti: k3-j784s4-main: Add DT node for UFS Udit Kumar
2023-07-25 10:36 ` Vignesh Raghavendra [this message]
2023-07-25 5:38 ` [PATCH 2/2] arm64: dts: ti: k3-j784s4-evm: Add Support for UFS peripheral Udit Kumar
2023-07-25 9:45 ` Chai, Wenle
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=c5b7564c-ca49-4c13-8da0-ea8149f24ce3@ti.com \
--to=vigneshr@ti.com \
--cc=Wenle.Chai@windriver.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
/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®