[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <496CA304.9000802@nokia.com>
Date: Tue, 13 Jan 2009 16:19:48 +0200
From: Adrian Hunter <ext-adrian.hunter@...ia.com>
To: Pierre Ossman <drzeus-mmc@...eus.cx>
CC: Tony Lindgren <tony@...mide.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
lkml <linux-kernel@...r.kernel.org>,
linux-omap Mailing List <linux-omap@...r.kernel.org>,
"Lavinen Jarkko (Nokia-M/Helsinki)" <jarkko.lavinen@...ia.com>,
Madhusudhan Chikkature <madhu.cr@...com>
Subject: Re: [PATCH 2/2] OMAP: HSMMC: Fix response type for busy after response
Pierre Ossman wrote:
> On Tue, 13 Jan 2009 15:38:41 +0200
> Adrian Hunter <ext-adrian.hunter@...ia.com> wrote:
>
>> This also fixes the hidden problem that the controller
>> was turning off the clock to the card while the card
>> was busy - the clock was then switched on for the
>> duration of each Send Status command used for polling,
>> which is why writes did not lock up altogether.
>> i.e. really dysfunctional.
>
> Does the driver only keep the clock running as long as there is an
> ongoing request? That kind of policy should really be handled in the
> core where we have more information and can control it better. E.g. some
> cards need the clock to finish up internal housekeeping so we need to
> delay things for those.
>
> Rgds
Unfortunately it seems to be something the controller does by itself,
beyond the control of the driver. Added Jarkko Lavinen and
Madhusudhan Chikkature to CC, maybe they can correct me.
If it obeys the standard, it should give an additional 8 clock cycles.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists