On Thursday 22 October 2015 15:43:46 Gabriele Mazzotta wrote:
> It's the F2 key. Depending on the value passed to the RBTN, it acts as
> hw slider or sw toggle.
Ok, we have differences in terminology and everybody understood this
problem differently.
To correct this situation, first define about what we are talking about:
* HW slider: It is hardware slider switch which as two positions ON and
OFF. Position exactly defines hardware state of wireless
radio devices. Not possible (or should not) to remap.
* SW hotkey toggle button: It is button or key, act in same way as any
other key on keyboard, controlled by SW
(if all drivers are installed, etc).
Next I think that this hypothesis is truth:
* Every machine on which is binded ACPI dell-rbtn.ko driver has either
HW slider or SW toggle. Not both!
Correct?
Then follows my expected behaviour for HW slider:
* State of HW slider position is exported by kernel as rfkill device.
* In any case HW slider position (ON/OFF) match hard rfkill state device
(rfkill device state is correct also after resume, wake from hibernate).
* Immediately after user change position of HW slider, rfkill device
reflect it.
And then expected behaviour for SW toggle button:
* Every time when user press it, kernel just send input event "wireless
key pressed" to userspace.
* Kernel does not send event "wireless key pressed" when user did not
pressed it (e.g. after resuming from suspend, waking from hibernate).
* Kernel should provide rfkill devices to "soft" block appropriate
wireless cards.
* Make sure that BIOS/firmware in any case does not change radio rfkill
state of any wireless card and wireless cards stay in same state as
before (no enable/disable or changing hard/soft rfkill state).
If last sentence is not truth, then kernel must not send "wireless key
pressed" event to userspace and act like "no key was pressed".
Make this sense? Or are there any objections about this behaviour?
--
Pali Rohár
pali.rohar@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
