linux.git/drivers/mmc/card, branch master

mmc: block: Move files to core

2016-12-12T15:30:05+00:00

Once upon a time it made sense to keep the mmc block device driver and its
related code, in its own directory called card. Over time, more an more
functions/structures have become shared through generic mmc header files,
between the core and the card directory. In other words, the relationship
between them has become closer.

By sharing functions/structures via generic header files, it becomes easy
for outside users to abuse them. In a way to avoid that from happen, let's
move the files from card directory into the core directory, as it enables
us to move definitions of functions/structures into mmc core specific
header files.

Note, this is only the first step in providing a cleaner mmc interface for
outside users. Following changes will do the actual cleanup, as that is not
part of this change.

Signed-off-by: Ulf Hansson 
Reviewed-by: Linus Walleij

mmc: mmc_test: remove BUG_ONs and deploy error handling

2016-12-05T09:31:13+00:00

It is unnecessary to panic the kernel when testing mmc. Instead,
cast a warning for folkz to debug and return the error code to
the caller to indicate the failure of this test should be enough.

Signed-off-by: Shawn Lin 
Signed-off-by: Ulf Hansson

mmc: queue: remove BUG_ON for bounce_sg

2016-12-05T09:31:13+00:00

bounce_sg for mqrq_cur and mqrq_pre are proper
allocated when initializing the queue and will not
be freed before explicitly cleaning the queue. So from
the code itself it should be quite confident to remove
this check. If that BUG_ON take effects, it is mostly
likely the memory is randomly oopsing.

Signed-off-by: Shawn Lin 
Signed-off-by: Ulf Hansson

mmc: sdio_uart: remove meaningless BUG_ON

2016-12-05T09:31:12+00:00

The code seems quite simple to maintain the sdio_uart_table,
and the insert/remove port from the table are symmetric. If
the BUG_ON occurs, which means serial_core modify the index
or mess up the port sequence anyway.

Signed-off-by: Shawn Lin 
Signed-off-by: Ulf Hansson

mmc: queue: Introduce queue depth and use it to allocate and free

2016-12-05T09:31:07+00:00

Add a mmc_queue member to record the size of the queue, which currently
supports 2 requests on-the-go at a time. Instead of allocating resources
for 2 slots in the queue, allow for an arbitrary number.

Signed-off-by: Adrian Hunter 
Signed-off-by: Ulf Hansson

mmc: queue: Factor out mmc_queue_reqs_free_bufs()

2016-12-05T09:31:06+00:00

In preparation for supporting a queue of requests, factor out
mmc_queue_reqs_free_bufs().

Signed-off-by: Adrian Hunter 
Reviewed-by: Linus Walleij 
Reviewed-by: Harjani Ritesh 
Signed-off-by: Ulf Hansson

mmc: queue: Factor out mmc_queue_alloc_sgs()

2016-12-05T09:31:05+00:00

In preparation for supporting a queue of requests, factor out
mmc_queue_alloc_sgs().

Signed-off-by: Adrian Hunter 
Reviewed-by: Linus Walleij 
Reviewed-by: Harjani Ritesh 
Signed-off-by: Ulf Hansson

mmc: queue: Factor out mmc_queue_alloc_bounce_sgs()

2016-12-05T09:31:05+00:00

In preparation for supporting a queue of requests, factor out
mmc_queue_alloc_bounce_sgs().

Signed-off-by: Adrian Hunter 
Reviewed-by: Linus Walleij 
Reviewed-by: Harjani Ritesh 
[Ulf: Fixed compiler warning]
Signed-off-by: Ulf Hansson

mmc: queue: Factor out mmc_queue_alloc_bounce_bufs()

2016-12-05T09:31:04+00:00

In preparation for supporting a queue of requests, factor out
mmc_queue_alloc_bounce_bufs().

Signed-off-by: Adrian Hunter 
Reviewed-by: Linus Walleij 
Reviewed-by: Harjani Ritesh 
[Ulf: Fixed compiler warning]
Signed-off-by: Ulf Hansson

mmc: queue: Fix queue thread wake-up

2016-12-05T09:31:03+00:00

The only time the driver sleeps expecting to be woken upon the arrival of
a new request, is when the dispatch queue is empty. The only time that it
is known whether the dispatch queue is empty is after NULL is returned
from blk_fetch_request() while under the queue lock.

Recognizing those facts, simplify the synchronization between the queue
thread and the request function. A couple of flags tell the request
function what to do, and the queue lock and barriers associated with
wake-ups ensure synchronization.

The result is simpler and allows the removal of the context_info lock.

Signed-off-by: Adrian Hunter 
Reviewed-by: Linus Walleij 
Reviewed-by: Harjani Ritesh 
Signed-off-by: Ulf Hansson