On Wednesday 04 December 2013, dingu...@altera.com wrote:
> +
> +* compatible: should be
> +- "altr,socfpga-dw-mshc": for controllers with Altera SOCFPGA
> + specific extensions.
> +
> +* samsung,dw-mshc-sdr-timing: See exynos-dw-mshc.txt for more information
> about
> + this
On Wednesday 04 December 2013, dingu...@altera.com wrote:
> From: Dinh Nguyen
>
> The system manager is an IP block on the SOCFPGA platform. The system manager
> contains registers that control other IPs on the platform. One of the IPs that
> the system manager has control over is the SD/MMC, by
From: Dinh Nguyen
Hi,
This is v3 of the patch series to enable SD/MMC on the SOCFPGA platform. The
SD/MMC IP is the Synopsys DW SD/MMC driver. However, the settings for the
clock-phase of the CIU resides in a register that is located outside of SD/MMC
IP, in a register block called the system ma
From: Dinh Nguyen
The SDR timing registers for the SD/MMC IP block for SOCFPGA is located
in the system manager. This system manager IP block is located outside of
the SD IP block itself. We can use the normal clock API to set the SDR
settings.
Also, there is no need for "altr,dw-mshc-ciu-div" a
From: Dinh Nguyen
The "altr,sysmgr-sdmmc-sdr" compatible property is used for the SOCFPGA
clk-sysmgr driver. This property represents the register inside the
system manager that controls the clock phase of the SD/MMC driver.
Signed-off-by: Dinh Nguyen
---
v3: Cannot use the syscon driver along
From: Dinh Nguyen
The system manager is an IP block on the SOCFPGA platform. The system manager
contains registers that control other IPs on the platform. One of the IPs that
the system manager has control over is the SD/MMC, by way of controlling the
clock phase on the SD/MMC Card Interface Unit
From: Dinh Nguyen
Add new bindings that support SD/MMC on Altera's SOCFPGA platform.
Signed-off-by: Dinh Nguyen
---
v3: none
v2: none
---
.../devicetree/bindings/mmc/socfpga-dw-mshc.txt| 38
arch/arm/boot/dts/socfpga.dtsi | 11 ++
arch/arm/b
This patch adds the erase capability to OMAP1/OMAP2420 MMC driver. Idea is
the same than in commit 93caf8e ("omap_hsmmc: add erase capability") that we
disable the data timeout interrupt for erases.
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 18 +++---
1 file changed,
host-irq is set twice so remove needless one.
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
index 927ed24..b438f0a 100644
--- a/drivers/mmc/host/omap.c
+++ b/drivers/mmc/host/omap.c
@@
Hi
I've sent these patches earlier to linux-mmc list. This time set is one
patch smaller since commit 31ee9181eb92
("mmc: omap: Fix DMA configuration to not rely on device id") does
practically same what one of my patch did.
Patch 1 is an obvious fix. 2-4 are preparing for 5 which also should fix
Field mem_res in struct mmc_omap_host is used only once in mmc_omap_probe
when setting the phys_base field so we may just se the phys_base straight
and remove needless mem_res.
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
index 42b665d..927ed24 100644
--- a/drivers/mmc/host/omap.c
+++ b/drivers/mmc/host/omap.c
@@ -1345,7 +1345,8 @@ stat
Omap MMC driver initialization can cause a NULL pointer dereference in
tasklet_hi_action on Nokia N810 if its miniSD cover is open during driver
initialization.
[1.07] Unable to handle kernel NULL pointer dereference at virtual
address
[1.08] pgd = c0004000
[1.08]
Because use_dma is set only in mmc_omap_probe and unset nowhere there is no
need to carry that flag in struct mmc_omap_host for mmc_omap_prepare_data
function.
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --
Simplify probe and cleanup code by using devm_ioremap_resource. This also
makes probe code to follow more common allocate private struct followed by
other initialization style.
Signed-off-by: Jarkko Nikula
---
drivers/mmc/host/omap.c | 41 -
1 file changed
* Tony Lindgren [131202 11:36]:
> Commit 31ee9181eb92: (mmc: omap: Fix DMA configuration to not rely
> on device id) fixed getting of the DMA resources when booted with
> device tree. This patch however changed the handling of the
> free_mem_region() error path by reusing the struct resource *res
* Jarkko Nikula [131203 08:18]:
> On 12/02/2013 07:34 PM, Tony Lindgren wrote:
> > Commit 31ee9181eb92: (mmc: omap: Fix DMA configuration to not rely
> > on device id) fixed getting of the DMA resources when booted with
> > device tree. This patch however changed the handling of the
> > free_mem_r
Hi Olivier,
On Tue, Dec 03, 2013 at 10:59:28AM +0100, Olivier Sobrie wrote:
> Hi Ludovic,
>
> I'm trying to use a wlan sdio TI wl1271 module with an at91sam9263
> processor. The wlan card is correctly recognized by the kernel but
> once the driver tries to initialize the card, then I observe sdio
On Wed, Dec 04, 2013 at 09:29:15AM +0900, Jaehoon Chung wrote:
> To know whether eMMC card is version5.0 or not, add the check point.
>
> Signed-off-by: Jaehoon Chung
Reviewed-by: Jackey Shen
> ---
> mmc_cmds.c |3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mmc_cmds.c b/mmc_c
19 matches
Mail list logo
