From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clk: ti: dpll: add support for specifying max rate for DPLLs
Date: Fri, 1 Apr 2016 12:27:50 -0700 [thread overview]
Message-ID: <20160401192750.GV18567@codeaurora.org> (raw)
In-Reply-To: <1458158097-21137-2-git-send-email-t-kristo@ti.com>
On 03/16, Tero Kristo wrote:
> DPLLs typically have a maximum rate they can support, and this varies
> from DPLL to DPLL. Add support of the maximum rate value to the DPLL
> data struct, and also add check for this in the DPLL round_rate function.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Cc: Lokesh Vutla <lokeshvutla@ti.com>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-04-01 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 19:54 [PATCH 0/3] ARM: AMx3xx: misc clock fixes Tero Kristo
2016-03-16 19:54 ` [PATCH 1/3] clk: ti: dpll: add support for specifying max rate for DPLLs Tero Kristo
2016-04-01 19:27 ` Stephen Boyd [this message]
2016-04-16 0:26 ` Stephen Boyd
2016-03-16 19:54 ` [PATCH 2/3] clk: ti: amx3xx: limit the maximum frequency of DPLLs based on spec Tero Kristo
2016-04-01 19:28 ` Stephen Boyd
2016-04-13 12:51 ` Tero Kristo
2016-04-16 0:23 ` Stephen Boyd
2016-04-16 0:27 ` Stephen Boyd
2016-03-16 19:54 ` [PATCH 3/3] ARM: dts: am43xx: add support for clkout1 clock Tero Kristo
2016-04-12 21:05 ` Tony Lindgren
2016-04-13 12:52 ` Tero Kristo
2016-04-13 19:07 ` Tony Lindgren
2016-03-16 22:33 ` [PATCH 0/3] ARM: AMx3xx: misc clock fixes 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=20160401192750.GV18567@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).