From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding
Date: Thu, 23 Jul 2015 17:19:02 +0900 [thread overview]
Message-ID: <55B0A376.2080906@samsung.com> (raw)
In-Reply-To: <1436770732-9430-1-git-send-email-javier@osg.samsung.com>
Hi Javier,
On 07/13/2015 03:58 PM, Javier Martinez Canillas wrote:
> 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.
>
>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
+ Devfreq maintainer (Myungjoo Ham)
I think that this patch will be more appropriate on devfreq git tree
than linux-samsung git tree.
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2015-07-23 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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=55B0A376.2080906@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).