devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Anson Huang <anson.huang@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
	"heiko@sntech.de" <heiko@sntech.de>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
	Andy Gross <andy.gross@linaro.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"marc.w.gonzalez@free.fr" <marc.w.gonzalez@free.fr>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"enric.balletbo@collabora.com" <enric.balletbo@collabora.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"horms+renesas@verge.net.au" <horms+renesas@verge.net.au>,
	Daniel Baluta <daniel.baluta@nxp.com>, linux-arm-
Subject: Re: [PATCH 3/3] cpufreq: imx-sc: add i.mx system controller cpufreq support
Date: Wed, 13 Feb 2019 15:45:02 +0530	[thread overview]
Message-ID: <20190213101502.v75d3nfwctcks2gx@vireshk-i7> (raw)
In-Reply-To: <DB3PR0402MB391662EC01B6160C1AA9A540F5660@DB3PR0402MB3916.eurprd04.prod.outlook.com>

On 13-02-19, 08:53, Anson Huang wrote:
> Forgot to mention, i.MX system controller cpufreq actually can NOT do any CPU
> clock/voltage scaling from Linux kernel, they are controlled by system controller
> firmware and ONLY can be requested via RPC with secure mode, so Linux kernel
> has to call SMC and trap to ARM-Trusted-Firmware to do it, in this case, is cpufreq-dt
> still suitable to support it? I saw cpufreq-dt driver will do CPU clock/voltage scaling
> directly.

What about moving those SMC calls to the clk-driver, then it wouldn't
matter to the cpufreq driver on how the clock is getting changed.

-- 
viresh

  reply	other threads:[~2019-02-13 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  3:08 [PATCH 1/3] arm64: dts: freescale: imx8qxp: add cpu opp table Anson Huang
2019-02-13  3:09 ` [PATCH 2/3] arm64: defconfig: enable i.mx system controller cpufreq Anson Huang
2019-02-13  3:09 ` [PATCH 3/3] cpufreq: imx-sc: add i.mx system controller cpufreq support Anson Huang
2019-02-13  7:09   ` Viresh Kumar
2019-02-13  8:46     ` Anson Huang
2019-02-13  8:53       ` Anson Huang
2019-02-13 10:15         ` Viresh Kumar [this message]
2019-02-13 10:35           ` Anson Huang
2019-02-13 10:12       ` Viresh Kumar

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=20190213101502.v75d3nfwctcks2gx@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=anson.huang@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=festevam@gmail.com \
    --cc=heiko@sntech.de \
    --cc=horms+renesas@verge.net.au \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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 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).