Thanks.
Regards
Haijun.
-Original Message-
From: David Laight [mailto:david.lai...@aculab.com]
Sent: Thursday, July 11, 2013 4:44 PM
To: Wood Scott-B07421; Zhang Haijun-B42677
Cc: Zhao Chenhui-B35336; linux-mmc@vger.kernel.org; Wrobel Heinz-R39252;
Fleming Andy-AFLEMING; Zhang
Add host-off-card-on dt property and parse it to support the
quirk SDHCI_QUIRK2_HOST_OFF_CARD_ON.
Signed-off-by: Wei Ni w...@nvidia.com
---
Documentation/devicetree/bindings/mmc/mmc.txt |2 ++
drivers/mmc/host/sdhci-pltfm.c|3 +++
2 files changed, 5 insertions(+)
diff
In order to decrease the latency of a prioritized request (such as READ
requests) the device driver might decide to stop the transmission of a
current low priority request in order to handle the high priority one.
The urgency of the request is decided by the block layer I/O scheduler.
When the
Add support for reinserting a dispatched request back to the
scheduler's internal data structures.
This capability is used by the device driver when it chooses to
interrupt the current request transmission and execute another (more
urgent) pending request. For example: interrupting long write in
From: Jens Axboe ax...@kernel.dk
We have officially run out of flags in a 32-bit space. Extend it
to 64-bit even on 32-bit archs.
Signed-off-by: Jens Axboe ax...@kernel.dk
diff --git a/block/blk-core.c b/block/blk-core.c
index 93a18d1..cfa4dd3 100644
--- a/block/blk-core.c
+++
This patch add support in block elevator layers for handling
urgent requests. The decision if a request is urgent or not is taken
by the scheduler. Request is marked as urgent in cmd_flags (by the
scheduler) with a new flag - REQ_URGENT.
Urgent request notification is passed to the underlying
When the scheduler reports to the block layer that there is an urgent
request pending, the device driver may decide to stop the transmission
of the current request in order to handle the urgent one. This is done
in order to reduce the latency of an urgent request. For example:
long WRITE may be
On Wed, Jul 10, 2013 at 09:36:24PM +0530, a-bin...@ti.com wrote:
From: Amarinder Bindra a-bin...@ti.com
OMAP's hs_mmc driver is used for MMC controller operation on many
omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
Considering that the device tree entries are already present for
omap_hsmmc.c depends on linux/sizes.h being
included indirectly by another header. Once we
enable COMPILE_TEST for this driver, we might
compile under architectures which won't include
linux/sizes.h for us. In fact, one such case
is x86.
In order to prevent compile breakages, let's
explicitly
On 07/11/2013 03:43:35 AM, David Laight wrote:
+#define IS_SVR_REV(svr, maj, min) \
+ ((SVR_MAJ(svr) == (maj)) (SVR_MIN(svr) == (min)))
I don't think IS_SVR_REV is needed. Callers can just do if
(SVR_REV(svr) == 0x30) or whatever, especially since we're relying
on
them to do
Tanya Brokhman tlin...@codeaurora.org writes:
When the scheduler reports to the block layer that there is an urgent
request pending, the device driver may decide to stop the transmission
of the current request in order to handle the urgent one. This is done
in order to reduce the latency of
2013/7/10 Wolfram Sang w...@the-dreams.de:
Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
we can rely on device core for setting the default pins. Compile tested only.
Acked-by: Linus Walleij linus.wall...@linaro.org (personally at LCE13)
Signed-off-by: Wolfram
12 matches
Mail list logo
