From: David Collins <collinsd@codeaurora.org> To: broonie@kernel.org, lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com Cc: David Collins <collinsd@codeaurora.org>, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, rnayak@codeaurora.org, sboyd@kernel.org, dianders@chromium.org Subject: [PATCH v2 0/2] regulator: add QCOM RPMh regulator driver Date: Fri, 13 Apr 2018 19:50:33 -0700 [thread overview] Message-ID: <cover.1523673467.git.collinsd@codeaurora.org> (raw) Hello, This patch series adds a driver and device tree binding documentation for PMIC regulator control via Resource Power Manager-hardened (RPMh) on some Qualcomm Technologies, Inc. SoCs such as SDM845. RPMh is a hardware block which contains several accelerators which are used to manage various hardware resources that are shared between the processors of the SoC. The final hardware state of a regulator is determined within RPMh by performing max aggregation of the requests made by all of the processors. The RPMh regulator driver depends upon the RPMh driver [1] and command DB driver [2] which are both still undergoing review. Changes since v1 [3]: - Addressed review feedback from Doug, Mark, and Stephen - Replaced set_voltage()/get_voltage() callbacks with set_voltage_sel()/ get_voltage_sel() - Added set_bypass()/get_bypass() callbacks for BOB pass-through mode control - Removed top-level PMIC data structures - Removed initialization variables from structs and passed them as function parameters - Removed various comments and error messages - Simplified mode handling - Refactored per-PMIC rpmh-regulator data specification - Simplified probe function - Moved header into DT patch - Removed redundant property listings from DT binding documentation Thanks, David [1]: https://lkml.org/lkml/2018/4/5/480 [2]: https://lkml.org/lkml/2018/4/10/714 [3]: https://lkml.org/lkml/2018/3/16/1431 David Collins (2): regulator: dt-bindings: add QCOM RPMh regulator bindings regulator: add QCOM RPMh regulator driver .../bindings/regulator/qcom,rpmh-regulator.txt | 207 +++++ drivers/regulator/Kconfig | 9 + drivers/regulator/Makefile | 1 + drivers/regulator/qcom_rpmh-regulator.c | 910 +++++++++++++++++++++ .../dt-bindings/regulator/qcom,rpmh-regulator.h | 36 + 5 files changed, 1163 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt create mode 100644 drivers/regulator/qcom_rpmh-regulator.c create mode 100644 include/dt-bindings/regulator/qcom,rpmh-regulator.h -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: collinsd@codeaurora.org (David Collins) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/2] regulator: add QCOM RPMh regulator driver Date: Fri, 13 Apr 2018 19:50:33 -0700 [thread overview] Message-ID: <cover.1523673467.git.collinsd@codeaurora.org> (raw) Hello, This patch series adds a driver and device tree binding documentation for PMIC regulator control via Resource Power Manager-hardened (RPMh) on some Qualcomm Technologies, Inc. SoCs such as SDM845. RPMh is a hardware block which contains several accelerators which are used to manage various hardware resources that are shared between the processors of the SoC. The final hardware state of a regulator is determined within RPMh by performing max aggregation of the requests made by all of the processors. The RPMh regulator driver depends upon the RPMh driver [1] and command DB driver [2] which are both still undergoing review. Changes since v1 [3]: - Addressed review feedback from Doug, Mark, and Stephen - Replaced set_voltage()/get_voltage() callbacks with set_voltage_sel()/ get_voltage_sel() - Added set_bypass()/get_bypass() callbacks for BOB pass-through mode control - Removed top-level PMIC data structures - Removed initialization variables from structs and passed them as function parameters - Removed various comments and error messages - Simplified mode handling - Refactored per-PMIC rpmh-regulator data specification - Simplified probe function - Moved header into DT patch - Removed redundant property listings from DT binding documentation Thanks, David [1]: https://lkml.org/lkml/2018/4/5/480 [2]: https://lkml.org/lkml/2018/4/10/714 [3]: https://lkml.org/lkml/2018/3/16/1431 David Collins (2): regulator: dt-bindings: add QCOM RPMh regulator bindings regulator: add QCOM RPMh regulator driver .../bindings/regulator/qcom,rpmh-regulator.txt | 207 +++++ drivers/regulator/Kconfig | 9 + drivers/regulator/Makefile | 1 + drivers/regulator/qcom_rpmh-regulator.c | 910 +++++++++++++++++++++ .../dt-bindings/regulator/qcom,rpmh-regulator.h | 36 + 5 files changed, 1163 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt create mode 100644 drivers/regulator/qcom_rpmh-regulator.c create mode 100644 include/dt-bindings/regulator/qcom,rpmh-regulator.h -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
next reply other threads:[~2018-04-14 2:50 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-14 2:50 David Collins [this message] 2018-04-14 2:50 ` [PATCH v2 0/2] regulator: add QCOM RPMh regulator driver David Collins 2018-04-14 2:50 ` [PATCH v2 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings David Collins 2018-04-14 2:50 ` David Collins 2018-04-14 2:50 ` David Collins 2018-04-16 20:57 ` Rob Herring 2018-04-16 20:57 ` Rob Herring 2018-04-16 22:06 ` David Collins 2018-04-16 22:06 ` David Collins 2018-04-17 20:06 ` Doug Anderson 2018-04-17 20:06 ` Doug Anderson 2018-04-18 21:44 ` David Collins 2018-04-18 21:44 ` David Collins 2018-05-02 16:37 ` Doug Anderson 2018-05-02 16:37 ` Doug Anderson 2018-05-03 0:13 ` David Collins 2018-05-03 0:13 ` David Collins 2018-05-03 15:01 ` Doug Anderson 2018-05-03 15:01 ` Doug Anderson 2018-04-14 2:50 ` [PATCH v2 2/2] regulator: add QCOM RPMh regulator driver David Collins 2018-04-14 2:50 ` David Collins 2018-04-17 18:23 ` [v2,2/2] " Matthias Kaehlcke 2018-04-17 18:23 ` Matthias Kaehlcke 2018-04-17 19:15 ` David Collins 2018-04-17 19:15 ` David Collins 2018-04-17 19:47 ` Matthias Kaehlcke 2018-04-17 19:47 ` Matthias Kaehlcke 2018-04-18 21:34 ` David Collins 2018-04-18 21:34 ` David Collins 2018-04-18 17:02 ` Mark Brown 2018-04-18 17:02 ` Mark Brown 2018-04-17 20:02 ` [PATCH v2 2/2] " Doug Anderson 2018-04-17 20:02 ` Doug Anderson 2018-04-18 23:30 ` David Collins 2018-04-18 23:30 ` David Collins 2018-04-19 6:04 ` Stephen Boyd 2018-04-19 6:04 ` Stephen Boyd 2018-04-19 16:16 ` Doug Anderson 2018-04-19 16:16 ` Doug Anderson 2018-04-20 22:08 ` David Collins 2018-04-20 22:08 ` David Collins 2018-04-24 17:45 ` Mark Brown 2018-04-24 17:45 ` Mark Brown 2018-04-24 21:09 ` David Collins 2018-04-24 21:09 ` David Collins 2018-04-25 10:31 ` Mark Brown 2018-04-25 10:31 ` Mark Brown 2018-04-25 21:04 ` David Collins 2018-04-25 21:04 ` David Collins 2018-05-01 21:02 ` Mark Brown 2018-05-01 21:02 ` Mark Brown
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.1523673467.git.collinsd@codeaurora.org \ --to=collinsd@codeaurora.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.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=mark.rutland@arm.com \ --cc=rnayak@codeaurora.org \ --cc=robh+dt@kernel.org \ --cc=sboyd@kernel.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: linkBe 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.