From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/6] ARM: sa1100: use clock api to get cpu freq in fb and pcmcia drivers
Date: Mon, 24 Nov 2014 23:05:30 +0000 [thread overview]
Message-ID: <1416870336-30114-1-git-send-email-dbaryshkov@gmail.com> (raw)
[Changes since V1:
- reorder patches to add sa1100 and sa1111 clocks before using them
in sa1100 pcmcia driver.
- Fix error returns in case clk_get returns an error.
- Call clk_prepare_enable/clk_disable_unprepare for the proper API
usage.]
On SA-1100 framebuffer and PCMCIA drivers make use of cpufreq_get(0)
function call to determine the cpu frequency. Russell's commit
1937f5b91833e2e8e53bcc821fc7a5fbe6ccb9b5 (ARM: fix sa1100 build) fixed
the build issues, but broke two devices (Collie and Jornada720). For
those two boards the cpufreq code gets compiled but is not enabled (as
board files do not provide timing information for the CPUFREQ driver).
Thus cpufreq_get(0) returns incorrect value and incorrect timings get
programmed into the hardware.
PXA2xx (the very similar platform) uses Clock API to determine CPU
frequency both in framebuffer and PCMCIA drivers. These patches make
similar changes to StrongARM drivers.
--
With best wishes
Dmitry
next reply other threads:[~2014-11-24 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 23:05 Dmitry Eremin-Solenikov [this message]
2014-11-24 23:05 ` [PATCH V2 1/6] ARM: sa1100: add cpu clock Dmitry Eremin-Solenikov
2014-11-24 23:05 ` [PATCH V2 2/6] ARM: sa1100: add a clock alias for sa1111 pcmcia device Dmitry Eremin-Solenikov
2014-11-24 23:05 ` [PATCH V2 3/6] fbdev: sa1100fb: make use of device clock Dmitry Eremin-Solenikov
2014-11-24 23:05 ` [PATCH V2 4/6] pcmcia: soc-common: enable/disable socket clocks Dmitry Eremin-Solenikov
2014-11-24 23:05 ` [PATCH V2 5/6] pcmcia: sa1111: provide device clock Dmitry Eremin-Solenikov
2014-11-24 23:05 ` [PATCH V2 6/6] pcmcia: sa1100: make use of " Dmitry Eremin-Solenikov
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=1416870336-30114-1-git-send-email-dbaryshkov@gmail.com \
--to=dbaryshkov@gmail.com \
--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).