public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Dong Aisheng <dongas86@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
	Chris Ball <chris@printf.net>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	brcm80211-dev-list@broadcom.com
Subject: Re: brcm 4329 problems
Date: Tue, 11 Feb 2014 10:27:33 +0000	[thread overview]
Message-ID: <20140211102733.GG26684@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAA+hA=Si4k0A5_-ve0oh8FKxCGDg5pD_M=Z4g2Ca7UWJaeq6Rw@mail.gmail.com>

On Tue, Feb 11, 2014 at 03:33:09PM +0800, Dong Aisheng wrote:
> It depends on both host and card that 1) if host is able to detect
> SDIO interrupts without clock
> and 2) if the card is able to send interrupt to host without clock.
> If any one of both can't do that, we may need to tell host to not
> do runtime suspend to prevent the clock from being disabled.
> Or the SDIO interrupt may not work.
> 
> The IMX esdhc/usdhc can not detect the SDIO interrupts sent from card
> if the clock is disabled.
> So we need such quirk to not allow runtime PM for SDIO cards.
> Doesn't it make sense?

That's strange.  I have it working as of last night.

Yes, I have to leave the AHB clock on so that the registers are readable,
in the interrupt handler, and that's something I only do if the SDIO
interrupt is enabled, but everything else gets disabled.

-- 
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up.  Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".

  parent reply	other threads:[~2014-02-11 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140201221548.GB26684@n2100.arm.linux.org.uk>
     [not found] ` <52EF59CB.5050901@broadcom.com>
     [not found]   ` <20140203153239.GL26684@n2100.arm.linux.org.uk>
     [not found]     ` <52F00021.6070904@broadcom.com>
     [not found]       ` <20140203210450.GN26684@n2100.arm.linux.org.uk>
     [not found]         ` <52F14F7E.9040900@broadcom.com>
     [not found]           ` <20140205153824.GS26684@n2100.arm.linux.org.uk>
     [not found]             ` <20140208215927.GA5276@n2100.arm.linux.org.uk>
     [not found]               ` <52F744C9.7040804@broadcom.com>
     [not found]                 ` <20140209205917.GO26684@n2100.arm.linux.org.uk>
2014-02-09 23:27                   ` brcm 4329 problems Russell King - ARM Linux
2014-02-10  6:50                     ` Dong Aisheng
2014-02-10 14:03                       ` Russell King - ARM Linux
2014-02-10 14:19                         ` Arend van Spriel
2014-02-10 15:25                         ` Ulf Hansson
2014-02-11  7:38                           ` Dong Aisheng
2014-02-11  9:46                             ` Ulf Hansson
2014-02-12  3:49                               ` Dong Aisheng
2014-02-11  7:33                         ` Dong Aisheng
2014-02-11  9:00                           ` Ulf Hansson
2014-02-12  3:06                             ` Dong Aisheng
2014-02-12 10:01                               ` Ulf Hansson
2014-02-11 10:27                           ` Russell King - ARM Linux [this message]
2014-02-12  3:17                             ` Dong Aisheng
2014-02-12  9:36                               ` Russell King - ARM Linux
2014-02-10 10:07                     ` Arend van Spriel

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=20140211102733.GG26684@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=chris@printf.net \
    --cc=dongas86@gmail.com \
    --cc=linux-mmc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox