On Thu, 2010-06-03 at 21:42 -0700, Philip Langdale wrote:
On Thu, 03 Jun 2010 20:35:31 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
On Thu, 2010-06-03 at 10:05 -0700, Philip Langdale wrote:
On Thu, 3 Jun 2010 09:39:14 -0700
Philip Langdale phil...@overt.org wrote:
On Fri, 04 Jun 2010 13:07:28 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
On this subject:
1) Would it make sense to have the hard-coded caps reflect the full
set of caps you see on the sdhci side?
This would be ugly cause two driver instances would have to talk one
with
On Thu, 2010-06-03 at 09:11 -0700, Philip Langdale wrote:
On Thu, 3 Jun 2010 04:16:27 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
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.
Old way of disabling
On Thu, 03 Jun 2010 19:31:49 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
On Thu, 2010-06-03 at 09:11 -0700, Philip Langdale wrote:
On Thu, 3 Jun 2010 04:16:27 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
The current way of disabling it is not well tested by vendor
On Thu, 3 Jun 2010 04:16:27 +0300
Maxim Levitsky maximlevit...@gmail.com wrote:
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.
Old way of disabling is still supported by
continuing to use CONFIG_MMC_RICOH_MMC.
On Thu, 3 Jun 2010 09:39:14 -0700
Philip Langdale phil...@overt.org wrote:
Have you been able to establish if 4bit and high-speed operations
work correctly through the MMC controller? I note that you didn't
set SDHCI_CAN_DO_HISPD.
Didn't test that yet, will do.
I hope my MMCPlus
