mmc-dev-attrs.txt 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. SD and MMC Device Attributes
  2. ============================
  3. All attributes are read-only.
  4. cid Card Identifaction Register
  5. csd Card Specific Data Register
  6. scr SD Card Configuration Register (SD only)
  7. date Manufacturing Date (from CID Register)
  8. fwrev Firmware/Product Revision (from CID Register) (SD and MMCv1 only)
  9. hwrev Hardware/Product Revision (from CID Register) (SD and MMCv1 only)
  10. manfid Manufacturer ID (from CID Register)
  11. name Product Name (from CID Register)
  12. oemid OEM/Application ID (from CID Register)
  13. serial Product Serial Number (from CID Register)
  14. erase_size Erase group size
  15. preferred_erase_size Preferred erase size
  16. Note on Erase Size and Preferred Erase Size:
  17. "erase_size" is the minimum size, in bytes, of an erase
  18. operation. For MMC, "erase_size" is the erase group size
  19. reported by the card. Note that "erase_size" does not apply
  20. to trim or secure trim operations where the minimum size is
  21. always one 512 byte sector. For SD, "erase_size" is 512
  22. if the card is block-addressed, 0 otherwise.
  23. SD/MMC cards can erase an arbitrarily large area up to and
  24. including the whole card. When erasing a large area it may
  25. be desirable to do it in smaller chunks for three reasons:
  26. 1. A single erase command will make all other I/O on
  27. the card wait. This is not a problem if the whole card
  28. is being erased, but erasing one partition will make
  29. I/O for another partition on the same card wait for the
  30. duration of the erase - which could be a several
  31. minutes.
  32. 2. To be able to inform the user of erase progress.
  33. 3. The erase timeout becomes too large to be very
  34. useful. Because the erase timeout contains a margin
  35. which is multiplied by the size of the erase area,
  36. the value can end up being several minutes for large
  37. areas.
  38. "erase_size" is not the most efficient unit to erase
  39. (especially for SD where it is just one sector),
  40. hence "preferred_erase_size" provides a good chunk
  41. size for erasing large areas.
  42. For MMC, "preferred_erase_size" is the high-capacity
  43. erase size if a card specifies one, otherwise it is
  44. based on the capacity of the card.
  45. For SD, "preferred_erase_size" is the allocation unit
  46. size specified by the card.
  47. "preferred_erase_size" is in bytes.