Hi Tony > Up until now, we polled the rfkill status for every incoming FUJ02E3 ACPI event. > It turns out that the firmware has a bitmask which indicates what rfkill-related > state it can report. > The rfkill_supported bitmask is now used to avoid polling for rfkill at all in > the notification handler if there is no support. Also, it is used in the platform > device callbacks. As before we register all callbacks and report "unknown" if the > firmware does not give us status updates for that particular bit. > > This was fed through checkpatch.pl and tested on the S6420 platform. > Jonathan, your platform is of particular importance as you are the only tester > on a platform with no S000 function in the DSDT. Please confirm you still get a > unknown status in the platform files. With debugging on full, you should see the > 0x1000 0x4 0x0 0x0 call disappear from your trace entirely. I'll check this as soon as I can. I'm at Linux.conf.au this week though so I'm not sure I'll be able to. We'll see. What kernel is the patch against? Regards jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
