linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Cc: Ian Molton <ian@mnementh.co.uk>,
	Samuel Ortiz <sameo@linux.intel.com>,
	linux-mmc@vger.kernel.org
Subject: [PATCH 3/3] sh: disable SD-card write-protection detection on kfr2r09
Date: Tue, 11 May 2010 09:52:39 +0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1005111152000.6810@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.1005111146330.6810@axis700.grange>

kfr2r09 board has a micro-SD card slot, therefore card write-protection
detection cannot work there, disable it.

Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
---
 arch/sh/boards/mach-kfr2r09/setup.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/arch/sh/boards/mach-kfr2r09/setup.c b/arch/sh/boards/mach-kfr2r09/setup.c
index 95850aa..68994a1 100644
--- a/arch/sh/boards/mach-kfr2r09/setup.c
+++ b/arch/sh/boards/mach-kfr2r09/setup.c
@@ -11,6 +11,7 @@
 #include <linux/platform_device.h>
 #include <linux/interrupt.h>
 #include <linux/mfd/sh_mobile_sdhi.h>
+#include <linux/mfd/tmio.h>
 #include <linux/mtd/physmap.h>
 #include <linux/mtd/onenand.h>
 #include <linux/delay.h>
@@ -358,8 +359,9 @@ static struct resource kfr2r09_sh_sdhi0_resources[] = {
 };
 
 static struct sh_mobile_sdhi_info sh7724_sdhi0_data = {
-	.dma_slave_tx = SHDMA_SLAVE_SDHI0_TX,
-	.dma_slave_rx = SHDMA_SLAVE_SDHI0_RX,
+	.dma_slave_tx	= SHDMA_SLAVE_SDHI0_TX,
+	.dma_slave_rx	= SHDMA_SLAVE_SDHI0_RX,
+	.tmio_flags	= TMIO_MMC_WRPROTECT_DISABLE,
 };
 
 static struct platform_device kfr2r09_sh_sdhi0_device = {
-- 
1.6.2.4


  parent reply	other threads:[~2010-05-11  9:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11  9:52 [PATCH 0/3] tmio: let platforms decide upon write-protection Guennadi Liakhovetski
2010-05-11  9:52 ` [PATCH 1/3] tmio: add a platform flag to disable card write-protection Guennadi Liakhovetski
2010-05-11 12:04   ` [PATCH 1/3] tmio: add a platform flag to disable card Magnus Damm
2010-05-11 12:15     ` Guennadi Liakhovetski
2010-05-11 12:17       ` Magnus Damm
2010-05-11  9:52 ` [PATCH 2/3] mfd: pass platform flags down to the tmio_mmc driver Guennadi Liakhovetski
2010-05-13 16:08   ` [PATCH 2/3 v2] " Guennadi Liakhovetski
2010-05-11  9:52 ` Guennadi Liakhovetski [this message]
2010-05-19 18:35 ` [PATCH 0/3] tmio: let platforms decide upon write-protection Guennadi Liakhovetski
2010-05-19 18:36   ` [PATCH 1/3] tmio: add a platform flag to disable card write-protection Guennadi Liakhovetski
2010-05-19 18:36   ` [PATCH 2/3 v2] mfd: pass platform flags down to the tmio_mmc driver Guennadi Liakhovetski
2010-05-19 18:36   ` [PATCH 3/3] sh: disable SD-card write-protection detection on kfr2r09 Guennadi Liakhovetski
2010-05-21 19:38   ` [PATCH 0/3] tmio: let platforms decide upon write-protection Andrew Morton
2010-05-22  7:33     ` [PATCH 0/3] tmio: let platforms decide upon write-protection availability Paul Mundt
2010-05-22  8:10       ` Paul Mundt
2010-05-25 19:09         ` [PATCH 0/3] tmio: let platforms decide upon write-protection Ian Molton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.1005111152000.6810@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=ian@mnementh.co.uk \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).