summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorAndrew Gabbasov <andrew_gabbasov@mentor.com>2015-03-19 07:44:03 -0500
committerPantelis Antoniou <pantelis.antoniou@konsulko.com>2015-05-05 11:53:52 +0300
commita626c8d418d5fd1f8429294e7efe3fa2e4ca90fe (patch)
treeedf39f78ca6b7028f34f041373fbda83840ee6c3 /include
parent3f2da751beb84861ba0a999aaea09e73f578022a (diff)
downloadtalos-obmc-uboot-a626c8d418d5fd1f8429294e7efe3fa2e4ca90fe.tar.gz
talos-obmc-uboot-a626c8d418d5fd1f8429294e7efe3fa2e4ca90fe.zip
mmc: Avoid extra duplicate entry in mmc device structure
The 'op_cond_response' field in mmc structure contains the response from the last SEND_OP_COND MMC command while making iterational polling of the card. Later it is copied to 'ocr' field, designed to contain the OCR register value, which is actually the same response from the same command. So, these fields have actually the same data, just in different time periods. It's easier to use the same 'ocr' field in both cases at once, without temporary using of the 'op_cond_response' field. Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
Diffstat (limited to 'include')
-rw-r--r--include/mmc.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/mmc.h b/include/mmc.h
index a251531aed..644e3fa1e1 100644
--- a/include/mmc.h
+++ b/include/mmc.h
@@ -356,7 +356,6 @@ struct mmc {
char op_cond_pending; /* 1 if we are waiting on an op_cond command */
char init_in_progress; /* 1 if we have done mmc_start_init() */
char preinit; /* start init as early as possible */
- uint op_cond_response; /* the response byte from the last op_cond */
int ddr_mode;
};
OpenPOWER on IntegriCloud