Some WMI implementations do notifies on WMI objects without a _WED method
allow WMI drivers to indicate that _WED should not be called for notifies
on the WMI objects the driver is bound to.
Instead the driver's notify callback will simply be called with a NULL
data argument.
Reported-by: Yauhen Kharuzhy <jekhor@gmail.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20211128190031.405620-3-hdegoede@redhat.com
 
                struct acpi_buffer evdata = { ACPI_ALLOCATE_BUFFER, NULL };
                acpi_status status;
 
-               status = get_event_data(wblock, &evdata);
-               if (ACPI_FAILURE(status)) {
-                       dev_warn(&wblock->dev.dev, "failed to get event data\n");
-                       return;
+               if (!driver->no_notify_data) {
+                       status = get_event_data(wblock, &evdata);
+                       if (ACPI_FAILURE(status)) {
+                               dev_warn(&wblock->dev.dev, "failed to get event data\n");
+                               return;
+                       }
                }
 
                if (driver->notify)
 
 struct wmi_driver {
        struct device_driver driver;
        const struct wmi_device_id *id_table;
+       bool no_notify_data;
 
        int (*probe)(struct wmi_device *wdev, const void *context);
        void (*remove)(struct wmi_device *wdev);