From: Jaewon Kim <jaewon02.kim@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Hyunhee Kim <hyunhee.kim@samsung.com>
Subject: Re: [PATCH 1/2] Input: add regulator haptic driver
Date: Mon, 01 Dec 2014 10:30:07 +0900 [thread overview]
Message-ID: <547BC49F.8040402@samsung.com> (raw)
In-Reply-To: <20141128125051.GA3643@sirena.org.uk>
Hi Mark,
2014년 11월 28일 21:50에 Mark Brown 이(가) 쓴 글:
> On Thu, Nov 20, 2014 at 10:31:39PM +0900, Jaewon Kim wrote:
>
>> + haptic->regulator = devm_regulator_get(&pdev->dev, "haptic");
>> + if (IS_ERR(haptic->regulator)) {
>> + dev_err(&pdev->dev, "failed to get regulator\n");
>> + return PTR_ERR(haptic->regulator);
>> + }
> This needs to be _get_exclusive() - the driver will be broken if
> something else shares the regualtor since it relies on both enabling and
> disabling the regulator and on setting the voltage for effects. It's
> not like a power supply where leaving the device powered when it could
> be off is going to have no effect, if the power is left on then the
> haptic motor will continue to operate.
Thanks to review my patch.
Haptic regulator has to only be used in this driver.
So, it is right to change like your advice.
I will fix next version.
Thanks
Jaewon Kim.
next prev parent reply other threads:[~2014-12-01 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 13:31 [PATCH 0/2] Add regulator-haptic driver Jaewon Kim
2014-11-20 13:31 ` [PATCH 1/2] Input: add regulator haptic driver Jaewon Kim
2014-11-20 14:33 ` Pankaj Dubey
2014-11-20 15:09 ` Dan Murphy
2014-11-21 1:49 ` Jaewon Kim
2014-11-21 1:22 ` Jaewon Kim
[not found] ` <20141128125051.GA3643@sirena.org.uk>
2014-12-01 1:30 ` Jaewon Kim [this message]
2014-11-20 13:31 ` [PATCH 2/2] ARM: dts: Add regulator-haptic device node for exynos3250-rinato Jaewon Kim
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=547BC49F.8040402@samsung.com \
--to=jaewon02.kim@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hyunhee.kim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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: 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
Powered by JetHome