All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: cl@rock-chips.com
Cc: heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com,
	catalin.marinas@arm.com, will.deacon@arm.com,
	shawnguo@kernel.org, rocky.hao@rock-chips.com, afaerber@suse.de,
	fabio.estevam@nxp.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	shawn.lin@rock-chips.com, kever.yang@rock-chips.com,
	rjw@rjwysocki.net, linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 2/3] cpufreq: rockchip: add support for rk3328 soc
Date: Thu, 14 Sep 2017 14:24:37 -0700	[thread overview]
Message-ID: <20170914212437.GC11836@ubuntu> (raw)
In-Reply-To: <1503477632-9661-3-git-send-email-cl@rock-chips.com>

On 23-08-17, 16:40, cl@rock-chips.com wrote:
> From: Liang Chen <cl@rock-chips.com>
> 
> Add compatible rockchip,rk3328 to the machines table to
> launch cpufreq-dt driver for rk3328 soc.
> 
> Signed-off-by: Liang Chen <cl@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..f16c3ba 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -76,6 +76,7 @@
>  	{ .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

WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/3] cpufreq: rockchip: add support for rk3328 soc
Date: Thu, 14 Sep 2017 14:24:37 -0700	[thread overview]
Message-ID: <20170914212437.GC11836@ubuntu> (raw)
In-Reply-To: <1503477632-9661-3-git-send-email-cl@rock-chips.com>

On 23-08-17, 16:40, cl at rock-chips.com wrote:
> From: Liang Chen <cl@rock-chips.com>
> 
> Add compatible rockchip,rk3328 to the machines table to
> launch cpufreq-dt driver for rk3328 soc.
> 
> Signed-off-by: Liang Chen <cl@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..f16c3ba 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -76,6 +76,7 @@
>  	{ .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

  reply	other threads:[~2017-09-14 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  8:40 [PATCH v1 0/3] Enable some devices for rk3328 evaluation board cl
2017-08-23  8:40 ` cl at rock-chips.com
2017-08-23  8:40 ` cl-TNX95d0MmH7DzftRWevZcw
2017-08-23  8:40 ` [PATCH v1 1/3] arm64: dts: rockchip: add mmc nodes " cl
2017-08-23  8:40   ` cl at rock-chips.com
2017-08-23  8:40   ` cl
2017-08-23  9:58   ` Shawn Lin
2017-08-23  9:58     ` Shawn Lin
2017-08-23  8:40 ` [PATCH v1 2/3] cpufreq: rockchip: add support for rk3328 soc cl
2017-08-23  8:40   ` cl at rock-chips.com
2017-09-14 21:24   ` Viresh Kumar [this message]
2017-09-14 21:24     ` Viresh Kumar
2017-08-23  8:40 ` [PATCH v1 3/3] arm64: dts: rockchip: add cpu regulator for rk3328 evaluation board cl
2017-08-23  8:40   ` cl at rock-chips.com

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=20170914212437.GC11836@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=afaerber@suse.de \
    --cc=catalin.marinas@arm.com \
    --cc=cl@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=heiko@sntech.de \
    --cc=kever.yang@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=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=rocky.hao@rock-chips.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=shawnguo@kernel.org \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.