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 <viresh.kumar@linaro.org>
Reviewed-by: Johan Hovold <johan@hovoldconsulting.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>

diff --git a/drivers/staging/greybus/firmware.c b/drivers/staging/greybus/firmware.c
index 884b7e2ad0a8740e5df7ab9a6fe8004abd13c8e2..e04ed6bffcf56308219cd52f313477257965d67c 100644 (file)
--- 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);