Documentation about the background and the design of mmc non-blocking.
Host driver guidelines to minimize request preparation overhead.
Signed-off-by: Per Forlin per.for...@linaro.org
Acked-by: Randy Dunlap rdun...@xenotime.net
---
ChangeLog:
v2: - Minor updates after proofreading comments from
On Wed, Jul 6, 2011 at 4:20 AM, Philip Rakity prak...@marvell.com wrote:
Subject: [PATCH V3] arm: mach-mmp: brownstone.c support multiple sd slots
V3
==
Change since V2 -- delete mmc3 since it was committed
to linux next.
enable mmc1 used for wifi (8688) and marked PERMANENT.
Wifi
Take care of slots while going to suspend state.
Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com
---
V4: make CONFIG_PM logic work even if not selected
V3: take care of each slot SUSPENDED state
(adding a status bit in the slot flags)
V2: move to pm_ops
drivers/mmc/host/atmel-mci.c |
Hi,
On Wed, Jul 06, 2011 at 11:31:36AM +0200, Nicolas Ferre wrote:
Take care of slots while going to suspend state.
Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com
FWIW:
Reviewed-by: Felipe Balbi ba...@ti.com
@@ -1878,10 +1879,72 @@ static int __exit atmci_remove(struct
dmaengine expects the maxburst parameter in words, not bytes.
The imxdma driver and its users do this wrong. Fix this.
As a side note the imx-pcm-dma-mx2 driver was 'fixed' to work
with imx-dma. This broke the driver with imx-sdma support which
correctly takes the maxburst parameter in words.
About the patch itself: I didn't verify the formulas, but it does solve one
special problem here. Thanks a lot! So:
Does it solve any other special problem except for the wrong clock rate
setting?
Nope, but that it does :)
--
Pengutronix e.K. | Wolfram Sang
No changes since v1 except acked-by and tested-by
More improvements and fixes for the Synopsys DesignWare MCI driver so
that it passes the mmc_test suite:
[PATCH 1/4] mmc: dw_mmc: fix stop when fallen back to PIO
Fixes a hang after an error/timeout in PIO mode.
[PATCH 2/4] mmc: dw_mmc:
There are several situations when dw_mci_submit_data_dma() decides to
fall back to PIO mode instead of using DMA, due to a short (to avoid
overhead) or complex (e.g. with unaligned buffers) transaction, even
though host-use_dma is set. However dw_mci_stop_dma() decides whether
to stop DMA or set
Remove error messages for timeout and CRC failure, since the error code
already indicates the problem.
Signed-off-by: James Hogan james.ho...@imgtec.com
Acked-by: Will Newton will.new...@imgtec.com
Tested-by: Jaehoon Chung jh80.ch...@samsung.com
---
drivers/mmc/host/dw_mmc.c |4
1 files
On Mon, Jul 04, 2011 at 12:59:29PM +0200, Koen Beel wrote:
On Mon, Jul 4, 2011 at 12:34 PM, Wolfram Sang w.s...@pengutronix.de wrote:
Well, maybe not. My colleague complained and I think he is right
that we are
mapping div2 from the range 0 to 256 (inclusive!) to an 8-bit range.
When a data write isn't acknowledged by the card (so no CRC status token
is detected after the data), the error -EIO is returned instead of the
-ETIMEDOUT expected by mmc_test 15 - Correct xfer_size at write (start
failure) and 17 Correct xfer_size at write (midway failure). In PIO
mode the
If an error occurs mid way through a transaction (such as a missing CRC
status response after the 2nd block written out of 3), then the FIFO may
still contain data which will interfere with the next transaction.
Therefore after an error has been detected, reset the fifo using the
CTRL register.
On Wed, Jul 6, 2011 at 11:38 AM, Wolfram Sang w.s...@pengutronix.de wrote:
On Mon, Jul 04, 2011 at 12:59:29PM +0200, Koen Beel wrote:
On Mon, Jul 4, 2011 at 12:34 PM, Wolfram Sang w.s...@pengutronix.de wrote:
Well, maybe not. My colleague complained and I think he is right
that we
I think I misunderstood this suggestion previously. Using DIV_ROUND_UP
would do the rounding in the correct direction.
This should result in: the actual clock is as high as possible
without being higher then the requested clock.
Yes, that should be done in V2. And if you could also put the
Led Technology srl vi presenta questo fantastico prodotto per presentare il
vostro Menù in un modo più tecnologico,
oppure la lampada a led per illuminare i vostri tavoli sotto gli ombrelloni.
Vedi la brochure della lavagna cliccando su questo link:
Hi!
HPI is a feature to handle a higher or urgent request then pre-ongoing
request and it's only possible when some conditions are met.
Agreed, as I read the spec this would writes, erases and BKOPS
(eMMC spec 4.41 7.6.20 (table 20) and the 3rd paragraph in 7.6.19).
BKOPS is a feature to
On Wed, Jul 06, 2011 at 11:18:33AM +0200, Sascha Hauer wrote:
dmaengine expects the maxburst parameter in words, not bytes.
The imxdma driver and its users do this wrong. Fix this.
As a side note the imx-pcm-dma-mx2 driver was 'fixed' to work
with imx-dma. This broke the driver with imx-sdma
On Wed, Jul 6, 2011 at 11:40 PM, Sebastian RASMUSSEN
sebastian.rasmus...@stericsson.com wrote:
Hi!
HPI is a feature to handle a higher or urgent request then pre-ongoing
request and it's only possible when some conditions are met.
Agreed, as I read the spec this would writes, erases and
On Jul 6, 2011, at 12:19 AM, zhangfei gao wrote:
On Wed, Jul 6, 2011 at 4:20 AM, Philip Rakity prak...@marvell.com wrote:
Subject: [PATCH V3] arm: mach-mmp: brownstone.c support multiple sd slots
V3
==
Change since V2 -- delete mmc3 since it was committed
to linux next.
enable mmc1
On Tue, Jul 05, 2011 at 11:54:34AM -0600, Grant Likely wrote:
On Tue, Jul 5, 2011 at 9:26 AM, Shawn Guo shawn@linaro.org wrote:
The patch adds device tree probe support for sdhci-esdhc-imx driver.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Wolfram Sang w.s...@pengutronix.de
On Wed, Jul 06, 2011 at 11:43:15PM +0800, Shawn Guo wrote:
On Tue, Jul 05, 2011 at 11:54:34AM -0600, Grant Likely wrote:
On Tue, Jul 5, 2011 at 9:26 AM, Shawn Guo shawn@linaro.org wrote:
The patch adds device tree probe support for sdhci-esdhc-imx driver.
Signed-off-by: Shawn Guo
V2
--
Include host.h change for callback to select_drive_strength
V1
--
Non default Drive Strength cannot be set automatically.
It is a function of the board design and only if there
is a specific platform handler can it be set. The platform
handler needs to take into account the board design.
the simplistic test of booting, and then suspending
(without loading the libertas driver), things go wrong:
http://dev.laptop.org/~dsd/20110706/dmesg.txt
I added printk's in mmc_power_save_host and mmc_power_restore_host.
The strange thing is that it tries to resume mmc1 even though it is
powered
Eric,
Not sure what to suggest.
If it makes more sense to take V3 which powers on the wifi card but does not do
power handling per
new spec take that. At least wifi card works and then wait for power code.
New code could delete
power code as part of the mod.
If it makes more sense to wait
On Thu, Jul 7, 2011 at 12:08 AM, Philip Rakity prak...@marvell.com wrote:
Eric,
Not sure what to suggest.
If it makes more sense to take V3 which powers on the wifi card but does not
do power handling per
new spec take that. At least wifi card works and then wait for power code.
New
Hi!
1. I wonder BKOPS is really required to perform frequently?
Yes I know it's helpful to use but no need to call it frequently.
I believe that the patch properly checks for R1_URGENT_BKOPS,
which seems correct..?
Right, it checks the R1_URGENT_BKOPS, I mean it called every user
The patch copies platform data into pltfm_imx_data and reference
the data there than platform data after probe.
This work is inspired by Grant Likely and Troy Kisky.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Troy Kisky troy.ki...@boundarydevices.com
Cc: Grant Likely
The patch removes all the uses of cpu_is_mx(). Instead, it utilizes
platform_device_id to distinguish the esdhc differences among SoCs.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Wolfram Sang w.s...@pengutronix.de
Cc: Chris Ball c...@laptop.org
Acked-by: Grant Likely
Neither platform based nor dt based device needs to pass the parent
to sdhci_alloc_host. There is no difference between platform and dt
on this point.
The patch makes the change to pass device itself than its parent to
sdhci_alloc_host for dt case too. Otherwise the probe function of
sdhci
The first patch copies platform data into driver private data, and
do not reference platform data after probe. The second one removes
the uses of cpu_is_mx(). The third one makes a dt related fix on
sdhci-pltfm.c, and the last one adds actual device tree probe for
sdhci-esdhc-imx driver.
The patch adds device tree probe support for sdhci-esdhc-imx driver.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Wolfram Sang w.s...@pengutronix.de
Cc: Chris Ball c...@laptop.org
Cc: Grant Likely grant.lik...@secretlab.ca
---
.../devicetree/bindings/mmc/fsl-imx-esdhc.txt | 34
Hi Philip,
-Original Message-
From: Philip Rakity [mailto:prak...@marvell.com]
Sent: Wednesday, July 06, 2011 9:22 PM
To: linux-mmc@vger.kernel.org
Cc: Nath, Arindam
Subject: [PATCH V2] mmc: sd.c Set Non Default Drive Strength via
platform
V2
--
Include host.h change for
On Tue, Jul 5, 2011 at 5:57 PM, Hanumath Prasad
hanumath.pra...@stericsson.com wrote:
Background operations is an optional feature defined in eMMC4.41 spec.
The need for BKOPS will be checked after servicing each user request
in R1 response. If need for BKOPS flag is set, then start BKOPS when
On Tue, Jul 05, 2011 at 12:16:11PM +0100, Russell King - ARM Linux wrote:
On Tue, Jun 28, 2011 at 09:57:25AM +0200, Linus Walleij wrote:
Stresstesting insert/remove of SD-cards can trigger
a StartBitErr. This made the driver to hang in forever
waiting for a non ocurring data timeout.
On Thu, Jul 07, 2011 at 12:47:47AM +0800, Shawn Guo wrote:
The patch copies platform data into pltfm_imx_data and reference
the data there than platform data after probe.
This work is inspired by Grant Likely and Troy Kisky.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Troy Kisky
On Thu, Jul 07, 2011 at 12:47:50AM +0800, Shawn Guo wrote:
The patch adds device tree probe support for sdhci-esdhc-imx driver.
Signed-off-by: Shawn Guo shawn@linaro.org
Cc: Wolfram Sang w.s...@pengutronix.de
Cc: Chris Ball c...@laptop.org
Cc: Grant Likely grant.lik...@secretlab.ca
On Wed, 2011-07-06 at 08:03 -0700, Mark Brown wrote:
On Wed, Jul 06, 2011 at 11:18:33AM +0200, Sascha Hauer wrote:
dmaengine expects the maxburst parameter in words, not bytes.
The imxdma driver and its users do this wrong. Fix this.
As a side note the imx-pcm-dma-mx2 driver was 'fixed'
37 matches
Mail list logo
