RFC clk: qoriq: Move chip-specific knowledge into driver
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 8 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 8 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver
Quoted 9 lines · Michael Turquette
Hi Scott,
Quoting Scott Wood (2015-06-18 19:49:10)
Quoted 5 lines
The existing device tree bindings are error-prone and inflexible. Correct the mistake by moving the knowledge into the driver, which has more flexibility in describing the quirks of each chip. This leaves the device tree to its proper role of identifying a programming interface rather than describing its individual registers.
Quoted 7 lines
Sorry for not responding to this one sooner. Fell through the cracks.
All of the changes to
drives/clk/clk-qoriq.clook great to me. I assume you need to keep all of these patches together and want to the take through the freescale tree? If so feel free to add,
I just sent a non-RFC v2, with improved compatibility with old device trees (especially ls1021a). It depends on the cpufreq patch though (at least, to avoid breaking qoriq-cpufreq until that patch is merged), so I'll also need an ack from Rafael for that if I'm taking it through my tree.
-Scott