From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: kernel@avr32linux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] atmel-mci: support multiple mmc slots
Date: Thu, 25 Sep 2008 09:05:56 +0200 [thread overview]
Message-ID: <20080925090556.44940c89@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080924163527.30cfc223@hskinnemo-gx745.norway.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
On Wed, 24 Sep 2008 16:35:27 +0200
Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
>
> On AP7000, the clock line is shared. Do I have to run the clock at the
> minimum of the two slots' maximum rates, or does it only matter when
> the card is being accessed?
>
I'd say always. I'd never dare overclock something that's powered, even
if we're not currently communicating with it.
Remember to deal with the case of a powered but unclocked card. This
will primarily happen during card init, but it could should up later as
well if we start implementing aggressive power management.
> > > > (This will also get a bit more painful when/if the core starts
> > > > disabling the clock when a card is idle)
> > >
> > > The atmel-mci driver already stops the clock between requests.
> >
> > Then I expect a patch to remove that. Fiddling with the clock is
> > dangerous and I've seen everything from hung cards to silently broken
> > writes when you disable the clock too early after a request.
>
> Ok. I'll see if I can fix that -- I take it you want a patch for
> 2.6.27, then?
>
.28 should be fine. It's a pretty uncommon bug.
> > > >
> > > > Fall back to polling?
> > >
> > > Probably, yes. Can I fall back to polling after the host has been
> > > registered?
> > >
> >
> > Hmm... no. Not sure how to handle this...
>
> I'll see if I can figure out a way to do it. I'm not giving it high
> priority since it's a fairly obscure error case which shouldn't happen
> with properly implemented board code.
>
Agreed.
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
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 --]
next prev parent reply other threads:[~2008-09-25 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 16:38 [PATCH 0/4] atmel-mci: updates for 2.6.28 Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 1/4] atmel-mci: Implement tasklet as a state machine Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 2/4] atmel-mci: Platform code for supporting multiple mmc slots Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 3/4] atmel-mci: support " Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 4/4] atmel-mci: Add experimental DMA support Haavard Skinnemoen
2008-09-23 17:53 ` [PATCH 3/4] atmel-mci: support multiple mmc slots Pierre Ossman
2008-09-23 18:16 ` Haavard Skinnemoen
2008-09-23 19:12 ` Pierre Ossman
2008-09-24 14:35 ` Haavard Skinnemoen
2008-09-25 7:05 ` Pierre Ossman [this message]
2008-09-25 13:51 ` Haavard Skinnemoen
2008-10-02 8:31 ` Pierre Ossman
2008-09-23 17:40 ` [PATCH 2/4] atmel-mci: Platform code for supporting " Pierre Ossman
2008-09-23 18:02 ` Haavard Skinnemoen
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=20080925090556.44940c89@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®