Hi, On 3/18/23 18:55, Andrew Kallmeyer wrote: > On Sat, Mar 18, 2023 at 10:50 AM Andrew Kallmeyer <kallmeyeras@xxxxxxxxx> wrote: >> >> Hi Armin, would it work to add the second GUID to the existing >> wmi_driver wmi_device_id array? Then I could save the wmi_device in >> the driver data on probe. Later when I get the notification on the >> other GUID I would just call wmidev_evaluate_method on the saved >> pointer out of the private data. > > Now that I have understood the multiple probe calls and went back to > read this, I realized that I would not be able to access the private > data of the notify device when handling the probe call for the query > device. Maybe you will have a good idea to solve this problem. Right in this model you would need a global shared notifier_head variable on which the event GUID driver would do a notify and on which the other GUId driver would then register a notifier to get called when the event GUID driver does the notify. So as said this is somewhat involved and I'm fine with the simpler current solution. Regards, Hans
