Armada 370/XP clocksource fixes
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest0 of 6 patches 0 repliesNew
- v12 of 5 patches 0 repliesSuperseded
Patches in v2 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Andrew Lunn |
|---|---|
| Series | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/6] Armada 370/XP clocksource fixes
Quoted 21 lines · Ezequiel Garcia
This small patchset fixes a somewhat minor issue found in the clocksource driver for Armada 370/XP SoC.
On one side the Armada 370 SoC has no 25 MHz fixed timer.
On the other side the Armada XP SoC cannot work properly without such 25 MHz fixed timer selected, because otherwise the base clock frequency would vary when doing cpufreq frequency changes.Therefore we can consider the SoCs as not being compatible, being better to have two compatible strings, one for each SoC. The previous compatible and its behavior has been maintained to preserve backwards compatibility.
In addition,
CLOCKSOURCE_OF_DECLAREis used to simplify the initialization.This patchset is based on v3.11-rc4. Also, to ease maintainer's task this is based on these two patches which are in linux-next:
commit
be14114934545f52be2ffddbe401ba0951007c59
Author: Stephen Boyd <[email protected]> "clocksource: time-armada-370-xp: Divorce from local timer API"
Quoted 5 lines
commit
4047c794ae18c467a5ea987265238186bc253f61
Author: Stephen Boyd <[email protected]> "clocksource: time-armada-370-xp: Fix sparse warning"Any testing and feedback is highly appreciated!
Hi Ezequiel
Sorry, i don't have access to hardware to test on at the moment.
Andrew