lkml.org 
[lkml]   [2008]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2)
Henrique de Moraes Holschuh wrote:
>
> rfkill-input (now) or userspace (someday) will take care of kicking the
> radio to RFKILL_STATE_UNBLOCKED when (1) issues an event that signals that
> radios don't have to remain blocked. Maybe this is why you see the WLAN
> going on when you deactivate the radio kill switch?

It's all done behind the scenes I think (it's an ipw2200 device). There's
no rfkill integration from that driver.

> And rfkill-input will soon be enhanced to let the user configure it to do
> something different if he wants. Your driver doesn't (and shouldn't)
> hardcode policy about it.

Ok, that makes things much easier for me :-) But it means that for now the
user will have to manually kick the device.

>
> Thanks. Please take note that rfkill will, right now, try to BLOCK all
> radios on suspend. That will be changed soon (2.6.28 at the latest), and
> your driver will have to handle blocking radios on suspend directly if it is
> needed for toshibas.

Why is this necessary? Doesn't the radio power down as part of the suspend
process? How would I tell what the hardware is doing?

I'll update the diff when I can.

--phil


\
 
 \ /
  Last update: 2008-08-06 05:37    [W:0.320 / U:0.412 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site