primecell: make correct clock parsing possible
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 7 patches 0 repliesNew
1 of 7 patches is in this archive. The cover letter announces 7.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 4/7 | spi: pl022: attempt to get sspclk by name | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] primecell: make correct clock parsing possible
Quoted 7 lines · Mark Rutland
These patches attempt to harmonize the bindings and the drivers with what's in use today, in a backwards compatible fashion, relieving us of our present Kafkaesque nightmare. Each peripheral's clock(s) are given explicit names which can be used, though code will fall back to the existing behaviour if said names are not provided. Additionally the currently unmet ordering requirement of
apb_pclkis dropped, given all existing that code requires this to be named anyway.
The reason why these clocks ended up with NULL names was to force the issue that clocks shall not be named solely by their connection IDs, which was a major problem before DT. Now that we have DT, I'm happier to reinstate the names, but I think we should just reinstate the names we had previously. That should be in the git history.
The down-side is those names are all in capitals - but they were named after the signal name(s) given in the Primecell documentation.
Signature · 3 lines
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad. Estimate before purchase was "up to 13.2Mbit".