All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Thomas Bechtold <thomasbechtold@jpberlin.de>
Cc: linux-mmc@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: "mmc_host mmc0: WARNING: IMR=0x00004040" on debug console
Date: Sat, 04 Feb 2012 17:54:36 -0500	[thread overview]
Message-ID: <m2ipjm9plf.fsf@bob.laptop.org> (raw)
In-Reply-To: <1326989504.2687.3.camel@salbei.fritz.box> (Thomas Bechtold's message of "Thu, 19 Jan 2012 17:11:44 +0100")

Hi, adding some recent atmel-mci.c committers to the thread,

On Thu, Jan 19 2012, Thomas Bechtold wrote:
> i updated from kernel 2.6.35.3 (from kernel.org) to kernel 3.2.1 (from 
> kernel.org) on arm (at91stamp9G20) and have a MMC card which can be 
> completly disabled with a hardware switch. The mmc card is then used by 
> another processor without linux. That works very well.
> My question is, why i get always the message "mmc_host mmc0: WARNING: 
> IMR=0x00004040" after i removed the mmc card slot once. That's a new 
> behavior with 3.2.1. I had no message with 2.6.35.3.
> When the mmc slot returns to linux, the message stops and i get:
>
> mmc_host mmc0: WARNING: IMR=0x00004040
> mmc0: host does not support reading read-only switch. assuming write-enable.
> mmc0: new SD card at address b368
> mmcblk0: mmc0:b368 H1697 1.91 GiB
>   mmcblk0: unknown partition table
>
> That's fine.
>
> Should i just ignore the message (or simple patch 
> driver/mmc/host/atmel_mci.c)?

It would be good to leave the warning in for situations that we still
don't expect, and it looks like IMR=0x00004040 decodes to ATMCI_ENDTX
and ATMCI_TXBUFE, so you could try something like:

        if (iflags & ~(ATMCI_SDIOIRQA | ATMCI_SDIOIRQB)) {
                /* Interrupts with ENDTX and TXBUFE set are seen
                 * with at91stamp9G20 hardware when switching the
                 * processor that MMC is attached to, so don't warn
                 * if they are set. 
                 */
                if (iflags & ~(ATMCI_ENDTX | ATMCI_TXBUFE)) {
                        dev_warn(&slot->mmc->class_dev, "WARNING: IMR="
                                 "0x%08x\n", iflags);
                }
        }

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-02-04 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 16:11 "mmc_host mmc0: WARNING: IMR=0x00004040" on debug console Thomas Bechtold
2012-02-04 22:54 ` Chris Ball [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-19 14:04 Thomas Bechtold

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=m2ipjm9plf.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=thomasbechtold@jpberlin.de \
    /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.