From: Rob Herring <robh@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: vincent.guittot@linaro.org, Jonathan.Cameron@Huawei.com,
lukasz.luba@arm.com, james.quinlan@broadcom.com,
linux-arm-kernel@lists.infradead.org, satyakim@qti.qualcomm.com,
f.fainelli@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, souvik.chakravarty@arm.com,
etienne.carriere@linaro.org, sudeep.holla@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] dt-bindings: arm: add support for SCMI Regulators
Date: Thu, 5 Nov 2020 11:39:04 -0600 [thread overview]
Message-ID: <20201105173904.GA1528783@bogus> (raw)
In-Reply-To: <20201102173238.4515-6-cristian.marussi@arm.com>
On Mon, 02 Nov 2020 17:32:38 +0000, Cristian Marussi wrote:
> Add devicetree bindings to support regulators based on SCMI Voltage
> Domain Protocol.
>
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> v3 --> v4
> - added list of supported Regulator bindings.
> v2 --> v3
> - avoid awkard examples based on _cpu/_gpu regulators
> v1 --> v2
> - removed any reference to negative voltages
> ---
> .../devicetree/bindings/arm/arm,scmi.txt | 43 +++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-11-05 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 17:32 [PATCH v4 0/5] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator Cristian Marussi
2020-11-02 17:32 ` [PATCH v4 1/5] firmware: arm_scmi: Add Voltage Domain Support Cristian Marussi
2020-11-02 17:32 ` [PATCH v4 2/5] firmware: arm_scmi: add SCMI Voltage Domain devname Cristian Marussi
2020-11-02 17:32 ` [PATCH v4 3/5] regulator: core: add of_match_full_name boolean flag Cristian Marussi
2020-11-02 17:32 ` [PATCH v4 4/5] regulator: add SCMI driver Cristian Marussi
2020-11-02 17:32 ` [PATCH v4 5/5] dt-bindings: arm: add support for SCMI Regulators Cristian Marussi
2020-11-05 17:39 ` Rob Herring [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=20201105173904.GA1528783@bogus \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.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=satyakim@qti.qualcomm.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@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 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).