From: Bhavya Kapoor <b-kapoor@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <conor+dt@kernel.org>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <kristo@kernel.org>,
<vigneshr@ti.com>, <nm@ti.com>, <sinthu.raja@ti.com>,
<n-francis@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am68-sk-base-board: Add clklb pin mux for mmc1
Date: Mon, 12 Aug 2024 12:23:26 +0530 [thread overview]
Message-ID: <413dc315-e8d0-4971-af23-ba21833eb855@ti.com> (raw)
In-Reply-To: <20240812051058.ooq7uxd6xdbhgjln@uda0497581>
HI Manorit, please review again for the limitation you found in the v1.
Thanks and Regards
On 12/08/24 10:40, Manorit Chawdhry wrote:
> Hi Bhavya,
>
> On 12:52-20240809, Bhavya Kapoor wrote:
>> mmc1 is not functional and needs clock loopback so that it can
>> create sampling clock from this for high speed SDIO operations.
>> Thus, add clklb pin mux to get mmc1 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>
>> Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
>> ---
>>
> R-by already given in v1 [0]
>
> [0]: https://lore.kernel.org/all/20240808050914.4jleprwmlrtv4alb@uda0497581/
>
> Regards,
> Manorit
next prev parent reply other threads:[~2024-08-12 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 7:22 [PATCH v2] arm64: dts: ti: k3-am68-sk-base-board: Add clklb pin mux for mmc1 Bhavya Kapoor
2024-08-12 5:10 ` Manorit Chawdhry
2024-08-12 6:53 ` Bhavya Kapoor [this message]
2024-08-12 7:34 ` Manorit Chawdhry
2024-08-24 19:51 ` 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=413dc315-e8d0-4971-af23-ba21833eb855@ti.com \
--to=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=n-francis@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