From: Anson Huang <anson.huang@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"festevam@gmail.com" <festevam@gmail.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH V4 2/2] clk: imx: scu: add cpu frequency scaling support
Date: Fri, 22 Feb 2019 02:34:16 +0000 [thread overview]
Message-ID: <DB3PR0402MB3916D31F618C847E3504A564F57F0@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <155078210899.77512.5319038009555276321@swboyd.mtv.corp.google.com>
Hi, Stephen
Best Regards!
Anson Huang
> -----Original Message-----
> From: Stephen Boyd [mailto:sboyd@kernel.org]
> Sent: 2019年2月22日 4:48
> To: devicetree@vger.kernel.org; festevam@gmail.com;
> kernel@pengutronix.de; linux-arm-kernel@lists.infradead.org; linux-
> clk@vger.kernel.org; linux-kernel@vger.kernel.org; mark.rutland@arm.com;
> mturquette@baylibre.com; robh+dt@kernel.org; s.hauer@pengutronix.de;
> shawnguo@kernel.org; viresh.kumar@linaro.org; Aisheng Dong
> <aisheng.dong@nxp.com>; Anson Huang <anson.huang@nxp.com>; Daniel
> Baluta <daniel.baluta@nxp.com>
> Cc: dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH V4 2/2] clk: imx: scu: add cpu frequency scaling support
>
> Quoting Anson Huang (2019-02-13 17:54:08)
> > On NXP's i.MX SoCs with system controller inside, CPU frequency
> > scaling can ONLY be done by system controller firmware, and it can
> > ONLY be requested from secure mode, so Linux kernel has to call ARM
> > SMC to trap to ARM-Trusted-Firmware to request system controller
> > firmware to do CPU frequency scaling.
> >
> > This patch adds i.MX system controller CPU frequency scaling support,
> > it reuses cpufreq-dt driver and implement the CPU frequency scaling
> > inside SCU clock driver.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > ---
> > Changes since V3:
> > - use different clk ops for CPU clock to avoid runtime check in
> clk_set_rate;
> > - use rsrc_id to determine whether it is CPU frequency change and also
> to get
> > cluster ID for SMC call.
>
> This directly conflicts with a patch to add get/set parent support from
> Aisheng Dong. Can you please work together and rebase the patch on top of
> that patch (which is in clk-next) and resend this?
I have resent the patch set based on top of clk-next and tested the function.
Please apply this resent patch, https://patchwork.kernel.org/patch/10825085/
Thanks,
Anson.
next prev parent reply other threads:[~2019-02-22 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 1:54 [PATCH V4 1/2] arm64: dts: freescale: imx8qxp: add cpu opp table Anson Huang
2019-02-14 1:54 ` [PATCH V4 2/2] clk: imx: scu: add cpu frequency scaling support Anson Huang
2019-02-15 23:58 ` Stephen Boyd
2019-02-16 0:41 ` Anson Huang
2019-02-21 20:48 ` Stephen Boyd
2019-02-22 2:34 ` Anson Huang [this message]
2019-02-14 7:12 ` [PATCH V4 1/2] arm64: dts: freescale: imx8qxp: add cpu opp table Viresh Kumar
2019-02-14 7:18 ` Anson Huang
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=DB3PR0402MB3916D31F618C847E3504A564F57F0@DB3PR0402MB3916.eurprd04.prod.outlook.com \
--to=anson.huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.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).