From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] clk fixes for 3.8
Date: Thu, 27 Dec 2012 13:14:28 +1300 [thread overview]
Message-ID: <1356567272-3420-1-git-send-email-linux@prisktech.co.nz> (raw)
Mike,
Three bugfixes for 3.8.
#1 was a boo-boo on my part, function returned the wrong variables.
#2 is a truncation problem which results in a higher-than-requested clock rate.
#3 became apparent when the MMC driver started requesting rate=0 during init.
Tony Prisk (3):
clk: vt8500: Fix error in PLL calculations on non-exact match.
clk: vt8500: Fix device clock divisor calculations
clk: vt8500: Fix division-by-0 when requested rate=0
drivers/clk/clk-vt8500.c | 28 +++++++++++++++++++++++-----
1 file changed, 23 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-12-27 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 0:14 Tony Prisk [this message]
2012-12-27 0:14 ` [PATCH 1/3] clk: vt8500: Fix error in PLL calculations on non-exact match Tony Prisk
2012-12-27 0:14 ` [PATCH 2/3] clk: vt8500: Fix device clock divisor calculations Tony Prisk
2012-12-27 0:14 ` [PATCH 3/3] clk: vt8500: Fix division-by-0 when requested rate=0 Tony Prisk
2013-01-14 23:06 ` [PATCH 0/3] clk fixes for 3.8 Mike Turquette
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=1356567272-3420-1-git-send-email-linux@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--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).