From: Cristian Marussi <cristian.marussi@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Cc: sudeep.holla@arm.com, james.quinlan@broadcom.com,
Jonathan.Cameron@Huawei.com, f.fainelli@gmail.com,
etienne.carriere@linaro.org, vincent.guittot@linaro.org,
daniel.lezcano@linaro.org, tarek.el-sherbiny@arm.com,
adrian.slatineanu@arm.com, souvik.chakravarty@arm.com,
wleavitt@marvell.com, wbartczak@marvell.com,
dan.carpenter@oracle.com, lukasz.luba@arm.com,
Cristian Marussi <cristian.marussi@arm.com>
Subject: [PATCH v2 0/3] Add ARM SCMI Powercap driver
Date: Tue, 6 Sep 2022 15:23:34 +0100 [thread overview]
Message-ID: <20220906142337.1697569-1-cristian.marussi@arm.com> (raw)
Hi all,
this short series builts on top of recently introduced SCMI v3.1 Powercap
protocol to implement an ARM SCMI Powercap driver which takes care to
expose via the Powercap framework all the SCMI Powercap zones that have
been discovered asking the SCMI platform firmware.
Basic testing has been performed against an emulated SCMI platform
supporting SCMIv3.1 Powercap protocol using powercap-utils.
A couple of fixes spotted with Smatch by Dan are queued on top of the
driver itself; these may have to be squashed finally into the driver itself
but for now I have just added them here as patches on top, for clarity and
to preserve authorship.
The series is based on sudeep/for-next/scmi [1] on top of
commit 40d30cf680cb ("firmware: arm_scmi: Harmonize SCMI tracing message format")
Thanks,
Cristian
---
v1 --> v2
- using clamp_t() to simplify normalizations
- cleanup style in block of var declarations
- refactor scale conversions code
- add MAINTAINER entry
- refactored normalizations and added dev_dbg
Cristian Marussi (1):
powercap: arm_scmi: Add SCMI Powercap based driver
Dan Carpenter (2):
powercap: arm_scmi: Fix signedness bug in probe
powercap: arm_scmi: Fix a NULL vs IS_ERR() bug
MAINTAINERS | 1 +
drivers/powercap/Kconfig | 13 +
drivers/powercap/Makefile | 1 +
drivers/powercap/arm_scmi_powercap.c | 509 +++++++++++++++++++++++++++
4 files changed, 524 insertions(+)
create mode 100644 drivers/powercap/arm_scmi_powercap.c
--
2.32.0
next reply other threads:[~2022-09-06 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 14:23 Cristian Marussi [this message]
2022-09-06 14:23 ` [PATCH v2 1/3] powercap: arm_scmi: Add SCMI Powercap based driver Cristian Marussi
2022-10-07 15:09 ` Rafael J. Wysocki
2022-10-07 15:39 ` Cristian Marussi
2022-10-10 9:21 ` Sudeep Holla
2022-10-10 13:14 ` Lukasz Luba
2022-09-06 14:23 ` [PATCH v2 2/3] powercap: arm_scmi: Fix signedness bug in probe Cristian Marussi
2022-09-06 14:23 ` [PATCH v2 3/3] powercap: arm_scmi: Fix a NULL vs IS_ERR() bug Cristian Marussi
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=20220906142337.1697569-1-cristian.marussi@arm.com \
--to=cristian.marussi@arm.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=adrian.slatineanu@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=etienne.carriere@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=tarek.el-sherbiny@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=wbartczak@marvell.com \
--cc=wleavitt@marvell.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).