Re: mmc_test Correct xfer_size at write

On 06/28/2011 05:50 PM, Pierre Ossman wrote: > On Tue, 28 Jun 2011 11:37:25 +0100 > James Hogan wrote: > >> Hi, >> >> I'm trying to figure out why the broken write transfer tests in mmc_test >> require the result to be -ETIMEDOUT, so that I can make dw_mmc pass >> these tests. Perhaps somebody co

Re: mmc_test Correct xfer_size at write

On Tue, 28 Jun 2011 11:37:25 +0100 James Hogan wrote: > Hi, > > I'm trying to figure out why the broken write transfer tests in mmc_test > require the result to be -ETIMEDOUT, so that I can make dw_mmc pass > these tests. Perhaps somebody could explain. > > I can understand for reads, that the

mmc_test Correct xfer_size at write

Hi, I'm trying to figure out why the broken write transfer tests in mmc_test require the result to be -ETIMEDOUT, so that I can make dw_mmc pass these tests. Perhaps somebody could explain. I can understand for reads, that the controller is waiting for the start bit on the data lines and so it ca

mmc_test Correct xfer_size at write

Hi, I'm trying to figure out why the broken write transfer tests in mmc_test require the result to be -ETIMEDOUT, so that I can make dw_mmc pass these tests. Perhaps somebody could explain. I can understand for reads, that the controller is waiting for the start bit on the data lines and so it ca