staging: mei: removing dependency between WD and AMTHI init function.
authorOren Weil <oren.jer.weil@intel.com>
Wed, 7 Sep 2011 06:03:07 +0000 (09:03 +0300)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 9 Sep 2011 20:28:20 +0000 (13:28 -0700)
commit617aa39639943626fa262757d176be413c54571b
tree883a42d111db684ffd1123df9688ab7b0bc0e160
parentf6c39d4f2d350df049a844b658eb6b08c5833e51
staging: mei: removing dependency between WD and AMTHI init function.

AMTHI need to be initialized after WD Client was initialized, moving the AMTHI outside
of the WD initialization function.
in order to remove the coupling between the initialization of those clients.

AMTHI is getting initialized (getting connected to the FW feature/client) in two ways:
 1) if mei driver fails to send connect message to watchdog client (WD initialization), then
    immediately the AMTHI client getting initialized right after the watchdog initialization function.
 2) if Watchdog client success to send connect message to watchdog client, then only after
    the driver is getting the connect response message the AMTHI client is getting initialized

Signed-off-by: Oren Weil <oren.jer.weil@intel.com>
Acked-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/staging/mei/init.c
drivers/staging/mei/interface.h
drivers/staging/mei/wd.c