All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Philip Langdale <philipl@overt.org>
Cc: linux-kernel@vger.kernel.org, Alex Dubov <oakad@yahoo.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.19] mmc: Add support for SDHC cards (Take 4)
Date: Thu, 04 Jan 2007 15:33:34 +0100	[thread overview]
Message-ID: <459D103E.4080605@drzeus.cx> (raw)
In-Reply-To: <459D0C4C.2050401@overt.org>

Philip Langdale wrote:
> In the process of developing this patch, we realised that the R6 response definition
> was incorrect and that it should have been identical to R1 (and so should R7).
> Correcting this mistake revealed problems in a couple of host controller drivers that
> relied on the response definitions to be unique. As we need a story for R7, I've
> also fixed up the R6 handling in the affected drivers but I have no idea if it will
> work in practice as I lack the hardware.
>
>   

Do this fix in a separate patch. And cc the relevant maintainers.

> --- /usr/src/linux/drivers/mmc/imxmmc.c	2007-01-01 07:12:02.000000000 -0800
> +++ linux-2.6.19-sdhc/drivers/mmc/imxmmc.c	2007-01-04 05:50:41.000000000 -0800
> @@ -351,9 +360,6 @@
>  	case MMC_RSP_R3: /* short */
>  		cmdat |= CMD_DAT_CONT_RESPONSE_FORMAT_R3;
>  		break;
> -	case MMC_RSP_R6: /* short CRC */
> -		cmdat |= CMD_DAT_CONT_RESPONSE_FORMAT_R6;
> -		break;
>  	default:
>  		break;
>  	}
>   

I think this chunk suffices. Until proven otherwise, regard R6 and R7 as
information the hw does not need to know about. Same thing in tifm_sd.

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org


      reply	other threads:[~2007-01-04 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 14:16 [PATCH 2.6.19] mmc: Add support for SDHC cards (Take 4) Philip Langdale
2007-01-04 14:33 ` Pierre Ossman [this message]

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=459D103E.4080605@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=philipl@overt.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.