This patchset aim to fix several sdhci bugs.
All the patches have been verified on sdhci-pxav3 platforms.
This patchset based on previous patch:
[PATCH v10 00/12] mmc: sdhci: fixes and enhancements
Introduction for the patches:
[PATCH 1/5] mmc: sdhci: fix transfer mode setting bug for cmds w/o
According to SD host spec (Capabilities Register, offset 0x4043:40),
if timer count for retuning return 0xF, it means get information from other
source
Signed-off-by: Kevin Liu kl...@marvell.com
---
drivers/mmc/host/sdhci.c |8
drivers/mmc/host/sdhci.h |1 +
2 files changed, 9
With current code, for commands like cmd5/cmd7 which transfer without data,
function sdhci_set_transfer_mode will just return without updating the
transfer setting. So the Transfer Mode Register (offset 0x3E) still keep
previous setting, which may be wrong since some bits (0x3E5:0) may have
been
Correct the judgement logic. When regulator vmmc is used, the voltage caps
should be cleared manually when both below conditions are true:
1. The requested voltage range is actually not supported by the regulator.
2. The voltage caps read from the capability register has been set.
Signed-off-by:
set_uhs_signaling was introduced in sdhci-pxav3.c to enable 1.8v signaling.
The function can be removed after sdhci.c has covered this.
Acked-by: Zhangfei Gao zhangfei@marvell.com
Signed-off-by: Kevin Liu kl...@marvell.com
---
drivers/mmc/host/sdhci-pxav3.c | 39
According to SD host controller spec (Host Control 2 Register,
offset 0x3E3:0), 1.8v signaling (0x3E3) must be enabled for
UHS-I modes. Otherwise all UHS-I modes will _NOT_ take effect.
Emmc chip working with DDR mode need host select UHS-I DDR50 mode.
So 1.8v signaling must also be enabled for
-Original Message-
From: Lars-Peter Clausen [mailto:l...@metafoo.de]
Sent: Tuesday, January 29, 2013 2:27 AM
To: Chris Ball
Cc: Stephen Warren; Shawn Guo; Zhangfei Gao; Kevin Liu;
linux-mmc@vger.kernel.org; Lars-Peter Clausen
Subject: [PATCH] mmc: sdhci-pltfm: Add a common clk API
On 01/29/2013 06:45 AM, Stephen Warren wrote:
On 01/28/2013 11:27 AM, Lars-Peter Clausen wrote:
Quite a few drivers have a implementation of the get_timeout_clock callback
which simply returns the result of clk_get_rate on devices clock. This patch
adds a common implementation of this to the
According to SD host spec (Capabilities Register, offset 0x4043:40),
if timer count for retuning return 0xF, it means get information from
other source. If driver didn't provide the function in case timer count
return 0xF, just disable retuning.
Signed-off-by: Kevin Liu kl...@marvell.com
On 01/29/2013 02:22 AM, Lars-Peter Clausen wrote:
On 01/29/2013 06:45 AM, Stephen Warren wrote:
On 01/28/2013 11:27 AM, Lars-Peter Clausen wrote:
Quite a few drivers have a implementation of the get_timeout_clock callback
which simply returns the result of clk_get_rate on devices clock. This
SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK does basically the same as
implementing struct sdhci_ops .get_timeout_clock, so simply set that
quirk and remove the custom code to simplify the driver.
Reported-by: Lars-Peter Clausen l...@metafoo.de
Signed-off-by: Stephen Warren swar...@wwwdotorg.org
---
On Wed, Jan 23, 2013 at 10:28:46PM +, Arnd Bergmann wrote:
On Tuesday 15 January 2013, Matt Porter wrote:
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
On Mon, Jan 28, 2013 at 09:27:24PM +0200, Andy Shevchenko wrote:
On Tue, Jan 15, 2013 at 10:32 PM, Matt Porter mpor...@ti.com wrote:
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data. Enables runtime PM support to
initialize the EDMA hwmod. Adds
Changes since v5:
- Dropped mmc portion and moved it to a separate series
- Incorporate corrected version of dma_request_slave_channel_compat()
- Fix #defines and enablement of TI_PRIV_EDMA option
Changes since v4:
- Fixed debug section mismatch in private edma api
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
instantiated via DT, the appropriate channel request call will be
made.
This allows for a much cleaner migration of drivers
The binding definition is based on the generic DMA request binding
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 27 +++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +
1 file changed, 49 insertions(+)
create mode 100644
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well. This just moves the
private EDMA API and enables it to build on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Sekhar Nori nsek...@ti.com
---
arch/arm/Kconfig
Fix build on OMAP, the irqs are undefined on AM33xx.
These error interrupt handlers were hardcoded as disabled
so since they are unused code, simply remove them.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Sekhar Nori nsek...@ti.com
---
arch/arm/common/edma.c | 37
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
---
drivers/dma/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index 0b408bb..239020b 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data. Enables runtime PM support to
initialize the EDMA hwmod. Adds AM33XX EMDA crossbar event mux
support.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Sekhar Nori nsek...@ti.com
---
On Wed, Jan 30, 2013 at 8:41 AM, Matt Porter mpor...@ti.com wrote:
On Mon, Jan 28, 2013 at 09:27:24PM +0200, Andy Shevchenko wrote:
On Tue, Jan 15, 2013 at 10:32 PM, Matt Porter mpor...@ti.com wrote:
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform
23 matches
Mail list logo
