From: Richard Purdie <rpurdie@rpsys.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Pavel Machek <pavel@suse.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: introduce delayed-leds.h to reduce code duplication
Date: Wed, 21 Jan 2009 16:54:16 +0000 [thread overview]
Message-ID: <1232556856.5343.48.camel@dax.rpnet.com> (raw)
In-Reply-To: <20090120120400.GA15144@khazad-dum.debian.net>
On Tue, 2009-01-20 at 10:04 -0200, Henrique de Moraes Holschuh wrote:
> I don't like the loss of functionality of the private workqueue. I kicked
> the thinkpad led handling to a private workqueue in order to never tie up
> the system-wide one with crap spinning around in the ACPI layer, etc. In
> fact, all thinkpad-acpi deferred work is in the private workqueue for this
> reason.
>
> This is easy enough to fix, you just need to provide both versions of the
> interface (standard workqueue, and private workqueue). OTOH, if nowadays
> the system-wide workqueue runs tasks in parallel and there is no risk of a
> task blocking others from completely unrelated subsystems, I can ditch the
> private workqueue.
>
> Also, if it is going to be generic, I'd suggest the usual "void *data"
> opaque type to carry information for the driver, instead of a "led number".
>
> I didn't see any comments from Richard, but your comment about a flag seems
> to imply there was a private one? IMHO enhancing the led class would be the
> best way to go about it, although deferred leds are simple enough that it
> doesn't matter much.
I think the best approach is to get this header working and then see how
many people can really share it. If its common enough we can add to the
core but lets see if its a useful abstraction first?
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next prev parent reply other threads:[~2009-01-21 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 22:43 Pavel Machek
2009-01-12 10:05 ` Henrique de Moraes Holschuh
2009-01-19 15:02 ` Pavel Machek
2009-01-20 12:04 ` Henrique de Moraes Holschuh
2009-01-21 16:54 ` Richard Purdie [this message]
2009-03-08 8:29 ` Pavel Machek
2009-03-11 1:39 ` Henrique de Moraes Holschuh
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=1232556856.5343.48.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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