Blame view

Documentation/mmc/mmc-dev-attrs.txt 2.8 KB
371a689f6   Andrei Warkentin   mmc: MMC boot par...
1
2
3
4
5
6
7
8
9
  SD and MMC Block Device Attributes
  ==================================
  
  These attributes are defined for the block devices associated with the
  SD or MMC device.
  
  The following attributes are read/write.
  
  	force_ro		Enforce read-only access even if write protect switch is off.
dfe86cba7   Adrian Hunter   mmc: add erase, s...
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
  SD and MMC Device Attributes
  ============================
  
  All attributes are read-only.
  
  	cid			Card Identifaction Register
  	csd			Card Specific Data Register
  	scr			SD Card Configuration Register (SD only)
  	date			Manufacturing Date (from CID Register)
  	fwrev			Firmware/Product Revision (from CID Register) (SD and MMCv1 only)
  	hwrev			Hardware/Product Revision (from CID Register) (SD and MMCv1 only)
  	manfid			Manufacturer ID (from CID Register)
  	name			Product Name (from CID Register)
  	oemid			OEM/Application ID (from CID Register)
  	serial			Product Serial Number (from CID Register)
  	erase_size		Erase group size
  	preferred_erase_size	Preferred erase size
  
  Note on Erase Size and Preferred Erase Size:
  
  	"erase_size" is the  minimum size, in bytes, of an erase
  	operation.  For MMC, "erase_size" is the erase group size
  	reported by the card.  Note that "erase_size" does not apply
  	to trim or secure trim operations where the minimum size is
  	always one 512 byte sector.  For SD, "erase_size" is 512
  	if the card is block-addressed, 0 otherwise.
  
  	SD/MMC cards can erase an arbitrarily large area up to and
  	including the whole card.  When erasing a large area it may
  	be desirable to do it in smaller chunks for three reasons:
  		1. A single erase command will make all other I/O on
  		the card wait.  This is not a problem if the whole card
  		is being erased, but erasing one partition will make
  		I/O for another partition on the same card wait for the
  		duration of the erase - which could be a several
  		minutes.
  		2. To be able to inform the user of erase progress.
  		3. The erase timeout becomes too large to be very
  		useful.  Because the erase timeout contains a margin
  		which is multiplied by the size of the erase area,
  		the value can end up being several minutes for large
  		areas.
  
  	"erase_size" is not the most efficient unit to erase
  	(especially for SD where it is just one sector),
  	hence "preferred_erase_size" provides a good chunk
  	size for erasing large areas.
  
  	For MMC, "preferred_erase_size" is the high-capacity
  	erase size if a card specifies one, otherwise it is
  	based on the capacity of the card.
  
  	For SD, "preferred_erase_size" is the allocation unit
  	size specified by the card.
  
  	"preferred_erase_size" is in bytes.
597dd9d79   Sujit Reddy Thumma   mmc: core: Use de...
66
67
68
69
70
71
  
  SD/MMC/SDIO Clock Gating Attribute
  ==================================
  
  Read and write access is provided to following attribute.
  This attribute appears only if CONFIG_MMC_CLKGATE is enabled.
4137e5049   Stephen Boyd   mmc: core: Fixup ...
72
  	clkgate_delay	Tune the clock gating delay with desired value in milliseconds.
597dd9d79   Sujit Reddy Thumma   mmc: core: Use de...
73
74
  
  echo <desired delay> > /sys/class/mmc_host/mmcX/clkgate_delay