On 31/12/15 03:09, Henry Chen wrote:
Hi Matthias,
On Wed, 2015-12-30 at 19:02 +0100, Matthias Brugger wrote:
On 22/12/15 08:51, Henry Chen wrote:
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing
On 31/12/15 03:09, Henry Chen wrote:
Hi Matthias,
On Wed, 2015-12-30 at 19:02 +0100, Matthias Brugger wrote:
On 22/12/15 08:51, Henry Chen wrote:
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing
Hi Matthias,
On Wed, 2015-12-30 at 19:02 +0100, Matthias Brugger wrote:
>
> On 22/12/15 08:51, Henry Chen wrote:
> > Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
> > because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
> > just return error
On 22/12/15 08:51, Henry Chen wrote:
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
just return error when issue happened, so the state machine will stay on
FSM_VLDCLR state when data send
On 22/12/15 08:51, Henry Chen wrote:
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
just return error when issue happened, so the state machine will stay on
FSM_VLDCLR state when data send
Hi Matthias,
On Wed, 2015-12-30 at 19:02 +0100, Matthias Brugger wrote:
>
> On 22/12/15 08:51, Henry Chen wrote:
> > Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
> > because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
> > just return error
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
just return error when issue happened, so the state machine will stay on
FSM_VLDCLR state when data send back later by PMIC and timeout again in
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
just return error when issue happened, so the state machine will stay on
FSM_VLDCLR state when data send back later by PMIC and timeout again in
8 matches
Mail list logo