From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] arm: sa1100: fix sa1100 fb and pcmcia w/o cpufreq
Date: Fri, 24 Oct 2014 14:37:22 +0400 [thread overview]
Message-ID: <1414147047-12892-1-git-send-email-dbaryshkov@gmail.com> (raw)
Hello,
These patches were sitting in my queue for some time. 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 values 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.
These patches are required to make use of framebuffer and CF card on
Sharp Collie (and possibly on HP Jornada 720).
--
With best wishes
Dmitry
next reply other threads:[~2014-10-24 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 10:37 Dmitry Eremin-Solenikov [this message]
2014-10-24 10:37 ` [PATCH 1/5] arm: sa1100: add cpu clock Dmitry Eremin-Solenikov
2014-10-24 10:37 ` [PATCH 2/5] arm: sa1100: add a clock alias for sa1111 pcmcia device Dmitry Eremin-Solenikov
2014-10-24 10:37 ` [PATCH 3/5] fbdev: sa1100fb: make use of device clock Dmitry Eremin-Solenikov
2014-10-28 10:52 ` Tomi Valkeinen
2014-10-24 10:37 ` [PATCH 4/5] pcmcia: sa1100: " Dmitry Eremin-Solenikov
2014-10-24 10:37 ` [PATCH 5/5] pcmcia: sa1111: provide " Dmitry Eremin-Solenikov
2014-10-29 18:41 ` [PATCH 0/5] arm: sa1100: fix sa1100 fb and pcmcia w/o cpufreq 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=1414147047-12892-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).