From: Rajendra Nayak <rnayak@codeaurora.org>
To: ulf.hansson@linaro.org, robh+dt@kernel.org, bjorn.andersson@linaro.org
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Rajendra Nayak <rnayak@codeaurora.org>
Subject: [PATCH 0/3] Add support for assigned-performance-states
Date: Tue, 4 Aug 2020 17:16:53 +0530 [thread overview]
Message-ID: <1596541616-27688-1-git-send-email-rnayak@codeaurora.org> (raw)
Some devics within power-domains with performance states do not
support DVFS, but still need to vote on a default/static state
while they are active. Add support for a new device tree property
which the clients can use to specify this and add support in
kernel to parse this value and vote.
Rajendra Nayak (3):
dt-bindings: power: Introduce 'assigned-performance-states' property
PM / Domains: Add support for 'assigned-performance-states'
arm64: dts: sc7180: Add assigned-performance-states for i2c
.../devicetree/bindings/power/power-domain.yaml | 47 ++++++++++++++++++++++
arch/arm64/boot/dts/qcom/sc7180.dtsi | 24 +++++++++++
drivers/base/power/domain.c | 27 +++++++++++++
include/linux/pm_domain.h | 1 +
4 files changed, 99 insertions(+)
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2020-08-04 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 11:46 Rajendra Nayak [this message]
2020-08-04 11:46 ` [PATCH 1/3] dt-bindings: power: Introduce 'assigned-performance-states' property Rajendra Nayak
2020-08-05 6:39 ` Stephen Boyd
2020-08-05 8:13 ` Rajendra Nayak
2020-08-05 23:57 ` Stephen Boyd
2020-08-04 11:46 ` [PATCH 2/3] PM / Domains: Add support for 'assigned-performance-states' Rajendra Nayak
2020-08-12 9:37 ` Ulf Hansson
2020-08-04 11:46 ` [PATCH 3/3] arm64: dts: sc7180: Add assigned-performance-states for i2c Rajendra Nayak
2020-08-05 6:41 ` Stephen Boyd
2020-08-05 8:14 ` Rajendra Nayak
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=1596541616-27688-1-git-send-email-rnayak@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@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 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.