From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] arm: sa1100: add cpu clock
Date: Tue, 12 Nov 2013 09:57:06 +0000 [thread overview]
Message-ID: <20131112095706.GE16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1384227132-10501-1-git-send-email-dbaryshkov@gmail.com>
On Tue, Nov 12, 2013 at 07:32:08AM +0400, Dmitry Eremin-Solenikov wrote:
> Both SA1100 framebuffer and PCMCIA drivers require knowledge of cpu
> frequency to correctly program timings. Currently they receive timing
> information by calling cpufreq_get(0). However if cpu frequency driver
> is not enabled (e.g. due to unsupported DRAM chip/board on sa1110)
> cpufreq_get(0) returns 0, causing incorrect timings to be programmed.
I added a select statement back in 1937f5b91833e2e8e53bcc821fc7a5fbe6ccb9b5
which avoids this problem. Does this not work?
next prev parent reply other threads:[~2013-11-12 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 3:32 [PATCH 1/5] arm: sa1100: add cpu clock Dmitry Eremin-Solenikov
2013-11-12 3:32 ` [PATCH 2/5] fbdev: sa1100fb: make use of device clock Dmitry Eremin-Solenikov
2013-11-12 3:32 ` [PATCH 3/5] pcmcia: sa1100: " Dmitry Eremin-Solenikov
2013-11-12 3:32 ` [PATCH 4/5] arm: sa1100: add a clock alias for sa1111 pcmcia device Dmitry Eremin-Solenikov
2013-11-12 12:00 ` Dmitry Artamonow
2013-11-12 3:32 ` [PATCH 5/5] pcmcia: sa1111: make use of device clock Dmitry Eremin-Solenikov
2013-11-12 9:57 ` Russell King - ARM Linux [this message]
2013-11-12 10:37 ` [PATCH 1/5] arm: sa1100: add cpu clock Dmitry Eremin-Solenikov
-- strict thread matches above, loose matches on Subject: below --
2014-10-24 10:37 [PATCH 0/5] arm: sa1100: fix sa1100 fb and pcmcia w/o cpufreq Dmitry Eremin-Solenikov
2014-10-24 10:37 ` [PATCH 1/5] arm: sa1100: add cpu clock 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=20131112095706.GE16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).