The DBM, in some versions, indicates via hardware interrupt
that a packet has been received on the DL (IN) path and that
the software should take the DWC controller out of L1 into L0.
Change-Id: I13180cffbe7040760842ebd345749d2a469adee2
Signed-off-by: Dov Levenglick <dovl@codeaurora.org>
Making the proper distinction between ep_reset function
calls that are made from within the dbm driver (in which
case the dbm ep number is provided) vs. when the call
is made from the dwc3 driver (in which case the usb ep
number is provided).
Change-Id: I0950a324da44c8abe780ad0a7b1095143a294a0b
Signed-off-by: Dov Levenglick <dovl@codeaurora.org>
Signed-off-by: Bar Weiner <bweiner@codeaurora.org>
Some dbm implementations require that after going
through a Low Power Mode (lpm) suspend flow - the
dbm ep be reset prior to resuming.
This patch implements and exposes this functionality.
Change-Id: I348a2c61ca159ef8b5a14fac3465d777bd4217b4
Signed-off-by: Dov Levenglick <dovl@codeaurora.org>
Refactoring of DBM code to allow easy support for future
DBM versions.
All DBM specific operation are now defined in dbm.h,
and implemented in a dbm specific version module.
Note that only a single instance of DBM is currently
supported.
Change-Id: I751300240951a84a42358c3b8b5222e73c537653
Signed-off-by: Bar Weiner <bweiner@codeaurora.org>
Dov Levenglick