From: Viresh Kumar <viresh.kumar@linaro.org>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, heiko@sntech.de
Subject: Re: [PATCH 2/2] cpufreq: dt: add support for rockchip rv1108
Date: Wed, 13 Sep 2017 12:18:40 -0700 [thread overview]
Message-ID: <20170913191840.GB11836@ubuntu> (raw)
In-Reply-To: <1503306624-28937-1-git-send-email-andy.yan@rock-chips.com>
On 21-08-17, 17:10, Andy Yan wrote:
> Add the compatible string to support the generic device tree
> cpufreq-dt driver on rockchip rv1108 soc.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
> ---
>
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 1c26292..2d71c09 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -69,6 +69,7 @@ static const struct of_device_id machines[] __initconst = {
> { .compatible = "renesas,r8a7794", },
> { .compatible = "renesas,sh73a0", },
>
> + { .compatible = "rockchip,rv1108", },
> { .compatible = "rockchip,rk2928", },
> { .compatible = "rockchip,rk3036", },
> { .compatible = "rockchip,rk3066a", },
You use operating-points-v2 or the V1 bindings for this SoC? The SoCs using
operating-points-v2 don't need such changes anymore.
--
viresh
next prev parent reply other threads:[~2017-09-13 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 9:06 [PATCH 1/2] ARM: dts: rockchip: add cpu opp table for rv1108 Andy Yan
2017-08-21 9:10 ` [PATCH 2/2] cpufreq: dt: add support for rockchip rv1108 Andy Yan
2017-08-22 22:54 ` Heiko Stuebner
2017-09-13 19:18 ` Viresh Kumar [this message]
2017-09-14 0:52 ` Andy Yan
2017-09-19 18:48 ` Viresh Kumar
2017-08-21 15:30 ` [PATCH 1/2] ARM: dts: rockchip: add cpu opp table for rv1108 Heiko Stuebner
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=20170913191840.GB11836@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=andy.yan@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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