From 336dfeaba1f6dd3b07571e0010707f716a1c6ee8 Mon Sep 17 00:00:00 2001 From: Viresh Kumar Date: Wed, 23 Sep 2015 16:48:13 -0700 Subject: greybus: firmware: Don't send control-disconnected event for firmware protocol After downloading the firmware for the next boot stage, module's firmware (for current boot stage) jumps into it and the new firmware and sends hotplug request to SVC. On hotplug request from the SVC, the AP first removes the existing interface. At this time, there is no point sending disconnected event for the firmware protocol, for the firmware used in previous stage, as the new firmware wouldn't be aware about it. Set flags for firmware protocol to skip control-disconnected operations. Signed-off-by: Viresh Kumar Reviewed-by: Johan Hovold Signed-off-by: Greg Kroah-Hartman --- drivers/staging/greybus/firmware.c | 1 + 1 file changed, 1 insertion(+) (limited to 'drivers/staging/greybus/firmware.c') diff --git a/drivers/staging/greybus/firmware.c b/drivers/staging/greybus/firmware.c index 884b7e2ad0a8..e04ed6bffcf5 100644 --- a/drivers/staging/greybus/firmware.c +++ b/drivers/staging/greybus/firmware.c @@ -210,5 +210,6 @@ static struct gb_protocol firmware_protocol = { .connection_init = gb_firmware_connection_init, .connection_exit = gb_firmware_connection_exit, .request_recv = gb_firmware_request_recv, + .flags = GB_PROTOCOL_SKIP_CONTROL_DISCONNECTED, }; gb_builtin_protocol_driver(firmware_protocol); -- cgit v1.2.3