linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding
@ 2015-07-13  6:58 Javier Martinez Canillas
  2015-07-23  8:19 ` Chanwoo Choi
  0 siblings, 1 reply; 5+ messages in thread
From: Javier Martinez Canillas @ 2015-07-13  6:58 UTC (permalink / raw)
  To: linux-arm-kernel

The exynos-ppmu driver is only a clock consumer and not a clock provider
but its Device Tree binding listed #clock-cells as an optional property.

Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>

---

 Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt | 1 -
 1 file changed, 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt b/Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt
index b54bf3a2ff57..aed486692880 100644
--- a/Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt
+++ b/Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt
@@ -17,7 +17,6 @@ Required properties:
 Optional properties:
 - clock-names : the name of clock used by the PPMU, "ppmu"
 - clocks : phandles for clock specified in "clock-names" property
-- #clock-cells: should be 1.
 
 Example1 : PPMU nodes in exynos3250.dtsi are listed below.
 
-- 
2.4.3

^ permalink raw reply related	[flat|nested] 5+ messages in thread
[parent not found: <1733224792.341671438577931309.JavaMail.weblogic@epmlwas06d>]

end of thread, other threads:[~2015-08-03  7:38 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-13  6:58 [PATCH] PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding Javier Martinez Canillas
2015-07-23  8:19 ` Chanwoo Choi
2015-07-23  8:30   ` Javier Martinez Canillas
2015-07-31  9:37     ` Javier Martinez Canillas
     [not found] <1733224792.341671438577931309.JavaMail.weblogic@epmlwas06d>
2015-08-03  7:38 ` Javier Martinez Canillas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).