From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] clk: at91: utmi: set the mainck rate
Date: Wed, 1 Nov 2017 23:40:31 -0700 [thread overview]
Message-ID: <20171102064031.GC30645@codeaurora.org> (raw)
In-Reply-To: <20170906095159.13295-1-ludovic.desroches@microchip.com>
On 09/06, Ludovic Desroches wrote:
> By default, it is assumed that the UTMI clock is generated from a 12 MHz
> reference clock (MAINCK). If it's not the case, the FREQ field of the
> SFR_UTMICKTRIM has to be updated to generate the UTMI clock in the
> proper way.
>
> The UTMI clock has a fixed rate of 480 MHz. In fact, there is no
> multiplier we can configure. The multiplier is managed internally,
> depending on the reference clock frequency, to achieve the target of
> 480 MHz.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-02 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 9:51 [PATCH v3] clk: at91: utmi: set the mainck rate Ludovic Desroches
2017-09-06 10:25 ` Ingo van Lil
2017-11-02 6:40 ` Stephen Boyd [this message]
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=20171102064031.GC30645@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).