u-boot.git/cmd/mmc.c, branch v2018.03 Unnamed repository; edit this file 'description' to name the repository. mmc: remove hc_wp_grp_size from struct mmc if not needed 2018-01-12T09:11:24+00:00 Jean-Jacques Hiblot jjhiblot@ti.com 2018-01-04T14:23:36+00:00 b7a6e2c9c396c35596f467f5187da937306ddeb8 hc_wp_grp_size is needed only if hardware partitionning is used. On ARM removing it saves about 30 bytes of code space. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> 
hc_wp_grp_size is needed only if hardware partitionning is used.
On ARM removing it saves about 30 bytes of code space.

Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
mmc: compile out erase and write mmc commands if write operations are not enabled 2018-01-12T09:11:24+00:00 Jean-Jacques Hiblot jjhiblot@ti.com 2018-01-04T14:23:34+00:00 e6fa5a546154a42c4f6662cd8890c238207ce21a Also remove erase_grp_size and write_bl_len from struct mmc as they are not used anymore. On ARM, removing them saves about 100 bytes of code space in SPL. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> 
Also remove erase_grp_size and write_bl_len from struct mmc as they are
not used anymore. On ARM, removing them saves about 100 bytes of code
space in SPL.

Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
mmc: make optional the support for eMMC hardware partitioning 2018-01-12T09:11:04+00:00 Jean-Jacques Hiblot jjhiblot@ti.com 2017-11-30T16:44:02+00:00 cf17789e078fd23b95ee86ffc441e98709c2d063 Not all boards have an eMMC and not all users have a need for this. Allow to compile it out. By default it is still included. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> 
Not all boards have an eMMC and not all users have a need for this.
Allow to compile it out. By default it is still included.

Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
mmc: dump card and host capabilities if debug is enabled 2018-01-12T09:11:04+00:00 Jean-Jacques Hiblot jjhiblot@ti.com 2017-11-30T16:43:54+00:00 52d241dfba7c3903a3a7d97fe6cb815c9ed379d6 This is a useful information while debugging the initialization process or performance issues. Also dump this information with the other mmc info if the verbose option is selected Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> 
This is a useful information while debugging the initialization process or
performance issues.
Also dump this information with the other mmc info if the verbose option
is selected

Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
cmd: mmc: display the mode name and current bus speed in the mmc info 2018-01-12T09:11:04+00:00 Jean-Jacques Hiblot jjhiblot@ti.com 2017-09-21T14:29:56+00:00 7a96ec74592847cd7bf5664cb72996500ebde92b Display the mode name when the user execute 'mmc info'. Also instead of displaying tran_speed, display the actual bus speed. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Display the mode name when the user execute 'mmc info'. Also instead of
displaying tran_speed, display the actual bus speed.

Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
blk: Remove various places that do flush cache after read 2017-09-15T12:05:10+00:00 Bin Meng bmeng.cn@gmail.com 2017-09-13T02:00:23+00:00 723b43daec7ee2ddb600cfcb9b0253d4a71c3915 All these places seem to inherit the codes from the MMC driver where a FIXME was put in the comment. However the correct operation after read should be cache invalidate, not flush. The underlying drivers should be responsible for the cache operation. Remove these codes completely. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Stefan Roese <sr@denx.de> Reviewed-by: York Sun <york.sun@nxp.com> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com> Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: York Sun <york.sun@nxp.com> 
All these places seem to inherit the codes from the MMC driver where
a FIXME was put in the comment. However the correct operation after
read should be cache invalidate, not flush.

The underlying drivers should be responsible for the cache operation.
Remove these codes completely.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: York Sun <york.sun@nxp.com>
Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: York Sun <york.sun@nxp.com>
cmd: mmc: add mmc partconf read capability 2017-08-17T08:00:11+00:00 Angelo Dureghello angelo@sysam.it 2017-08-01T12:27:10+00:00 bdb6099666933491ce393e52132e05604da91b1a This patch allows to show the EXT_CSD[179] partition_config register info, just by specifying the dev param: U-Boot> mmc partconf 0 EXT_CSD[179], PARTITION_CONFIG: BOOT_ACK: 0x0 BOOT_PARTITION_ENABLE: 0x0 PARTITION_ACCESS: 0x0 Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Anatolij Gustschin <agust@denx.de> 
This patch allows to show the EXT_CSD[179] partition_config
register info, just by specifying the dev param:

  U-Boot> mmc partconf 0
  EXT_CSD[179], PARTITION_CONFIG:
  BOOT_ACK: 0x0
  BOOT_PARTITION_ENABLE: 0x0
  PARTITION_ACCESS: 0x0

Signed-off-by: Angelo Dureghello <angelo@sysam.it>
Signed-off-by: Anatolij Gustschin <agust@denx.de>
mmc: use new hwpart API when CONFIG_BLK enabled 2017-07-19T10:13:59+00:00 Kever Yang kever.yang@rock-chips.com 2017-06-08T01:20:03+00:00 4dc80c8732f0fe971669a8440abd78c42bd1367c When CONFIG_BLK is enabled, the hwpart id is different with legacy interface, update it to kame driver work with CONFIG_BLK. Signed-off-by: Kever Yang <kever.yang@rock-chips.com> Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com> 
When CONFIG_BLK is enabled, the hwpart id is different with legacy
interface, update it to kame driver work with CONFIG_BLK.

Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
cmd_mmc: fix arg parsing for setdsr subcmd 2017-04-12T16:46:38+00:00 Markus Niebel Markus.Niebel@tq-group.com 2017-02-03T14:26:36+00:00 84c1dfe42f08570b8a62f64ab3e45d1b62783b07 The handler do_setdsr receives only the dsr parameter, the action is parsed before. Error was introduced when restructuring the mmc command implementation in commit 1fd93c6e7d8a1e4d6261058cefab11b875ded252. Reported-by: Michael Krummsdorf <Michael.Krummsdorf@tq-group.com> Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com> 
The handler do_setdsr receives only the dsr parameter,
the action is parsed before.

Error was introduced when restructuring the mmc command
implementation in commit 1fd93c6e7d8a1e4d6261058cefab11b875ded252.

Reported-by: Michael Krummsdorf <Michael.Krummsdorf@tq-group.com>
Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com>
mmc: add bkops-enable command 2016-12-01T02:09:44+00:00 Tomas Melin tomas.melin@vaisala.com 2016-11-25T09:01:03+00:00 cd3d48807dfb64f521fcbc30034d4e921d842a5b Add new command that provides possibility to enable the background operations handshake functionality (BKOPS_EN, EXT_CSD byte [163]) on eMMC devices. This is an optional feature of eMMCs, the setting is write-once. The command must be explicitly taken into use with CONFIG_CMD_BKOPS_ENABLE. Signed-off-by: Tomas Melin <tomas.melin@vaisala.com> 
Add new command that provides possibility to enable the
background operations handshake functionality
(BKOPS_EN, EXT_CSD byte [163]) on eMMC devices.

This is an optional feature of eMMCs, the setting is write-once.
The command must be explicitly taken into use with
CONFIG_CMD_BKOPS_ENABLE.

Signed-off-by: Tomas Melin <tomas.melin@vaisala.com>