public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: kdorfman@codeaurora.org
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Hanumath Prasad <hanumath.prasad@stericsson.com>,
	Per FORLIN <per.forlin@stericsson.com>,
	Sebastian Rasmussen <sebras@gmail.com>,
	"Dong, Chuanxiao" <chuanxiao.dong@intel.com>,
	"svenkatr@ti.com" <svenkatr@ti.com>,
	Saugata Das <saugata.das@linaro.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v8] mmc: support BKOPS feature for eMMC
Date: Fri, 11 May 2012 14:38:26 +0900	[thread overview]
Message-ID: <4FACA5D2.3050706@samsung.com> (raw)
In-Reply-To: <aa38953dd272014cd1c4d014ce9d15bd.squirrel@www.codeaurora.org>

Hi Konstantin.

On 05/10/2012 11:46 PM, kdorfman@codeaurora.org wrote:

> Hi Jaehoon,
> I see 2 issues with new patch:
> 1. New code starts BKOPS always with waiting for BUSY. (see comment below
> in the code)
> 2. Runtime suspend (mmc_suspend_host) do not checks that BKOPS is in
> progress,
> this means, that CMD5 (slee) will fail.

You're right. it needs to check in progress.
I will add them.

> 
> 
> In your previous patch (v7) was code:
> 
> -	cmd.flags = MMC_RSP_SPI_R1B | MMC_RSP_R1B | MMC_CMD_AC;
> +	cmd.flags = MMC_CMD_AC;
> +	if (index == EXT_CSD_BKOPS_START &&
> +	    card->ext_csd.raw_bkops_status < EXT_CSD_BKOPS_LEVEL_2)
> +		cmd.flags |= MMC_RSP_SPI_R1 | MMC_RSP_R1;
> +	else
> +		cmd.flags |= MMC_RSP_SPI_R1B | MMC_RSP_R1B;
> 
> When level of raw_bkops_status is not critical, the host controller flags
> used
> without waiting for BUSY line release. This means, that mmc queue thread
> will continue
> to fetch requests while BKOPS still running on the card.
> Without this code, BKOPS will always be blocking till BKOPS done and using
> HPI for interrupt BKOPS on
> new request is not need.
> Why you removed this code?

You're right. it's my mistake. Actually i modified to use with __mmc_switch().
As I remember, maybe you mentioned this point. right?
So i tried to use based on your review. it's missing in this patch.

Thank you for your comment. any other comments?
If you have others, let me know, plz.

Best Regards,
Jaehoon Chung

> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  reply	other threads:[~2012-05-11  5:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 13:37 [PATCH v8] mmc: support BKOPS feature for eMMC Jaehoon Chung
2012-05-10 14:46 ` kdorfman
2012-05-11  5:38   ` Jaehoon Chung [this message]
2012-05-11 10:06     ` kdorfman
2012-05-11 11:40 ` S, Venkatraman
2012-05-14  2:44   ` Jaehoon Chung
2012-05-15  2:45     ` Jaehoon Chung
2012-05-11 12:39 ` Subhash Jadavani
2012-05-14  2:58   ` Jaehoon Chung
2012-05-14  9:55     ` Subhash Jadavani
2012-05-15  2:48       ` Jaehoon Chung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FACA5D2.3050706@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=adrian.hunter@intel.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=hanumath.prasad@stericsson.com \
    --cc=kdorfman@codeaurora.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=saugata.das@linaro.org \
    --cc=sebras@gmail.com \
    --cc=svenkatr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox