From: "Rob Herring (Arm)" <robh@kernel.org>
To: David Dai <davidai@google.com>
Cc: Will Deacon <will@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Pavan Kondeti <quic_pkondeti@quicinc.com>,
devicetree@vger.kernel.org,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Conor Dooley <conor+dt@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@google.com>,
Quentin Perret <qperret@google.com>,
Gupta Pankaj <pankaj.gupta@amd.com>,
Marc Zyngier <maz@kernel.org>, Mel Gorman <mgorman@suse.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
kernel-team@android.com
Subject: Re: [PATCH v6 1/2] dt-bindings: cpufreq: add virtual cpufreq device
Date: Wed, 22 May 2024 10:00:54 -0500 [thread overview]
Message-ID: <171639005247.3294172.9981807951705426790.robh@kernel.org> (raw)
In-Reply-To: <20240521043102.2786284-2-davidai@google.com>
On Mon, 20 May 2024 21:30:51 -0700, David Dai wrote:
> Adding bindings to represent a virtual cpufreq device.
>
> Virtual machines may expose MMIO regions for a virtual cpufreq device
> for guests to read performance information or to request performance
> selection. The virtual cpufreq device has an individual controller for
> each performance domain. Performance points for a given domain can be
> normalized across all domains for ease of allowing for virtual machines
> to migrate between hosts.
>
> Co-developed-by: Saravana Kannan <saravanak@google.com>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
> Signed-off-by: David Dai <davidai@google.com>
> ---
> .../cpufreq/qemu,virtual-cpufreq.yaml | 48 +++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/cpufreq/qemu,virtual-cpufreq.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-05-22 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 4:30 [PATCH v6 0/2] Improve VM CPUfreq and task placement behavior David Dai
2024-05-21 4:30 ` [PATCH v6 1/2] dt-bindings: cpufreq: add virtual cpufreq device David Dai
2024-05-22 15:00 ` Rob Herring (Arm) [this message]
2024-05-21 4:30 ` [PATCH v6 2/2] cpufreq: add virtual-cpufreq driver David Dai
2024-06-27 21:22 ` David Dai
2024-06-28 12:01 ` Rafael J. Wysocki
2024-06-28 12:42 ` Sudeep Holla
2024-07-10 0:07 ` Saravana Kannan
2024-08-30 22:51 ` David Dai
2024-06-28 12:51 ` Sudeep Holla
2024-07-10 9:05 ` Marc Zyngier
2024-05-21 7:41 ` [PATCH v6 0/2] Improve VM CPUfreq and task placement behavior Viresh Kumar
2024-05-22 18:22 ` David Dai
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=171639005247.3294172.9981807951705426790.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davidai@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mgorman@suse.de \
--cc=mhiramat@google.com \
--cc=oliver.upton@linux.dev \
--cc=pankaj.gupta@amd.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=quic_pkondeti@quicinc.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®