public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@csr.com>
To: Ohad Ben-Cohen <ohad@bencohen.org>
Cc: akpm@linux-foundation.org, "p hilipl"@overt.org,
	ian@mnementh.co.uk, matt@console-pimps.org, pierre@ossman.eu,
	roberto.foglietta@gmail.com, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] sdio: add MMC_CAP_VDD_165_195 host capability
Date: Mon, 28 Sep 2009 19:09:52 +0100	[thread overview]
Message-ID: <4AC0FBF0.6090007@csr.com> (raw)
In-Reply-To: <1254160269.10634.15.camel@localhost>

Ohad Ben-Cohen wrote:
> From: Ohad Ben-Cohen <ohad@wizery.com>
> 
> To allow the usage of MMC_VDD_165_195, host capability
> MMC_CAP_VDD_165_195 is introduced. This is necessary
> because MMC_VDD_165_195 is currently reserved/undefined.

The host already reports what voltages it supports (in
mmc_host::ocr_avail) so a seperate MMC_CAP_* isn't needed.

This interpretation of the reserved bits in the OCR should only done for
certain cards where the bits actually do mean 1.8 V operation (with v2.0
signalling) is possible.

That's a fair amount of work so perhaps in the interim something like this:

--- a/drivers/mmc/core/sdio.c
+++ b/drivers/mmc/core/sdio.c
@@ -494,6 +494,9 @@ int mmc_attach_sdio(struct mmc_host *host, u32 ocr)
 		ocr &= ~0x7F;
 	}

+	if (ocr & MMC_VDD_165_195)
+		printk(KERN_WARNING "%s: warning: card claims non-standard 1.65-1.95
V support"
+
 	host->ocr = mmc_select_voltage(host, ocr);

 	/*

And revisit this if these bits either: a) gain a (different) standard
meaning; or b) some other card uses these bits in a different
non-standard way.  Neither seems likely.

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom

  reply	other threads:[~2009-09-28 18:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 17:51 [PATCH] sdio: add MMC_CAP_VDD_165_195 host capability Ohad Ben-Cohen
2009-09-28 18:09 ` David Vrabel [this message]
2009-09-28 20:02   ` Ohad Ben-Cohen
2009-09-29  2:25   ` Philip Langdale
2009-09-29 18:28     ` Pierre Ossman
2009-09-29 20:20       ` Philip Langdale
2009-09-29 21:37         ` Pierre Ossman
2009-09-30  6:10           ` Philip Langdale
2009-10-08 18:38             ` Pierre Ossman
2009-10-10 18:42               ` Philip Langdale
2009-10-12 13:11                 ` David Vrabel
2009-10-13  2:39                   ` Philip Langdale
2009-10-14  7:56                     ` Ohad Ben-Cohen
2009-10-14  8:48                       ` Pierre Ossman
2009-10-14 10:34                         ` David Vrabel
2009-10-14 11:05                           ` Pierre Ossman
  -- strict thread matches above, loose matches on Subject: below --
2009-09-28 17:55 Ohad Ben-Cohen
2009-09-28 17:58 Ohad Ben-Cohen
2009-09-28 18:10 ` Matt Fleming
2009-09-28 20:10   ` Ohad Ben-Cohen
2009-09-28 22:59   ` Andrew Morton
2009-09-29  5:53     ` Matt Fleming

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=4AC0FBF0.6090007@csr.com \
    --to=david.vrabel@csr.com \
    --cc="p hilipl"@overt.org \
    --cc=akpm@linux-foundation.org \
    --cc=ian@mnementh.co.uk \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=ohad@bencohen.org \
    --cc=pierre@ossman.eu \
    --cc=roberto.foglietta@gmail.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