Re: RESEND:[PATCH V3] sdhci: only reprogram retuning timer when flag is set

2014-03-19 Thread Aaron Lu
On 02/22/2014 03:59 AM, Arend van Spriel wrote: > When the host->tuning_count is zero it means that the > retuning is disabled. This is checked on the first > run of sdhci_execute_tuning() by the if statement below: > > if (!(host->flags & SDHCI_NEEDS_RETUNING) && host->tuning_count && >

Re: mvsdio: unhandled interrupt, mmc writes queuing up

2014-03-19 Thread Nicolas Pitre
On Wed, 19 Mar 2014, Bruno Prémont wrote: > Hi, > > Since upgrading my Sheevaplug from 3.7.2 to 3.13.6 (FDT) I'm seeing > mvsdio f109.mvsdio: unhandled interrupt status=0x8810 en=0x pio=0 > at varied timings. It has been many years since I've looked at the code for this driver. I'm t

mvsdio: unhandled interrupt, mmc writes queuing up

2014-03-19 Thread Bruno Prémont
Hi, Since upgrading my Sheevaplug from 3.7.2 to 3.13.6 (FDT) I'm seeing mvsdio f109.mvsdio: unhandled interrupt status=0x8810 en=0x pio=0 at varied timings. In addition to that, kernel seems excessively busy doing writeback via workqueue (without success?): [14909.275124] kworker/u2:2

Re: [PATCH] mmc: sdhci-bcm-kona: Fix locking in sdhci_bcm_kona_sd_card_emulate()

2014-03-19 Thread Christian Daudt
On Wed, Mar 5, 2014 at 8:25 PM, Markus Mayer wrote: > Since sdhci_bcm_kona_sd_card_emulate() can be called from interrupt > context, we must use a spinlock instead of a mutex. This change > essentially restores the way things worked before the change to > mutexes in http://www.spinics.net/lists/li