arm: sa1100: add cpu clock for fbdev and pcmcia
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | arm: sa1100: add cpu clockarch/ | +34 | 0 replies | |
| 2/5 | arm: sa1100: add a clock alias for sa1111 pcmcia devicearch/ | +2 | 0 replies | |
| 3/5 | fbdev: sa1100fb: make use of device clockdrivers/ drivers/ | +18 | 0 replies | |
| 4/5 | pcmcia: sa1100: make use of device clockdrivers/ drivers/ | +13 | 0 replies | |
| 5/5 | pcmcia: sa1111: provide device clockdrivers/ | +4 | 0 replies |
Reviews trailers per patch
1 of 5 patches has a Reviewed-by or Acked-by.
| Patch | Tomi Valkeinen |
|---|---|
| 1/5 | |
| 2/5 | |
| 3/5 | A-b |
| 4/5 | |
| 5/5 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH RESEND 0/5] arm: sa1100: add cpu clock for fbdev and pcmcia
These patches are required to make SL-5500 (collie) to work properly. Framebuffer maintainer added his ack to the respective patch. PCMCIA subsystem seems to be unmaintained at this moment. Russell, could you please review and hopefully ack these patches?
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.