From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, eric.piel@tremplin-utc.net
Subject: Re: hp_accel: do not call ACPI from invalid context
Date: Tue, 13 Jan 2009 23:33:00 +0100 [thread overview]
Message-ID: <20090113223300.GB7770@elf.ucw.cz> (raw)
In-Reply-To: <20090113141116.6faeada9.akpm@linux-foundation.org>
On Tue 2009-01-13 14:11:16, Andrew Morton wrote:
> On Mon, 12 Jan 2009 11:31:55 +0100
> Pavel Machek <pavel@suse.cz> wrote:
>
> >
> > LED on HP notebooks is connected through ACPI. That unfortunately
> > means that it needs to be delayed by using schedule_work() to avoid
> > calling ACPI interpretter in invalid context. This patch fixes that.
> >
> > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > -static void hpled_set(struct led_classdev *led_cdev,
> > - enum led_brightness value)
> > -{
> > - hpled_acpi_write(adev.device->handle, !!value);
> > -}
> > -
> > -static struct led_classdev hpled_led = {
> > - .name = "hp:red:hddprotection",
> > - .default_trigger = "heartbeat",
>
> Current mainline+lis3lv02d-merge-with-leds-hp-disk.patch has "none"
> here, so the patch didn't apply.
Oops, sorry about that. I was hand-editing patches a bit too much :-(.
> > - .brightness_set = hpled_set,
> > +static struct delayed_led_classdev hpled_led = {
> > + .led_classdev = {
> > + .name = "hp::hddprotect",
> > + .default_trigger = "none",
>
> But I assume we wanted "none" here anyway, so that's what I'll do.
Thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-01-13 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 10:31 Pavel Machek
2009-01-13 22:11 ` Andrew Morton
2009-01-13 22:33 ` Pavel Machek [this message]
2009-01-13 22:17 ` Andrew Morton
2009-01-13 22:40 ` Pavel Machek
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=20090113223300.GB7770@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®