public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	Rabin Vincent <rabin.vincent@stericsson.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/4] mfd/ab8500: don't use mutex_lock_interruptible
Date: Fri, 16 Mar 2012 19:46:09 +0100	[thread overview]
Message-ID: <20120316184609.GN20524@sortiz-mobl> (raw)
In-Reply-To: <1331211706-9763-1-git-send-email-linus.walleij@stericsson.com>

Hi Linus,

On Thu, Mar 08, 2012 at 02:01:46PM +0100, Linus Walleij wrote:
> From: Rabin Vincent <rabin.vincent@stericsson.com>
> 
> This disadvantage of having it interruptible is that it would
> appear to work OK in most situations, but in the rare case
> that this call does fail, it can lead to misconfiguration
> of the AB, such as a regulator not being turned off and
> leading to a platform power consumption increase.
> 
> There's no real benefit to having this interruptible.
> 
> Make it a plain mutex_lock. The non-interruptability matches
> other low-level I/O functions such as SPI and I2C.
> 
> Signed-off-by: Rabin Vincent <rabin.vincent@stericsson.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>  drivers/mfd/ab8500-core.c |   12 +++---------
>  1 files changed, 3 insertions(+), 9 deletions(-)
All 4 patches applied, thanks.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2012-03-16 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 13:01 [PATCH 1/4] mfd/ab8500: don't use mutex_lock_interruptible Linus Walleij
2012-03-15 18:25 ` Linus Walleij
2012-03-16 18:46 ` Samuel Ortiz [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=20120316184609.GN20524@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rabin.vincent@stericsson.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