From: Michal Simek <michal.simek@amd.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Swati Agarwal <swati.agarwal@amd.com>
Cc: <adrian.hunter@intel.com>, <michal.simek@xilinx.com>,
<linux-mmc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <git@amd.com>
Subject: Re: [PATCH] mmc: sdhci-of-arasan: Add support to request the "gate" clock
Date: Mon, 27 Feb 2023 16:09:42 +0100 [thread overview]
Message-ID: <6e037df0-8f59-9277-3f40-c22278e02430@amd.com> (raw)
In-Reply-To: <CAPDyKFoGmHpdt5UckyDTWQSK7OmZ789g9Owz7sPP4VJ6ezJbsQ@mail.gmail.com>
On 2/27/23 15:56, Ulf Hansson wrote:
> CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
>
>
> On Thu, 23 Feb 2023 at 15:14, Swati Agarwal <swati.agarwal@amd.com> wrote:
>>
>> Add support to read the optional "gate" clock property and request the
>> clock which will be used to ungate the DLL clock.
>>
>> For Xilinx platforms which has DLL module, dll clock must be
>> ungated/enabled when SD controller operates at higher frequencies like 50
>> MHz, 100 MHz and 200 MHz. This will be done by explicitly requesting gate
>> clock from the driver.
>
> I guess we need to update the DT bindings too?
DT binding has it already. It is just not used.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mmc/arasan,sdhci.yaml?h=v6.2#n110
Thanks,
Michal
next prev parent reply other threads:[~2023-02-27 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 14:14 [PATCH] mmc: sdhci-of-arasan: Add support to request the "gate" clock Swati Agarwal
2023-02-27 8:16 ` Michal Simek
2023-02-27 14:56 ` Ulf Hansson
2023-02-27 15:09 ` Michal Simek [this message]
2023-02-27 15:31 ` Ulf Hansson
2023-03-02 11:09 ` Adrian Hunter
2023-03-09 15:02 ` Ulf Hansson
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=6e037df0-8f59-9277-3f40-c22278e02430@amd.com \
--to=michal.simek@amd.com \
--cc=adrian.hunter@intel.com \
--cc=git@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=swati.agarwal@amd.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).