Re: iwlwifi - rfkill only works if the interface is up

[Helmut Schaa <helmut.schaa@googlemail.com>]

Am Montag, 1. Dezember 2008 schrieb Marcel Holtmann:
> Hi Tomas,
> 
> > > Nevertheless, I'm wondering if the current behaviour (even with the patch above)
> > > makes much sense. I mean, the user space cannot rely on the rfkill state
> > > unless an appropriate interface is up. As the device is able to report the
> > > killswitch state without firmware being loaded the following approach could
> > > be feasible:
> > > - iwl_pci_probe enables the device and enables the interrupts
> > > - iwl_mac_start just loads the firmware
> > > - iwl_mac_stop just releases the firmware but leaves the interrupts enabled
> > 
> > In 3495  rfkill interrupt is not available and rfkill state is
> > delivered only when firmware is loaded, therefore this is not
> > possible to bring device down and also expect rfill switch event.
> > There were few threads about this subject.
> > In 4965 and 5000 this will work
> 
> do we unregister the rfkill switch when bringing the adapter down.

No.

> If not, then we might should do that. I don't see a point in exposing a
> rfkill switch if we can't do anything with it.

Either that, or make the rfkill usable even when the interface is down.

Helmut