From: Pierre Ossman <drzeus@drzeus.cx>
To: Philip Langdale <philipl@overt.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, sdhci-devel@list.drzeus.cx,
fseidel@suse.de, weyland@library.ethz.ch
Subject: Re: [PATCH] ricoh_mmc: Handle newer models of Ricoh controllers
Date: Wed, 26 Nov 2008 16:12:54 +0100 [thread overview]
Message-ID: <20081126161254.25ee531f@mjolnir.drzeus.cx> (raw)
In-Reply-To: <492D6300.2060401@overt.org>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Wed, 26 Nov 2008 06:53:52 -0800
Philip Langdale <philipl@overt.org> wrote:
> Matthew Garrett wrote:
> >
> > Thinking about it, it could possibly be handled by changing to
> > suspend_noirq and resume_noirq rather than the normal suspend and resume
> > functions? That ought to get the ordering constraints right. The problem
> > occurs when ricoh_mmc suspends before sdhci and resumes after it.
>
> I'll investigate that and see what happens.
>
Or you integrate it into sdhci_pci. Look at the register fiddling for
JMicron chips in there.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-11-26 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 8:42 Philip Langdale
2008-11-25 9:27 ` Mathias Weyland
2008-11-25 10:45 ` Pierre Ossman
2008-11-26 15:22 ` Frank Seidel
2008-11-26 13:36 ` Frans Pop
2008-11-26 14:42 ` Philip Langdale
2008-11-26 14:45 ` Pierre Ossman
2008-11-26 14:50 ` Matthew Garrett
2008-11-26 14:53 ` Philip Langdale
2008-11-26 15:12 ` 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=20081126161254.25ee531f@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=elendil@planet.nl \
--cc=fseidel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=philipl@overt.org \
--cc=sdhci-devel@list.drzeus.cx \
--cc=weyland@library.ethz.ch \
/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
all inboxes | Powered by JetHome®