From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org
Subject: [GIT PULL] versatile clock misc updates for 4.17
Date: Thu, 15 Mar 2018 11:18:56 +0000 [thread overview]
Message-ID: <20180315111856.GA27430@e107155-lin> (raw)
Hi Stephen, Michael,
These couple of changes are on the list for a while and I have not got
any response from you guys. So thought of sending the pull request
instead.
Regards,
Sudeep
--
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/versatile-clk-4.17
for you to fetch changes up to e772c23d70e2e991409cf0e68be77f4126fc578a:
clk: versatile: Remove WARNs in ->round_rate() (2018-03-15 10:45:50 +0000)
----------------------------------------------------------------
versatile clock updates for v4.17
1. Get rid of warnings triggerred when an unachievable clock rate as
clk_round_rate() can be used to get the closest achievable clock
2. Add minimum and maximum rate boundaries for vexpress oscillator clock
using clk_hw_set_rate_range provider API.
----------------------------------------------------------------
Brian Starkey (1):
clk: versatile: Remove WARNs in ->round_rate()
Sudeep Holla (1):
clk: versatile: add min/max rate boundaries for vexpress osc clock
drivers/clk/versatile/clk-vexpress-osc.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
reply other threads:[~2018-03-15 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180315111856.GA27430@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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).