Re: [PATCH 1/5] arm: sa1100: add cpu clock

[PATCH 1/5] arm: sa1100: add cpu clock · Dmitry Eremin-Solenikov <hidden> · 2013-11-12
[PATCH 2/5] fbdev: sa1100fb: make use of device clock · Dmitry Eremin-Solenikov <hidden> · 2013-11-12
[PATCH 3/5] pcmcia: sa1100: make use of device clock · Dmitry Eremin-Solenikov <hidden> · 2013-11-12
[PATCH 4/5] arm: sa1100: add a clock alias for sa1111 pcmcia device · Dmitry Eremin-Solenikov <hidden> · 2013-11-12
[PATCH 4/5] arm: sa1100: add a clock alias for sa1111 pcmcia device · Dmitry Artamonow <hidden> · 2013-11-12
[PATCH 5/5] pcmcia: sa1111: make use of device clock · Dmitry Eremin-Solenikov <hidden> · 2013-11-12
[PATCH 1/5] arm: sa1100: add cpu clock · Russell King - ARM Linux <hidden> · 2013-11-12
[PATCH 1/5] arm: sa1100: add cpu clock · Dmitry Eremin-Solenikov <hidden> · 2013-11-12

STALE4580d

From: Russell King - ARM Linux <hidden>
Date: 2013-11-12 09:57:06
Also in: linux-arm-kernel

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?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help