Skip to content

GitLab

Switch branch/tag
  1. 20 Mar, 2017 2 commits
  3. 16 Mar, 2017 1 commit
  5. 01 Sep, 2016 1 commit
  7. 29 Aug, 2016 4 commits
  9. 23 Jun, 2016 1 commit
  11. 07 Jun, 2016 1 commit
  13. 11 May, 2016 1 commit
  15. 08 Mar, 2016 1 commit
    • Avi Shchislowski's avatar
      mmc_utils: add ffu support · 89cd01ed
      Avi Shchislowski authored 
      

Adding support for field firmware update over multiple command ioctl.
As multiple command ioctl is supported only from kernel 4.4, this patch
should be used against kernel 4.4 and above.

Known issues:
- There is no support for Multiple Block write commands (CMD25) in existing
  IOCTL implementation
- In case MODE_OPERATION_CODES field is not supported by the device
  manual reset of the device/platform is required.
  The reset issue discussed in another email thread - " [RFC 0/6] mmc:
  Field Firmware Update"
Signed-off-by: default avatarYaniv Agman <yaniv.agman@sandisk.com>
Signed-off-by: default avatarAvi Shchislowski <avi.shchislowski@sandisk.com>
Signed-off-by: default avatarChris Ball <chris@printf.net>
      89cd01ed
  17. 18 Nov, 2015 1 commit
  19. 01 May, 2015 4 commits
  21. 12 Aug, 2014 1 commit
    • Roman Peniaev's avatar
      mmc-utils: RPMB: add support for 4 rpmb operations · c6cb053e
      Roman Peniaev authored 
      

mmc rpmb write-key <rpmb device> <key file>
  Program authentication key which is 32 bytes length and stored in the specified file.
  Also you can specify '-' instead of key file path and utility will read the key from stdin.
  BEWARE: key can be programmed only once!
  Example:
    $ echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH | mmc rpmb write-key /dev/mmcblk0rpmb -

mmc rpmb read-counter <rpmb device>
  Counter value for the <rpmb device> will be read to stdout.

mmc rpmb read-block <rpmb device> <address> <blocks count> <output file> [key file]
  Blocks of 256 bytes will be read from <rpmb device> to output file or stdout if '-'
  is specified instead of regular path. If key is specified - read data will be verified.
  Instead of regular path you can specify '-' and key will be read from stdin.
  Example:
    $ echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH | \
        mmc rpmb read-block /dev/mmcblk0rpmb 0x02 2 /tmp/block -
  or read the block without verification
    $ mmc rpmb read-block /dev/mmcblk0rpmb 0x02 2 /tmp/block

mmc rpmb write-block <rpmb device> <address> <256 byte data file> <key file>
  Block of 256 bytes will be written from data file to <rpmb device>.
  Also you can specify '-' instead of key file path or data file and utility will read the
  data from stdin.
  Example:
    $ (awk 'BEGIN {while (c++<256) printf "a"}' | echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH) | \
      mmc rpmb write-block /dev/mmcblk0rpmb 0x02 - -
Signed-off-by: default avatarRoman Pen <r.peniaev@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Cc: Ben Gardiner <bengardiner@nanometrics.ca>,
Signed-off-by: default avatarChris Ball <chris@printf.net>
      c6cb053e
  23. 26 Sep, 2013 5 commits
  25. 27 Jun, 2013 9 commits
  27. 26 May, 2013 1 commit
  29. 19 Oct, 2012 1 commit
  31. 21 Sep, 2012 1 commit
  33. 17 May, 2012 3 commits
  35. 20 Feb, 2012 2 commits
    • Chris Ball's avatar
      Rename extcsd read/write to writeprotect get/set · b9c7a17f
      Chris Ball authored 
      

This leaves "extcsd read" pointing to Giuseppe's code.  Also, abstract
out the writeprotect code so that there's only one shared implementation
in print_writeprotect_status(), used by both "extcsd read" and
"writeprotect get".
Signed-off-by: default avatarChris Ball <cjb@laptop.org>
      b9c7a17f
    • Giuseppe CAVALLARO's avatar
      improve the parsing of the EXT_CSD registers · a5bf4a20
      Giuseppe CAVALLARO authored 
      

This patch enhances the debug information reported
for the mmc card by parsing the extended CSD registers
obviously according to all the current specifications.

I have no HW to test eMMC 4.5 at this moment. In any case,
the patch supports JEDEC Standard No. 84-B45.
No issues on JESD84-A441 and older specs raised on my side.

This patch indeed want to start providing a full parsing
of the all EXT_CSD registers in the following layout:

Name [FIELD: <value>]

Voluntarily, I added the FIELD because it can actually help on
searching though the SPEC in case of doubts.
In fact, in this stage, not all the register bits are yet parsed.
Currently this has been done for a small subset of registers
(e.g. 173, 160 ...) where IMO it's quite useful for an end-user
to get some details. I do hope this will be improved in the near
feature (also for write operations).

P.S. The original patch posted time ago for the Kernel has been
reviewed-by Sebastian Rasmussen, acked-by: Linus Walleij and reported
by Youssef Tiki.
Signed-off-by: default avatarGiuseppe Cavallaro <peppe.cavallaro@st.com>
Signed-off-by: default avatarChris Ball <cjb@laptop.org>
      a5bf4a20