RE: [PATCH v2 5/5] mmc: dw_mmc: Set timeout to max upon resume

2013-07-10 Thread Seungwon Jeon
On Wed, July 10, 2013, Doug Anderson wrote: > The TMOUT register is initted to 0x at probe time but isn't > initted after suspend/resume. Add an init of this value. > > No problems were observed without this (it will also get initted in > __dw_mci_start_request if there is data to send),

RE: [PATCH v2 5/5] mmc: dw_mmc: Set timeout to max upon resume

2013-07-10 Thread Seungwon Jeon
On Wed, July 10, 2013, Doug Anderson wrote: The TMOUT register is initted to 0x at probe time but isn't initted after suspend/resume. Add an init of this value. No problems were observed without this (it will also get initted in __dw_mci_start_request if there is data to send), but

[PATCH v2 5/5] mmc: dw_mmc: Set timeout to max upon resume

2013-07-09 Thread Doug Anderson
The TMOUT register is initted to 0x at probe time but isn't initted after suspend/resume. Add an init of this value. No problems were observed without this (it will also get initted in __dw_mci_start_request if there is data to send), but it makes the register dump before and after

[PATCH v2 5/5] mmc: dw_mmc: Set timeout to max upon resume

2013-07-09 Thread Doug Anderson
The TMOUT register is initted to 0x at probe time but isn't initted after suspend/resume. Add an init of this value. No problems were observed without this (it will also get initted in __dw_mci_start_request if there is data to send), but it makes the register dump before and after