We normally get EXT hotplug events or poll for MP hotplugging so we
don't need to force extension port initialization during device setup.
But for gen20 devices, we disable MP polling because MP is always
present. However, this prevents MP initialization during device setup
and users need to plug another extension to trigger EXT/MP detection.

Therefore, we now trigger EXT/MP detection during device setup
automatically. This also avoids slightly delayed extension detection
and provides sysfs child-devices prior to the "changed"-uevent during
device setup.

Signed-off-by: David Herrmann <[email protected]>
---
Hi Jiri

Three trivial fixes for the pending series. If there are any issues, please
let me know. And thanks for reviewing them!

Cheers
David

 drivers/hid/hid-wiimote-core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hid/hid-wiimote-core.c b/drivers/hid/hid-wiimote-core.c
index 89118e9..f54595c 100644
--- a/drivers/hid/hid-wiimote-core.c
+++ b/drivers/hid/hid-wiimote-core.c
@@ -1247,7 +1247,7 @@ static void wiimote_init_worker(struct work_struct *work)
                changed = true;
        }
 
-       if (!wiimote_init_check(wdata))
+       if (changed || !wiimote_init_check(wdata))
                wiimote_init_hotplug(wdata);
 
        if (changed)
-- 
1.8.2.3

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to