[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0907310853470.4541@axis700.grange>
Date: Fri, 31 Jul 2009 08:55:30 +0200 (CEST)
From: Guennadi Liakhovetski <g.liakhovetski@....de>
To: Ian Molton <ian@...menth.co.uk>
cc: pHilipp Zabel <philipp.zabel@...il.com>,
Paul Mundt <lethal@...ux-sh.org>,
Magnus Damm <magnus.damm@...il.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
linux-kernel@...r.kernel.org, Pierre Ossman <drzeus@...eus.cx>,
Magnus Damm <damm@...nsource.se>
Subject: Re: MMC: Make the configuration memory resource optional
On Thu, 30 Jul 2009, Ian Molton wrote:
> Guennadi Liakhovetski wrote:
>
> > While you're at it, please, consider swapping the two lines in
> > tmio_mmc_probe():
> >
> > - tmio_mmc_clk_stop(host);
> > reset(host);
> > + tmio_mmc_clk_stop(host);
> >
> > Otherwise, I think, reset causes problems trying to access the controller
> > with disabled clock. At least this is needed on SuperH.
>
> Interesting. I'll see what the result of this is on TMIO - This sequence was
> garnered from the WinCE driver for the chip.
>
> I cant see _why_ this should be a problem, as this disables the card clock,
> not HCLK. Could you debug further in tmio_mmc_clk_stop() please and see if
> reordering only one of the two IO accesses cures this?
Not sure I understood the "reordering only one of the two IO accesses"
correctly, but I swapped the two sd_ctrl_write16() calls in
tmio_mmc_clk_stop() and no, it didn't cure the problem.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
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