From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/6] regulator: qcom-spmi: Add vendor specific configuration
Date: Fri, 12 Jun 2015 16:24:37 -0700 [thread overview]
Message-ID: <557B6A35.70009@codeaurora.org> (raw)
In-Reply-To: <CAL_JsqL6R5jz1Xhgav0a0SeWqcRT200sofP-G_zQLfDVeqwarA@mail.gmail.com>
On 06/11/2015 08:13 PM, Rob Herring wrote:
> On Thu, Jun 11, 2015 at 7:37 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> Add support for over current protection (OCP), pin control
>> selection, soft start and soft start strength, auto-mode, input
>> current limiting, and pull down.
>>
>> Cc: <devicetree@vger.kernel.org>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> ---
>>
>> Changes from v1:
>> * New patch split from original SPMI regulator driver
>>
>> .../bindings/regulator/qcom,spmi-regulator.txt | 62 +++++
>> drivers/regulator/qcom_spmi-regulator.c | 298 ++++++++++++++++++++-
>> 2 files changed, 358 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt b/Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt
>> index 75b4604bad07..ab01a152e930 100644
>> --- a/Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt
>> +++ b/Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt
>> @@ -99,6 +99,68 @@ see regulator.txt - with additional custom properties described below:
>> soft start are active all the time. 0 = Set initial mode to
>> low power mode (LPM).
>>
>> +- qcom,auto-mode-enable:
> Auto regulator modes are fairly common. Can't we have a common property here?
Should we use regulator-init-mode? We could make
spmi_regulator_of_map_mode() turn "2" into REGULATOR_MODE_FAST and then
use that to enable auto mode.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-06-12 23:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 0:37 [PATCH v2 0/6] SPMI regulator driver Stephen Boyd
2015-06-12 0:37 ` [PATCH v2 1/6] regulator: Add QCOM " Stephen Boyd
2015-06-12 12:04 ` Mark Brown
2015-06-12 0:37 ` [PATCH v2 2/6] regulator: Add system_load constraint Stephen Boyd
2015-06-12 12:05 ` Mark Brown
2015-06-12 0:37 ` [PATCH v2 3/6] regulator: Add pull down support Stephen Boyd
2015-06-12 12:09 ` Mark Brown
2015-06-12 0:37 ` [PATCH v2 4/6] regulator: Add soft start support Stephen Boyd
2015-06-12 12:16 ` Mark Brown
2015-06-12 0:37 ` [PATCH v2 5/6] regulator: Add input current limit support Stephen Boyd
2015-06-12 12:18 ` Mark Brown
2015-06-12 0:37 ` [PATCH v2 6/6] regulator: qcom-spmi: Add vendor specific configuration Stephen Boyd
2015-06-12 3:13 ` Rob Herring
2015-06-12 22:10 ` Stephen Boyd
2015-06-12 23:24 ` Stephen Boyd [this message]
2015-06-14 4:12 ` Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 0:31 [PATCH v2 0/6] SPMI regulator driver Stephen Boyd
2015-06-12 0:31 ` [PATCH v2 6/6] regulator: qcom-spmi: Add vendor specific configuration Stephen Boyd
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=557B6A35.70009@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).