Thread (31 messages) 31 messages, 4 authors, 2013-12-22
STALE4599d
Revisions (23)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v1 [diff vs current]
  6. v1 [diff vs current]
  7. v1 [diff vs current]
  8. v1 [diff vs current]
  9. v1 [diff vs current]
  10. v1 [diff vs current]
  11. v4 [diff vs current]
  12. v4 [diff vs current]
  13. v4 [diff vs current]
  14. v4 [diff vs current]
  15. v4 [diff vs current]
  16. v4 [diff vs current]
  17. v4 [diff vs current]
  18. v4 [diff vs current]
  19. v5 [diff vs current]
  20. v4 [diff vs current]
  21. v5 [diff vs current]
  22. v5 [diff vs current]
  23. v5 current

[RFC PATCH v5 1/4] cpufreq: Add a cpufreq driver for Marvell Dove

From: Jason Cooper <hidden>
Date: 2013-12-21 19:25:01
Also in: linux-pm 

Andrew,

On Sat, Dec 21, 2013 at 05:26:45PM +0100, Andrew Lunn wrote:
quoted
quoted
+Dove cpufreq driver
+-------------------
+
+The Dove cpufreq driver makes use of the pmu node in the device tree.
I would prefer to reword this to make it OS-agnostic.  The cpufreq
driver is Linux-specific.
Why is it Linux specific? 
I'll admit I may be bike-shedding here, and I'm more seeking
opinion/clarification than mandating anything.  The above sentence,
imho, is describing how Linux/FreeBSD uses the node, not describing the
hardware.

thx,

Jason.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help