Re: [PATCH v2 2/3] cros_ec: Fix deadlock when EC is not responsive at probe

Hi Thierry, On Tue, Feb 14, 2017 at 08:58:01PM +0100, Thierry Escande wrote: > From: Gwendal Grignou > > When the EC is not responsive at probe, we try to get basic information > (protocol to use) later on through cros_xfer_cmd() call. > This patch makes sure there is no

Re: [PATCH v2 2/3] cros_ec: Fix deadlock when EC is not responsive at probe

Hi Thierry, On Tue, Feb 14, 2017 at 08:58:01PM +0100, Thierry Escande wrote: > From: Gwendal Grignou > > When the EC is not responsive at probe, we try to get basic information > (protocol to use) later on through cros_xfer_cmd() call. > This patch makes sure there is no deadlock when

[PATCH v2 2/3] cros_ec: Fix deadlock when EC is not responsive at probe

From: Gwendal Grignou When the EC is not responsive at probe, we try to get basic information (protocol to use) later on through cros_xfer_cmd() call. This patch makes sure there is no deadlock when re-probing the EC by replacing call to cros_xfer_cmd() with send_command()

[PATCH v2 2/3] cros_ec: Fix deadlock when EC is not responsive at probe

From: Gwendal Grignou When the EC is not responsive at probe, we try to get basic information (protocol to use) later on through cros_xfer_cmd() call. This patch makes sure there is no deadlock when re-probing the EC by replacing call to cros_xfer_cmd() with send_command() in the function