From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: shuahkhan@gmail.com, "Kim, Milo" <Milo.Kim@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] leds: add new lp8788 led driver
Date: Tue, 24 Jul 2012 13:55:14 +0100 [thread overview]
Message-ID: <20120724125513.GG12438@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAK5ve-KAufV5h93AcWdVUVZx2E+pfgQ1L0jp5H28wHgBfV2zPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Tue, Jul 24, 2012 at 08:23:00AM +0800, Bryan Wu wrote:
> On Mon, Jul 23, 2012 at 2:19 AM, Mark Brown
> > If the work is flushed then the state that userspace thought was set
> > when the driver is removed will actually be set before the driver is
> > removed. This is fairly minor but might be useful.
> So what's kind of state you mentioned here that is cared by user
> space. I find these 2 functions are quite confused for use right now.
Any state - none of the drivers with sleeping I/O can do anything
directly in their callbacks so they defer everything to work (we really
should have that in the core but it was too annoying to implement last
time I looked).
> Literally, canceling normally will remove pending work item and wait
> for running work item to finish. flushing will wait for both pending
> and running work item to finish.
Right, so if we flush it means we know that any scheduled work actually
ran and implemented whatever change was requested.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-24 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 8:43 [PATCH v2] leds: add new lp8788 led driver Kim, Milo
2012-07-20 15:49 ` Shuah Khan
2012-07-20 18:48 ` Bryan Wu
2012-07-22 18:19 ` Mark Brown
2012-07-24 0:23 ` Bryan Wu
2012-07-24 12:55 ` Mark Brown [this message]
2012-07-25 4:46 ` Bryan Wu
2012-07-25 18:43 ` Mark Brown
2012-07-26 2:51 ` Bryan Wu
2012-08-01 20:35 ` Mark Brown
2012-07-20 16:23 ` devendra.aaru
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=20120724125513.GG12438@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Milo.Kim@ti.com \
--cc=bryan.wu@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkhan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.