{"push_id":1434850409,"size":1,"distinct_size":1,"ref":"refs/heads/cm-14.1_caf","head":"86c8e95a4d8411e84d3b92b6afa496c3ec32b601","before":"ece9ede109cbc5ce079224671514953a221e584a","commits":[{"sha":"86c8e95a4d8411e84d3b92b6afa496c3ec32b601","author":{"name":"Jack Pham","email":"f646de8ac2008412216aeba4d048e5819cf51aef@codeaurora.org"},"message":"usb: dwc3-msm: Handle erratic event with full POR sequence\n\nThe current handling of erratic errors that occur in peripheral\nmode does so by scheduling a block reset. Since this occurs\nasynchronously, additional changes needed to be made to ensure\nthe device controller would not generate spurious events or\ntry to access any registers while the reset was in progress\nand the clocks were off. Even after that, the controller would\nstill not be functional until a cable reconnect since the block\nreset routine did not do anything to re-establish the peripheral\nsession.\n\nInstead, improve the erratic error handling to simulate a\ncable disconnection-reconnection sequence. The forced disconnect\nshould solve issues related to post-error events as well as\nprevent any function drivers from continuing to issue endpoint\ncommands. This is followed with the controller entering low\npower mode. If the cable is still physically connected, then\ninvoke a reconnection which does the full reset and power-on\ninitialization sequence that is more complete than the current\nblock reset. The USB session would then get re-enumerated.\n\nChange-Id: I45ccb30ff12064e5410d45c423a404d97b299022\nSigned-off-by: Jack Pham <jackp@codeaurora.org>\nSigned-off-by: Azhar Shaikh <azhars@codeaurora.org>\nSigned-off-by: Felipe Leon <fglfgl27@gmail.com>","distinct":true,"url":"https://api.github.com/repos/bhb27/BHB27Kernel/commits/86c8e95a4d8411e84d3b92b6afa496c3ec32b601"}]}
{"actor":{"display_login":"bhb27"}}