On Thursday, November 15, 2012, Seungwon Jeon
> I checked this commit.
> v3 doesn't work in dw_mmc host driver.
> It makes some driver warning while v1 is fine.
> I'm finding the reason. And could you check minor one below?
Please let me correct my test. There is something applied wrong.
Anyway I
I checked this commit.
v3 doesn't work in dw_mmc host driver.
It makes some driver warning while v1 is fine.
I'm finding the reason. And could you check minor one below?
On Tuesday, November 13, 2012, Seungwon Jeon
> Hi Konstantin,
>
> I'm looking into this patch.
> Idea looks good as a whole.
>
Hi Konstantin,
I'm looking into this patch.
Idea looks good as a whole.
On Tuesday, November 13, 2012, Konstantin Dorfman
wrote:
> When current request is running on the bus and if next request fetched
> by mmcqd is NULL, mmc context (mmcqd thread) gets blocked until the
> current request compl
When current request is running on the bus and if next request fetched
by mmcqd is NULL, mmc context (mmcqd thread) gets blocked until the
current request completes. This means if new request comes in while
the mmcqd thread is blocked, this new request can not be prepared in
parallel to current ong
