From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
ak@linux.intel.com, Len Brown <lenb@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RESEND] [PATCH -next 2/2] acpi,rfkill,backlight: comapl-laptop update - use rfkill switch subsystem
Date: Thu, 10 Jul 2008 10:29:34 -0300 [thread overview]
Message-ID: <20080710132934.GB1346@khazad-dum.debian.net> (raw)
In-Reply-To: <200807101517.38109.IvDoorn@gmail.com>
On Thu, 10 Jul 2008, Ivo van Doorn wrote:
> > Do you want me to mark rfkill_force_state() as mandatory in the docs? It
> > *IS* the preferred way to deal with firmware/hardware-initiated state
> > changes, after all.
>
> Please do. Thanks.
>
> > The rfkill subsystem will limp along without it, even when there are
> > hardware rfkill lines... but no OSD function will work, as the system will
> > pick up the change only when someone reads or writes to the state
> > attribute...
>
> That reason alone is good enough for me to mark it mandatory for any drivers
> which features the rfkill key. :)
Input drivers don't need it at all, so it is not the drivers with rfkill
keys (input devices) that need it. Rather, the drivers of wireless devices
with hardware rfkill lines are the ones who "need" it.
Yeah, I am definately adding it to the docs. Did some locking fixes and
other dangerous crap too (in the sense that it can easily force me to down a
brown paperbag!), that needs to go to the list for RFC. Will send what I
have done already after some light testing.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-07-10 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 21:10 Cezary Jackiewicz
2008-07-09 21:33 ` Ivo van Doorn
2008-07-09 21:44 ` Cezary Jackiewicz
2008-07-09 21:57 ` Ivo van Doorn
2008-07-10 1:12 ` Henrique de Moraes Holschuh
2008-07-10 13:17 ` Ivo van Doorn
2008-07-10 13:29 ` Henrique de Moraes Holschuh [this message]
2008-07-10 1:07 ` 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=20080710132934.GB1346@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cezary.jackiewicz@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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®