From: Neha Malcom Francis <n-francis@ti.com>
To: Bhavya Kapoor <b-kapoor@ti.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <conor+dt@kernel.org>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <kristo@kernel.org>,
<m-chawdhry@ti.com>, <vigneshr@ti.com>, <nm@ti.com>,
<sinthu.raja@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am68-sk-base-board: Add clklb pin mux for mmc1
Date: Thu, 8 Aug 2024 13:19:35 +0530 [thread overview]
Message-ID: <2279305f-2efa-4320-866a-fc4340d2e70c@ti.com> (raw)
In-Reply-To: <1319a6ac-6784-45d6-8a0e-170e40d3aa18@ti.com>
Hi Bhavya
On 08/08/24 13:08, Bhavya Kapoor wrote:
> Hi Neha,
>
> On 08/08/24 11:51 am, Neha Malcom Francis wrote:
>> Hi Bhavya
>>
>> On 07/08/24 15:46, Bhavya Kapoor wrote:
>>> mmc1 was not functional since pin mux for clklb was not present.
>>> Thus, add clklb pin mux to get MMC working.
>>>
>>> Fixes: a266c180b398 ("arm64: dts: ti: k3-am68-sk: Add support for AM68 SK
>>> base board")
>>> Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
>>> ---
>>>
>>> rebased to next-20240807
>>>
>>> arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
>>> b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
>>> index 90dbe31c5b81..d5ceab79536c 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
>>> +++ b/arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts
>>> @@ -204,6 +204,7 @@ main_mmc1_pins_default: main-mmc1-default-pins {
>>> pinctrl-single,pins = <
>>> J721S2_IOPAD(0x104, PIN_INPUT, 0) /* (P23) MMC1_CLK */
>>> J721S2_IOPAD(0x108, PIN_INPUT, 0) /* (N24) MMC1_CMD */
>>> + J721S2_IOPAD(0x100, PIN_INPUT, 0) /* (###) MMC1_CLKLB */
>>> J721S2_IOPAD(0x0fc, PIN_INPUT, 0) /* (M23) MMC1_DAT0 */
>>> J721S2_IOPAD(0x0f8, PIN_INPUT, 0) /* (P24) MMC1_DAT1 */
>>> J721S2_IOPAD(0x0f4, PIN_INPUT, 0) /* (R24) MMC1_DAT2 */
>>
>> How is this different from the P23 pinmux for MMC1_CLK? Could you explain what
>> CLKLB is, since it doesn't have a ball number I'm finding it difficult to
>> understand what it is?
>>
> This pin needs to be setup so that MMC_CLK is looped back at pad level for
> highspeed SDIO operations (has been same across K3 family). MMC0/1 has this pin
> configured as INPUT by reset default as these have boot media
>
> These pinmuxes are derived from pinmux file shared by EVM team during
> wakeup/board bringup.
>
Thank you for explaining.
Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
> Regards
>
--
Thanking You
Neha Malcom Francis
next prev parent reply other threads:[~2024-08-08 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 10:16 [PATCH] arm64: dts: ti: k3-am68-sk-base-board: Add clklb pin mux for mmc1 Bhavya Kapoor
2024-08-08 5:09 ` Manorit Chawdhry
2024-08-08 6:21 ` Neha Malcom Francis
2024-08-08 7:38 ` Bhavya Kapoor
2024-08-08 7:49 ` Neha Malcom Francis [this message]
2024-08-08 8:29 ` Manorit Chawdhry
2024-08-08 10:53 ` Nishanth Menon
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=2279305f-2efa-4320-866a-fc4340d2e70c@ti.com \
--to=n-francis@ti.com \
--cc=b-kapoor@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sinthu.raja@ti.com \
--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).