From: Viresh Kumar <viresh.kumar@linaro.org>
To: Finley Xiao <finley.xiao@rock-chips.com>
Cc: heiko@sntech.de, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, jay.xu@rock-chips.com,
huangtao@rock-chips.coms, tony.xie@rock-chips.com,
cl@rock-chips.com
Subject: Re: [PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver
Date: Fri, 4 Aug 2017 10:40:41 +0530 [thread overview]
Message-ID: <20170804051041.GB28857@vireshk-i7> (raw)
In-Reply-To: <1501811551-39168-1-git-send-email-finley.xiao@rock-chips.com>
On 04-08-17, 09:52, Finley Xiao wrote:
> This patch adds the rk3328 compatible string for supporting
> the generic cpufreq driver on RK3328.
>
> Signed-off-by: Finley Xiao <finley.xiao@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 096aea7..13c0c47 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -76,6 +76,7 @@ static const struct of_device_id machines[] __initconst = {
> { .compatible = "rockchip,rk3188", },
> { .compatible = "rockchip,rk3228", },
> { .compatible = "rockchip,rk3288", },
> + { .compatible = "rockchip,rk3328", },
> { .compatible = "rockchip,rk3366", },
> { .compatible = "rockchip,rk3368", },
> { .compatible = "rockchip,rk3399", },
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2017-08-04 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 1:52 [PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver Finley Xiao
2017-08-04 5:10 ` Viresh Kumar [this message]
2017-08-09 22:49 ` Rafael J. Wysocki
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=20170804051041.GB28857@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=cl@rock-chips.com \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.coms \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tony.xie@rock-chips.com \
/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