From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Kukjin Kim <kgene@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH] PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding
Date: Mon, 13 Jul 2015 08:58:51 +0200 [thread overview]
Message-ID: <1436770732-9430-1-git-send-email-javier@osg.samsung.com> (raw)
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
next reply other threads:[~2015-07-13 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:58 Javier Martinez Canillas [this message]
2015-07-23 8:19 ` [PATCH] PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding Chanwoo Choi
2015-07-23 8:30 ` Javier Martinez Canillas
2015-07-31 9:37 ` Javier Martinez Canillas
-- strict thread matches above, loose matches on Subject: below --
2015-08-03 4:58 MyungJoo Ham
2015-08-03 7:38 ` Javier Martinez Canillas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436770732-9430-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=cw00.choi@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox