devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Collins <quic_collinsd@quicinc.com>
To: Rob Herring <robh+dt@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>, <devicetree@vger.kernel.org>
Cc: David Collins <quic_collinsd@quicinc.com>,
	Cristian Marussi <cristian.marussi@arm.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	"Subbaraman Narayanamurthy" <quic_subbaram@quicinc.com>
Subject: [PATCH v2 0/2] regulator: scmi: add support for registering SCMI regulators by name
Date: Mon, 21 Mar 2022 17:47:18 -0700	[thread overview]
Message-ID: <cover.1647909090.git.quic_collinsd@quicinc.com> (raw)

Add support to register SCMI regulator subnodes based on an SCMI
Voltage Domain name specified via the "arm,scmi-domain-name" device
tree property.  In doing so, make the "reg" property optional with
the constraint that at least one of "reg" or "arm,scmi-domain-name"
must be specified.  If both are specified, then both must match the
Voltage Domain data exposed by the SCMI platform.

Name based SCMI regulator registration helps ensure that an SCMI
agent doesn't need to be aware of the numbering scheme used for
Voltage Domains by the SCMI platform.  It also ensures that the
correct Voltage Domain is selected for a given physical regulator.
This cannot be guaranteed with numeric Voltage Domain IDs alone.

Changes in v2:
- Replaced usage of DT property "regulator-name" with "arm,scmi-domain-name".

v1 of this patch series can be found at [1].

[1]: https://lore.kernel.org/lkml/cover.1643069954.git.quic_collinsd@quicinc.com/T/

David Collins (2):
  dt-bindings: firmware: arm,scmi: define support for name based
    regulators
  regulator: scmi: add support for registering SCMI regulators by name

 .../bindings/firmware/arm,scmi.yaml           | 15 ++++-
 drivers/regulator/scmi-regulator.c            | 58 ++++++++++++++++++-
 2 files changed, 67 insertions(+), 6 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-03-22  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  0:47 David Collins [this message]
2022-03-22  0:47 ` [PATCH v2 1/2] dt-bindings: firmware: arm,scmi: define support for name based regulators David Collins
2022-03-22 11:40 ` [PATCH v2 0/2] regulator: scmi: add support for registering SCMI regulators by name Sudeep Holla
2022-03-23  1:12   ` David Collins
2022-03-24 17:23     ` Mark Brown
2022-03-25 10:35       ` 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=cover.1647909090.git.quic_collinsd@quicinc.com \
    --to=quic_collinsd@quicinc.com \
    --cc=broonie@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_subbaram@quicinc.com \
    --cc=robh+dt@kernel.org \
    --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).