From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Linus Walleij <linus.walleij@stericsson.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] AB3100 regulator support v2
Date: Tue, 1 Sep 2009 23:10:58 +0100 [thread overview]
Message-ID: <20090901221057.GA20242@sirena.org.uk> (raw)
In-Reply-To: <63386a3d0909011505oed88151i95df1e97cf131c36@mail.gmail.com>
On Wed, Sep 02, 2009 at 12:05:10AM +0200, Linus Walleij wrote:
> But generally speaking the AB3100 can be used on top of any
> i2c adapter and a bunch of them actually use
> wait_for_completion_interruptible_timeout();
> and wait_event_interruptible_timeout(); for example.
There was some discussion of this on the I2C list and a decision that it
was sensible to move away from doing that since it was being found to
cause more problems than it solved - the FSL driver is the one I
remember actually doing so.
> One of them being i2c/buses/i2c-imx.c actually, Mark does
> this mean you actually have the risk of being kill -9:ed in the
> middle of a regulator operation for the WM drivers, for
> example
Yes. Pretty much any embedded I2C driver could cause issues for the
Wolfson drivers - there's a whole bunch of audio CODECs that are very
widely deployed.
> In the general sense perhaps this doesn't happen so much,
Yes, it's fairly rare which is the main reason it's not being chased
after particularly actively.
next prev parent reply other threads:[~2009-09-01 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 21:29 [PATCH 1/2] AB3100 regulator support v2 Linus Walleij
2009-08-31 12:44 ` Mark Brown
2009-08-31 14:16 ` Linus Walleij
2009-09-01 10:23 ` Mark Brown
2009-09-01 13:51 ` Russell King - ARM Linux
2009-09-01 22:05 ` Linus Walleij
2009-09-01 22:10 ` Linus Walleij
2009-09-01 22:10 ` Mark Brown [this message]
2009-09-01 13:47 ` Russell King - ARM Linux
2009-09-01 21:55 ` Linus Walleij
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=20090901221057.GA20242@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.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