linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, robh@kernel.org,
	satyakim@qti.qualcomm.com, sudeep.holla@arm.com,
	broonie@kernel.org, james.quinlan@broadcom.com,
	Jonathan.Cameron@Huawei.com, etienne.carriere@linaro.org,
	lukasz.luba@arm.com
Subject: Re: [PATCH 0/4] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator
Date: Fri, 9 Oct 2020 13:42:48 +0100	[thread overview]
Message-ID: <20201009124056.GB32363@e119603-lin.cambridge.arm.com> (raw)
In-Reply-To: <8483165a-e413-b2f8-bd33-6da07fe56d62@gmail.com>

On Mon, Oct 05, 2020 at 05:38:52PM -0700, Florian Fainelli wrote:
> 
> 
> On 10/5/2020 3:26 PM, Cristian Marussi wrote:
> >Hi,
> >
> >this series introduces the support for the new SCMI Voltage Domain Protocol
> >defined by the upcoming SCMIv3.0 specification, whose BETA release is
> >available at [1].
> >
> >Afterwards, a new generic SCMI Regulator driver is developed on top of the
> >new SCMI VD Protocol.
> >
> >The series is currently based on for-next/scmi [2] on top of:
> >
> >commit 66d90f6ecee7 ("firmware: arm_scmi: Enable building as a single
> >		     module")
> >
> >Any feedback welcome,
> 
> Well, this is just great! We were right about to develop a proprietary SCMI
> protocol in order to control a locked down PMIC accessible behind a secured
> firmware. We would have done essentially just that since the use case is to
> control the various regulators exposed by this PMIC over SCMI. Thanks a lot!
> 

You're welcome :D ... any feedback from your independent testing will be
appreciated.

Thanks

Cristian
> >
> >Thanks,
> >
> >Cristian
> >
> >[1]:https://developer.arm.com/documentation/den0056/c/
> >[2]:https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/log/?h=for-next/scmi
> >
> >
> >Cristian Marussi (4):
> >   firmware: arm_scmi: Add Voltage Domain Support
> >   firmware: arm_scmi: add SCMI Voltage Domain devname
> >   regulator: add SCMI driver
> >   dt-bindings: arm: add support for SCMI Regulators
> >
> >  .../devicetree/bindings/arm/arm,scmi.txt      |  44 ++
> >  drivers/firmware/arm_scmi/Makefile            |   2 +-
> >  drivers/firmware/arm_scmi/common.h            |   1 +
> >  drivers/firmware/arm_scmi/driver.c            |   3 +
> >  drivers/firmware/arm_scmi/voltage.c           | 378 ++++++++++++++
> >  drivers/regulator/Kconfig                     |   9 +
> >  drivers/regulator/Makefile                    |   1 +
> >  drivers/regulator/scmi-regulator.c            | 488 ++++++++++++++++++
> >  include/linux/scmi_protocol.h                 |  64 +++
> >  9 files changed, 989 insertions(+), 1 deletion(-)
> >  create mode 100644 drivers/firmware/arm_scmi/voltage.c
> >  create mode 100644 drivers/regulator/scmi-regulator.c
> >
> 
> -- 
> Florian

      reply	other threads:[~2020-10-09 12:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 22:26 [PATCH 0/4] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator Cristian Marussi
2020-10-05 22:26 ` [PATCH 1/4] firmware: arm_scmi: Add Voltage Domain Support Cristian Marussi
2020-10-08 10:10   ` Etienne Carriere
2020-10-09 12:37     ` Cristian Marussi
2020-10-05 22:26 ` [PATCH 2/4] firmware: arm_scmi: add SCMI Voltage Domain devname Cristian Marussi
2020-10-05 22:26 ` [PATCH 3/4] regulator: add SCMI driver Cristian Marussi
2020-10-06 10:56   ` Mark Brown
2020-10-15 15:38     ` Cristian Marussi
2020-10-05 22:26 ` [PATCH 4/4] dt-bindings: arm: add support for SCMI Regulators Cristian Marussi
2020-10-06 10:59   ` Mark Brown
2020-10-07  8:06     ` Cristian Marussi
2020-10-06  0:38 ` [PATCH 0/4] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator Florian Fainelli
2020-10-09 12:42   ` Cristian Marussi [this message]

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=20201009124056.GB32363@e119603-lin.cambridge.arm.com \
    --to=cristian.marussi@arm.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=broonie@kernel.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=lukasz.luba@arm.com \
    --cc=robh@kernel.org \
    --cc=satyakim@qti.qualcomm.com \
    --cc=sudeep.holla@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).