All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Simkowiak <derek@webtuner.tv>
To: Avi Shchislowski <Avi.Shchislowski@sandisk.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"'cjb@laptop.org'" <cjb@laptop.org>
Cc: Alex Lemberg <Alex.Lemberg@sandisk.com>,
	Gwendal Grignou <gwendal@google.com>
Subject: Re: [PATCH 0/3]mmc: Support-FFU-for-eMMC-v5.0
Date: Thu, 6 Nov 2014 11:12:03 -0800	[thread overview]
Message-ID: <545BC803.1040206@webtuner.tv> (raw)
In-Reply-To: <FDD07FEB422EF948A392FDC201AEEAE64F6AFCDA@SACMBXIP02.sdcorp.global.sandisk.com>

Regarding v5.0: a while ago, Romain wrote a small eMMC 5.0 patch that 
Ulf ack'd:

http://comments.gmane.org/gmane.linux.kernel.mmc/23795

But this patch got lost and was never merged.  I wanted to re-submit on 
Romain's behalf but haven't been able to find the time.  Perhaps you 
could take this task?

I have verified that this patch is necessary for my Jedec 5.0 hardware.


Thanks,
Derek

On 11/06/2014 07:41 AM, Avi Shchislowski wrote:
> The Field Firmware Update (FFU) feature is new for eMMC 5.0 spec (Jedec:
>   JESD84-B50.pdf)
>     
>   http://www.jedec.org/standards-documents/technology-focus-areas/flash-
>   memory-ssds-ufs-emmc/e-mmc
>   
>   *New ioctl has been add:
>   * [Alex Lemberg] "MMC_FFU_INVOKE - transfer the new Firmware data from user spac[Alex Lemberg]space
>   	to the eMMC deivce and install the new image[Alex Lemberg] firmware.
> * This solution allows to:
> - Complete eMMC 5.0 FFU procedure as an atomic operation, without being interrupted by other IO requests
> - Not limited Firmware data size. Using Multiple Write operations.
> - Support of both EXT_CSD_MODE_OPERATION_CODES modes [Alex Lemberg]
> * The solution is using "udev" device manager to transfer FW data from user space to eMMC driver [Alex Lemberg]
> * Pre-existing functions from mmc_test were used in this solution.
>
> Signed-off-by: Avi Shchislowski <avi.shchislowski@sandisk.com>
> Signed-off-by: Alex Lemberg <alex.lemberg@sandisk.com>
>
> Avi Shchislowski (3):
>    mmc: add eMMC5.0 ffu ext_csd fields
>    mmc: Support FFU for eMMC v5.0 1/2
>    mmc: Support FFU for eMMC v5.0 2/2
>
>   drivers/mmc/card/Kconfig    |    8 +
>   drivers/mmc/card/block.c    |    5 +
>   drivers/mmc/card/mmc_test.c |   97 +--------
>   drivers/mmc/core/Makefile   |    1 +
>   drivers/mmc/core/core.c     |  128 ++++++++++++
>   drivers/mmc/core/mmc.c      |    9 +
>   drivers/mmc/core/mmc_ffu.c  |  487 +++++++++++++++++++++++++++++++++++++++++++
>   include/linux/mmc/card.h    |    2 +
>   include/linux/mmc/core.h    |   30 +++
>   include/linux/mmc/mmc.h     |    9 +
>   10 files changed, 690 insertions(+), 86 deletions(-)  create mode 100644 drivers/mmc/core/mmc_ffu.c
>
> --
> 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:[~2014-11-06 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:41 [PATCH 0/3]mmc: Support-FFU-for-eMMC-v5.0 Avi Shchislowski
2014-11-06 19:12 ` Derek Simkowiak [this message]

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=545BC803.1040206@webtuner.tv \
    --to=derek@webtuner.tv \
    --cc=Alex.Lemberg@sandisk.com \
    --cc=Avi.Shchislowski@sandisk.com \
    --cc=cjb@laptop.org \
    --cc=gwendal@google.com \
    --cc=linux-mmc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.