On Tue, Jan 3, 2012 at 11:33 AM, Ulf Hansson ulf.hans...@stericsson.com wrote:
Removing a card slowly can trigger a GPIO irq to be raised far
before the card is actually removed. This means the scheduled
detect work will not find out that the card were removed and thus
the card and the block
Dmitry Shmidt wrote:
Signed-off-by: Dmitry Shmidt dimitr...@google.com
---
drivers/mmc/card/block.c |2 +-
drivers/mmc/core/bus.c | 25 +++--
include/linux/mmc/card.h |2 +-
3 files changed, 9 insertions(+), 20 deletions(-)
diff --git a/drivers/mmc/card/block.c
This patch adds a primitive helper to support card hotplug detection on
platforms, where a GPIO, capable of producing interrupts, is used for
detection of card-insertion and -removal events.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
v2: allow NULL hotplug handler context in
On ARM the same clock is used by the PM subsystem and by the driver
directly. This leads to the clock staying permanently on, independent of
the runtime PM state. This patch makes clock enable and disable calls in
the driver SuperH-specific.
Signed-off-by: Guennadi Liakhovetski
This patch series uses a previously proposed generic GPIO card hotplug
handler, fixes multiple PM issues, adds some cosmetic clean up. Not all of
these patches really depend on each other, but it's easier to preserve the
original order. Some patches, e.g., #9, are an RFC so far and might have
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
drivers/mmc/host/tmio_mmc_pio.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/host/tmio_mmc_pio.c b/drivers/mmc/host/tmio_mmc_pio.c
index 9106b3d..f68e6f3 100644
---
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
Only compile-tested.
arch/arm/mach-shmobile/board-ag5evm.c | 24
1 files changed, 4 insertions(+), 20 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-ag5evm.c
Now, that all users of tmio_mmc_cd_wakeup() have been converted over to
drivers/mmc/core/cd-gpio.c, that function can be removed.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
include/linux/mfd/tmio.h | 11 ---
1 files changed, 0 insertions(+), 11 deletions(-)
diff
To use TMIO MMC driver ability to interface to the generic MMC GPIO card
hotplug detection helper, the SDHI driver has to pass the GPIO number and
IRQ flags down from its own platform data.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
drivers/mmc/host/sh_mobile_sdhi.c |5
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
arch/arm/mach-shmobile/board-mackerel.c | 24
1 files changed, 4 insertions(+), 20 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-mackerel.c
b/arch/arm/mach-shmobile/board-mackerel.c
index
The condition, whether we have to use the native TMIO card hotplug
detection interrupt, is rather complex, it is better to only calculate it
once and store in the private data.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
drivers/mmc/host/tmio_mmc.h |1 +
On 3/01/2012 12:33 p.m., Ulf Hansson wrote:
Removing a card slowly can trigger a GPIO irq to be raised far
before the card is actually removed. This means the scheduled
detect work will not find out that the card were removed and thus
the card and the block device will not be unregistered.
One
Enable eMMC background operations (BKOPS) feature.
If URGENT_BKOPS is set after a response, note that BKOPS
are required. After all I/O requests are finished, run
BKOPS if required. Should read/write operations be requested
during BKOPS, first issue HPI to interrupt the ongoing BKOPS
and then
On Wed, Jan 04, 2012 at 04:01:07PM +0100, Matthieu CASTET wrote:
Hi,
our controller set Max Block Length to 3 (4096 byte), but the linux driver
ignore this value [1].
Is there any reason to do that .
The reason is, sd host controller spec defines 3 as reserved, not 4096.
Or it is code
This patch is support the sysfs for operation mode.
There are two operation modes(open-ended/pre-defined).
Now, operation mode is selected only one at the compile time.
But using this patch, we can change the operation mode with node at runtime.
* pre-defined mode
echo 1
Fix the following build warning:
warning: (MMC_TIFM_SD MEMSTICK_TIFM_MS) selects TIFM_CORE which has unmet
direct dependencies (MISC_DEVICES EXPERIMENTAL PCI)
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
drivers/memstick/host/Kconfig |2 +-
drivers/mmc/host/Kconfig
Hi,
On Tue, Jan 03 2012, Will Newton wrote:
On Mon, Jan 2, 2012 at 7:00 AM, Seungwon Jeon tgih@samsung.com wrote:
UHS_REG should be cleared for non-DDR mode. But currently there is
no way to clear DDR mode, if it is already set once. This patch adds
clearing DDR mode for non-DDD mode.
Hi,
On Wed, Jan 04 2012, Viresh Kumar wrote:
With the inclusion of following patch:
mmc: sdhci: remove state argument from sdhci_suspend_host
we get a compilation error for sdhci-spear:
drivers/mmc/host/sdhci-spear.c:283:2: error: too many arguments to function
‘sdhci_suspend_host’
This
Hi, all..
Here is description for MMC block devices in Documentation/devices.txt :
179 block MMC block devices
0 = /dev/mmcblk0 First SD/MMC card
1 = /dev/mmcblk0p1First partition on first MMC card
8 =
19 matches
Mail list logo
