From: Heiko Stuebner <heiko@sntech.de>
To: cl@rock-chips.com
Cc: 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, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: rockchip: add cpu regulator for rk3328 evaluation board
Date: Fri, 25 Aug 2017 11:35:41 +0200 [thread overview]
Message-ID: <3733498.rByIbfHvAf@phil> (raw)
In-Reply-To: <1503542223-21044-4-git-send-email-cl@rock-chips.com>
Am Donnerstag, 24. August 2017, 10:37:03 CEST schrieb cl@rock-chips.com:
> From: Liang Chen <cl@rock-chips.com>
>
> RK3328 Evaluation Board use rk805 pmic, and one of the DCDCs in
> rk805 is for cpu regulator, assign the cpu regulator, so the
> cpufreq can work fine.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
applied ... but I cannot say if it will still be eligible for 4.14
(late in the cycle). If necessary I'll move it forward a release.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] arm64: dts: rockchip: add cpu regulator for rk3328 evaluation board
Date: Fri, 25 Aug 2017 11:35:41 +0200 [thread overview]
Message-ID: <3733498.rByIbfHvAf@phil> (raw)
In-Reply-To: <1503542223-21044-4-git-send-email-cl@rock-chips.com>
Am Donnerstag, 24. August 2017, 10:37:03 CEST schrieb cl at rock-chips.com:
> From: Liang Chen <cl@rock-chips.com>
>
> RK3328 Evaluation Board use rk805 pmic, and one of the DCDCs in
> rk805 is for cpu regulator, assign the cpu regulator, so the
> cpufreq can work fine.
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
applied ... but I cannot say if it will still be eligible for 4.14
(late in the cycle). If necessary I'll move it forward a release.
Thanks
Heiko
next prev parent reply other threads:[~2017-08-25 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 2:37 [PATCH v1 0/3] Enable some devices for rk3328 evaluation board cl
2017-08-24 2:37 ` cl
2017-08-24 2:37 ` cl at rock-chips.com
2017-08-24 2:37 ` [PATCH v2 1/3] arm64: dts: rockchip: add mmc nodes " cl
2017-08-24 2:37 ` cl
2017-08-24 2:37 ` cl at rock-chips.com
2017-08-25 9:34 ` Heiko Stuebner
2017-08-25 9:34 ` Heiko Stuebner
2017-08-24 2:37 ` [PATCH v2 2/3] cpufreq: rockchip: add support for rk3328 soc cl
2017-08-24 2:37 ` cl
2017-08-24 2:37 ` cl at rock-chips.com
2017-08-25 9:29 ` Heiko Stuebner
2017-08-25 9:29 ` Heiko Stuebner
2017-08-24 2:37 ` [PATCH v2 3/3] arm64: dts: rockchip: add cpu regulator for rk3328 evaluation board cl
2017-08-24 2:37 ` cl at rock-chips.com
2017-08-25 9:35 ` Heiko Stuebner [this message]
2017-08-25 9:35 ` 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=3733498.rByIbfHvAf@phil \
--to=heiko@sntech.de \
--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=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=viresh.kumar@linaro.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.