Re: [RFC] mmc: Do no export the rpmb as a partition

Sebastian Andrzej Siewior bigeasy at linutronix.de writes: So my question is basically, is it okay to read from this partition? You can read from RPMB only after sending RPMB command (25) according to RPMB protocol. So the RPMB is not first class partition. -- To unsubscribe from this list:

Re: [PATCH v4 0/3] about data busy

Hello Addy, On Sat, Feb 14, 2015 at 7:17 AM, Addy Ke addy...@rock-chips.com wrote: patch 1: This patch can fix bug that controller is still data busy after reset all blocks. After this patch, I still get data busy in set_ios(). patch 2: This patch fix bug 'Timeout sending

[PATCH/RFC] mmc: sh_mmcif: Add exclusion between cmd and interrupt

From: Kouichi Tomita kouichi.tomita...@renesas.com A command end interrupt should not be processed between command issue and setting of wait_for flag. It expects already the flag to be set. Therefore the exclusive control was added. Signed-off-by: Kouichi Tomita kouichi.tomita...@renesas.com

[PATCH/RFC] mmc: sh_mmcif: Move dev_err() of mmcif_timeout_work()

From: Kouichi Tomita kouichi.tomita...@renesas.com If interruption of command already occurred, mrq pointer in dev_err() would refer to NULL, because the host-state is changed to STATE_IDLE and mrq pointer is changed to NULL by interrupt handler. Therefore dev_err is moved after checking

[PATCH] mmc: sirf: update sdhci_sirf_execute_tuning procedure

From: weijun yang york.y...@csr.com For the original tuning code, delay value is set to SD Bus Clock Delay Register (SD_CLK_DELAY_SETTING) as (val | (Val 7) | (val 16)), which means CLK_DELAY_IN1, CLK_DELAY_IN2 and CLK_DELAY_OUT are the same and with 128 steps. This is doubtful. In CSR design

Re: [PATCH/RFC] mmc: sh_mmcif: Add exclusion between cmd and interrupt

Hello. On 02/15/2015 05:46 PM, Yoshihiro Kaneko wrote: From: Kouichi Tomita kouichi.tomita...@renesas.com A command end interrupt should not be processed between command issue and setting of wait_for flag. It expects already the flag to be set. Therefore the exclusive control was added.

Re: [PATCH v4 1/3] mmc: dw_mmc: update clock after host reach a stable voltage

Hi Addy, On Sat, Feb 14, 2015 at 11:47 AM, Addy Ke addy...@rock-chips.com wrote: As show in mmc_power_up(), in MMC_POWER_UP state, the voltage isn't stable and we may get 'data busy' which can't be cleaned by resetting all blocks. So we should not send command to update clock in this state.

Re: [PATCH v4 0/3] about data busy

On 02/15/2015 08:41 PM, Javier Martinez Canillas wrote: Hello Addy, On Sat, Feb 14, 2015 at 7:17 AM, Addy Ke addy...@rock-chips.com wrote: patch 1: This patch can fix bug that controller is still data busy after reset all blocks. After this patch, I still get data busy in