On Fri, 30 Jul 2010 19:28:44 +0200
Linus Walleij wrote:
> 2010/6/22 Rabin Vincent :
>
> > From: Hanumath Prasad
> >
> > A non-zero value of SEC_COUNT does not indicate that the card is sector
> > addressed. __According to the MMC specification, cards with a density
> > greater than 2GiB are sec
The patch titled
mmc-fix-all-hangs-related-to-mmc-sd-card-insert-removal-during-suspend-resume-update
has been added to the -mm tree. Its filename is
mmc-fix-all-hangs-related-to-mmc-sd-card-insert-removal-during-suspend-resume-update.patch
Before you just go and hit "reply", please:
Hi Andreas
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Andreas Feuersinger
> Sent: Thursday, July 29, 2010 5:46 AM
> To: libertas-...@lists.infradead.org; linux-mmc@vger.kernel.org; linux-
> wirel...@vger.kernel.org
2.6.34-stable review patch. If anyone has any objections, please let us know.
--
From: Daniel Mack
commit 8a64c0f6b7ec7f758c4ef445e49f479e27fa2236 upstream.
When operating in 1-bit mode, SDAT1 is used as dedicated interrupt line.
However, the 8686 will only drive this line whe
2010/6/22 Rabin Vincent :
> From: Hanumath Prasad
>
> A non-zero value of SEC_COUNT does not indicate that the card is sector
> addressed. According to the MMC specification, cards with a density
> greater than 2GiB are sector addressed.
What's happening with this beauty? Andrew would you mind
2.6.33-stable review patch. If anyone has any objections, please let us know.
--
From: Daniel Mack
commit 8a64c0f6b7ec7f758c4ef445e49f479e27fa2236 upstream.
When operating in 1-bit mode, SDAT1 is used as dedicated interrupt line.
However, the 8686 will only drive this line whe
2.6.32-stable review patch. If anyone has any objections, please let us know.
--
From: Daniel Mack
commit 8a64c0f6b7ec7f758c4ef445e49f479e27fa2236 upstream.
When operating in 1-bit mode, SDAT1 is used as dedicated interrupt line.
However, the 8686 will only drive this line whe
Hello!
I wonder if somebody's had some spare moment to review this patch.
Welcome advice and feedback as usual
Many thanks in advance.
Best Regards,
Giuseppe
> -Original Message-
> From: Giuseppe CAVALLARO [mailto:peppe.cavall...@st.com]
> Sent: Thursday, July 29, 2010 10:31 AM
> To: lin
If you don't use CONFIG_MMC_UNSAFE_RESUME, as soon as you attempt to
suspend, the card will be removed, therefore this patch doesn't change
the behavior of this option.
However the removal will be done by pm notifier, which runs while
userspace is still not frozen and thus can freely use del_gendi
The current way of disabling it is not well tested by vendor
and has all kinds of bugs that show up on resume from ram/disk.
A very good example is a dead SDHCI controller.
Old way of disabling is still supported by
continuing to use CONFIG_MMC_RICOH_MMC.
Based on 'http://list.drzeus.cx/pipermail
Hi,
Here is updated version of fixes I created for mmc subsystem.
First patch is unchanged, and I can say is very well tested.
The second patch that fixes nasty hang that happens if you have MMC card in
reader
during suspend.
I updated it to address corner issues that I was told about.
Consider
On Wed, Jul 28, 2010 at 05:43:00PM +0800, Zang Roy-R61911 wrote:
[...]
> > > + /* The default value of DMAS bits of Protocol Control
> > Register is not
> > > + * correct. clear these two bits to use simple DMA */
> > > +#define ESDHCI_CTRL_DMAS_MASK 0xFCFF
> > > + if (host->quirks
On Fri, Jul 30, 2010 at 11:52:57AM +0800, Roy Zang wrote:
> P4080 ESDHC controller does not support 1.8V and 3.0V voltage. but the
> host controller capabilities register wrongly set the bits.
> This patch adds the workaround to correct the weird voltage setting bits.
>
> Signed-off-by: Roy Zang
13 matches
Mail list logo
