From: Judith Mendez <jm@ti.com>
To: Nitin Yadav <n-yadav@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] arm64: dts: ti: k3-am62a-main: Add sdhci0 instance
Date: Tue, 28 Nov 2023 13:58:33 -0600 [thread overview]
Message-ID: <6eab794f-a5cf-455a-9b49-bc73259bd58e@ti.com> (raw)
In-Reply-To: <db70f42e-0296-4f36-ac97-2ecf38b84f51@ti.com>
Hi Nitin,
On 11/27/23 10:39 PM, Nitin Yadav wrote:
>
>
> On 11/28/2023 3:11 AM, Judith Mendez wrote:
>> On 10/30/23 1:31 AM, Nitin Yadav wrote:
>>> Add sdhci0 DT node in k3-am62a-main for eMMC support. Droping
>>> ITAP values as they are NA in datasheet[0] for lower speed modes.
>>>
>>> [0]https://www.ti.com/lit/gpn/am62a3 Table: 7-79 (Page No. 179)
>>>
>>
>> Minor comment below. All else looks good to me.
>>
>> Reviewed by: Judith Mendez <jm@ti.com>
>>
>>> Signed-off-by: Nitin Yadav <n-yadav@ti.com>
>>> ---
>>> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 19 +++++++++++++++++++
>>> 1 file changed, 19 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>>> index de36abb243f1..89b8b7d302cd 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>>> +++ b/arch/arm64/boot/dts/ti/k3-am62a-main.dtsi
>>> @@ -488,6 +488,25 @@ main_gpio1: gpio@601000 {
>>> status = "disabled";
>>> };
>>> + sdhci0: mmc@fa10000 {
>>> + compatible = "ti,am62-sdhci";
>>> + reg = <0x00 0xfa10000 0x00 0x260>, <0x00 0xfa18000 0x00 0x134>;
>>> + interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
>>> + power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
>>> + clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
>>> + clock-names = "clk_ahb", "clk_xin";
>>> + assigned-clocks = <&k3_clks 57 6>;
>>> + assigned-clock-parents = <&k3_clks 57 8>;
>>> + mmc-hs200-1_8v;
>>> + ti,trm-icp = <0x2>;
>>> + ti,otap-del-sel-legacy = <0x0>;
>>> + ti,otap-del-sel-mmc-hs = <0x0>;
>>> + ti,otap-del-sel-hs200 = <0x6>;
>>
>> I am wondering why DDR52 speed mode was not added?
> plz refer datasheet. No mention of DDR52 in this revised addition.
I believe it is mentioned in the RIOT, not datasheet.
>>
>>> + bus-width = <8>;
>>> + ti,clkbuf-sel = <0x7>;
>>> + status = "disabled";
>>> + };
>>> +
>>> sdhci1: mmc@fa00000 {
>>> compatible = "ti,am62-sdhci";
>>> reg = <0x00 0xfa00000 0x00 0x260>, <0x00 0xfa08000 0x00 0x134>;
>>
>> ~ Judith
next prev parent reply other threads:[~2023-11-28 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 6:31 [PATCH v2 0/2] Add eMMC support for AM62a SK Nitin Yadav
2023-10-30 6:31 ` [PATCH v2 1/2] arm64: dts: ti: k3-am62a-main: Add sdhci0 instance Nitin Yadav
2023-11-27 21:41 ` Judith Mendez
2023-11-28 4:39 ` Nitin Yadav
2023-11-28 19:58 ` Judith Mendez [this message]
2023-10-30 6:31 ` [PATCH v2 2/2] arm64: dts: ti: k3-am62a7-sk: Enable eMMC support Nitin Yadav
2023-11-29 0:29 ` Judith Mendez
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=6eab794f-a5cf-455a-9b49-bc73259bd58e@ti.com \
--to=jm@ti.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=n-yadav@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@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;
as well as URLs for NNTP newsgroup(s).