Re: Hynix eMMC RPMB: Access timeouts, broken?

2013-07-02 Thread Krishna Konda
On 6/4/2013 4:32 AM, Dirk Behme wrote: Using some recent Hynix eMMC devices [1] on our Freescale i.MX6 boards we get harmless (?), but annoying access timeouts accessing the RPMB partition: mmcblk1rpmb: error -110 transferring data, sector 0, nr 32, cmd response 0x900, card status 0xb00 mmcblk1

Re: [PATCH] mmc: core: Fixup Oops for SDIO shutdown

2013-07-02 Thread Stephen Warren
On 07/02/2013 04:53 AM, Ulf Hansson wrote: > Commit "mmc: core: Handle card shutdown from mmc_bus" introduced an > Oops in the shutdown sequence for SDIO. > > The drv pointer, does not exist for SDIO since the probing of the SDIO > card from the mmc_bus perspective is expected to fail by returning

Re: [PATCH v2] mmc: sh_mmcif: add support for Device Tree DMA bindings

2013-07-02 Thread Guennadi Liakhovetski
Hi Chris What's the plan about this patch? Do you think you'd be able to push it for 3.11 or rather 3.12? Thanks Guennadi On Mon, 24 Jun 2013, Guennadi Liakhovetski wrote: > To use DMA in the Device Tree case the driver has to be modified > to use suitable API to obtain DMA channels. > > Sign

Re: [PATCH v2] Add basic support for password protected (locked) SD cards.

2013-07-02 Thread Peter Turczak
Thank you, Jae hoon, for the heads up! You are right, I missed a few spots in the first run. This version fixes the mistakes from last time. Adds support for sd cards that are locked by a password and rereading an already enumerated card. This fixes compatibility issues with password locked cards

Re: [PATCH] mmc: core: Fixup Oops for SDIO shutdown

2013-07-02 Thread Tuomas Tynkkynen
On 07/02/2013 01:53 PM, Ulf Hansson wrote: > Commit "mmc: core: Handle card shutdown from mmc_bus" introduced an > Oops in the shutdown sequence for SDIO. > > The drv pointer, does not exist for SDIO since the probing of the SDIO > card from the mmc_bus perspective is expected to fail by returning

Re: [PATCH] mmc: core: Fixup Oops for SDIO shutdown

2013-07-02 Thread Jaehoon Chung
Acked-by: Jaehoon Chung Best Regards, Jaehoon Chung On 07/02/2013 07:53 PM, Ulf Hansson wrote: > Commit "mmc: core: Handle card shutdown from mmc_bus" introduced an > Oops in the shutdown sequence for SDIO. > > The drv pointer, does not exist for SDIO since the probing of the SDIO > card from t

Re: Oops on linux-next during reboot, possibly related to "mmc: core: Handle card shutdown from mmc_bus"

2013-07-02 Thread Ulf Hansson
On 1 July 2013 13:40, Tuomas Tynkkynen wrote: > Hi, > > On next-20130628 I get the following Oops during reboot: > [ 89.814921] Unable to handle kernel NULL pointer dereference at virtual > address 004c > [ 89.824208] pgd = ecd54000 > [ 89.827276] [004c] *pgd= > [ 89.83134

[PATCH] mmc: core: Fixup Oops for SDIO shutdown

2013-07-02 Thread Ulf Hansson
Commit "mmc: core: Handle card shutdown from mmc_bus" introduced an Oops in the shutdown sequence for SDIO. The drv pointer, does not exist for SDIO since the probing of the SDIO card from the mmc_bus perspective is expected to fail by returning -ENODEV. This patch adds the proper check for the p

Re: Crash during reboot due to 7628774 "mmc: core: Handle card shutdown from mmc_bus"

2013-07-02 Thread Ulf Hansson
On 1 July 2013 22:32, Stephen Warren wrote: > It looks like commit 7628774 "mmc: core: Handle card shutdown from > mmc_bus" causes a crash during "reboot" at least on Tegra platforms. The > issue appears to be in: > >> static void mmc_bus_shutdown(struct device *dev) >> { >> struct mmc_drive

Re: Oops on linux-next during reboot, possibly related to "mmc: core: Handle card shutdown from mmc_bus"

2013-07-02 Thread Jaehoon Chung
Hi Tuomas, It seems to produce this problem when wifi is enabled. In case of WiFi, used the sdio_bus_register in sdio_bus.c. Then i think right that "shutdown callback function" is existed in WiFi driver. And need to use the sdio_bus_shutdown, not mmc_bus_shutdown. sdio is used sdio_driver and m