From: Alim Akhtar <alim.akhtar@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, linux-samsung-soc@vger.kernel.org,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
Thomas Abraham <thomas.ab@samsung.com>
Subject: Re: [PATCH v4 3/4] regulator: s2mps11: add support for S2MPS15 regulators
Date: Thu, 29 Oct 2015 14:04:44 +0530 [thread overview]
Message-ID: <5631DA24.10303@samsung.com> (raw)
In-Reply-To: <5631D533.6070807@samsung.com>
Hi,
On 10/29/2015 01:43 PM, Krzysztof Kozlowski wrote:
> On 29.10.2015 17:08, Lee Jones wrote:
>> On Thu, 29 Oct 2015, Alim Akhtar wrote:
>>
>>> From: Thomas Abraham <thomas.ab@samsung.com>
>>>
>>> The S2MPS15 PMIC is similar in functionality to S2MPS11/14 PMIC. It contains
>>> 27 LDO and 10 Buck regulators and allows programming these regulators via a
>>> I2C interface. This patch adds initial support for LDO/Buck regulators of
>>> S2MPS15 PMIC.
>>>
>>> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
>>> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>> ---
>>> drivers/regulator/Kconfig | 4 +-
>>> drivers/regulator/s2mps11.c | 135 ++++++++++++++++++++++++++++++++++++++++++-
>>> 2 files changed, 136 insertions(+), 3 deletions(-)
>>
>> [...]
>>
>>> @@ -1070,6 +1202,7 @@ static const struct platform_device_id s2mps11_pmic_id[] = {
>>> { "s2mps11-pmic", S2MPS11X},
>>> { "s2mps13-pmic", S2MPS13X},
>>> { "s2mps14-pmic", S2MPS14X},
>>> + { "s2mps15-regulator", S2MPS15X},
>>> { "s2mpu02-pmic", S2MPU02},
>>> { },
>>> };
>>
>> Are you going to s/pmic/regulator/ for the existing devices too?
>
> Yeah, I expected that as well... but of course it is orthogonal to this
> patchset.
>
Agree with Krzysztof here. Noted, will send a separate patch to rename
other S2MPxxx-pmic to *-regulator.
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2015-10-29 8:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 4:58 [PATCH v4 0/4] mfd: sec: add S2MPS15 PMIC support Alim Akhtar
2015-10-29 4:58 ` [PATCH v4 1/4] dt-bindings: mfd: s2mps11: add documentation for s2mps15 PMIC Alim Akhtar
2015-10-29 5:57 ` Krzysztof Kozlowski
2015-10-29 7:48 ` Alim Akhtar
2015-10-29 4:58 ` [PATCH v4 2/4] mfd: sec: Add support for S2MPS15 PMIC Alim Akhtar
2015-10-29 8:06 ` Lee Jones
2015-10-29 8:32 ` Alim Akhtar
2015-10-29 4:58 ` [PATCH v4 3/4] regulator: s2mps11: add support for S2MPS15 regulators Alim Akhtar
2015-10-29 8:08 ` Lee Jones
2015-10-29 8:13 ` Krzysztof Kozlowski
2015-10-29 8:34 ` Alim Akhtar [this message]
2015-10-29 4:58 ` [PATCH v4 4/4] drivers/rtc/rtc-s5m.c: add support for S2MPS15 RTC Alim Akhtar
2015-10-29 5:07 ` Krzysztof Kozlowski
2015-10-29 5:34 ` Alim Akhtar
2015-10-29 5:54 ` Krzysztof Kozlowski
2015-10-29 7:47 ` Alim Akhtar
2015-10-29 11:03 ` Krzysztof Kozlowski
2015-10-29 11:20 ` Alim Akhtar
2015-10-29 11:35 ` [rtc-linux] " Krzysztof Kozlowski
2015-10-29 16:13 ` Alim Akhtar
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=5631DA24.10303@samsung.com \
--to=alim.akhtar@samsung.com \
--cc=broonie@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=thomas.ab@samsung.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