Searched hist:a626c8d418d5fd1f8429294e7efe3fa2e4ca90fe (Results 1 – 2 of 2) sorted by relevance
| /openbmc/u-boot/include/ |
| H A D | mmc.h | diff a626c8d418d5fd1f8429294e7efe3fa2e4ca90fe Thu Mar 19 07:44:03 CDT 2015 Andrew Gabbasov <andrew_gabbasov@mentor.com> 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>
|
| /openbmc/u-boot/drivers/mmc/ |
| H A D | mmc.c | diff a626c8d418d5fd1f8429294e7efe3fa2e4ca90fe Thu Mar 19 07:44:03 CDT 2015 Andrew Gabbasov <andrew_gabbasov@mentor.com> 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>
|