linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] Input: arizona-haptic: Correct disable of haptics device
Date: Wed, 2 Dec 2015 16:16:57 -0800	[thread overview]
Message-ID: <20151203001657.GA37628@dtor-ws> (raw)
In-Reply-To: <1448906540-15356-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Mon, Nov 30, 2015 at 06:02:20PM +0000, Charles Keepax wrote:
> A small copy and paste error was preventing the haptics device being
> disabled. This patch corrects the value written on disable.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>

Applied, thank you.

> ---
>  drivers/input/misc/arizona-haptics.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/input/misc/arizona-haptics.c b/drivers/input/misc/arizona-haptics.c
> index 4bf6785..d5994a7 100644
> --- a/drivers/input/misc/arizona-haptics.c
> +++ b/drivers/input/misc/arizona-haptics.c
> @@ -97,8 +97,7 @@ static void arizona_haptics_work(struct work_struct *work)
>  
>  		ret = regmap_update_bits(arizona->regmap,
>  					 ARIZONA_HAPTICS_CONTROL_1,
> -					 ARIZONA_HAP_CTRL_MASK,
> -					 1 << ARIZONA_HAP_CTRL_SHIFT);
> +					 ARIZONA_HAP_CTRL_MASK, 0);
>  		if (ret != 0) {
>  			dev_err(arizona->dev, "Failed to stop haptics: %d\n",
>  				ret);
> -- 
> 2.1.4
> 

-- 
Dmitry

      reply	other threads:[~2015-12-03  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 18:02 [PATCH] Input: arizona-haptic: Correct disable of haptics device Charles Keepax
2015-12-03  0:16 ` Dmitry Torokhov [this message]

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=20151203001657.GA37628@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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).