1
2
3
4
5
6
7
8
9
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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
#ifndef LINUX_MMC_IOCTL_H
#define LINUX_MMC_IOCTL_H
#include <linux/types.h>
struct mmc_ioc_cmd {
/* Implies direction of data. true = write, false = read */
int write_flag;
/* Application-specific command. true = precede with CMD55 */
int is_acmd;
__u32 opcode;
__u32 arg;
__u32 response[4]; /* CMD response */
unsigned int flags;
unsigned int blksz;
unsigned int blocks;
/*
* Sleep at least postsleep_min_us useconds, and at most
* postsleep_max_us useconds *after* issuing command. Needed for
* some read commands for which cards have no other way of indicating
* they're ready for the next command (i.e. there is no equivalent of
* a "busy" indicator for read operations).
*/
unsigned int postsleep_min_us;
unsigned int postsleep_max_us;
/*
* Override driver-computed timeouts. Note the difference in units!
*/
unsigned int data_timeout_ns;
unsigned int cmd_timeout_ms;
/*
* For 64-bit machines, the next member, ``__u64 data_ptr``, wants to
* be 8-byte aligned. Make sure this struct is the same size when
* built for 32-bit.
*/
__u32 __pad;
/* DAT buffer */
__u64 data_ptr;
};
#define mmc_ioc_cmd_set_data(ic, ptr) ic.data_ptr = (__u64)(unsigned long) ptr
#define MMC_IOC_CMD _IOWR(MMC_BLOCK_MAJOR, 0, struct mmc_ioc_cmd)
/**
* There are four request types that are applicable for rpmb accesses- two
* under read category and two under write. They are
*
* Reads
* -------
* 1. Read Write Counter
* 2. Authenticated data read
*
*
* Writes
* -------
* 1. Provision RPMB key (though it might be done in a secure environment)
* 2. Authenticated data write
*
* While its given that the rpmb data frames are going to have that
* information encoded in it and the frames should be generated by a secure
* piece of code, the request types can be classified as above.
*
* So here are the set of commands that should be executed atomically in the
* ioctl for rpmb read operation
* 1. Switch partition
* 2. Set block count
* 3. Write data frame - CMD25 to write the rpmb data frame
* 4. Set block count
* 5. Read the data - CMD18 to do the actual read
*
* Similarly for rpmb write operation, these are the commands that should be
* executed atomically in the ioctl for rpmb write operation
* 1. Switch partition
* 2. Set block count
* 3. Write data frame - CMD25 to write the rpmb data frame with data
* 4. Set block count
* 5. Read the data - CMD25 to write rpmb data frame indicating that rpmb
* result register is about to be read
* 6. Set block count
* 7. Read rpmb result - CMD18 to read the rpmb result register
*
* Each of the above commands should be sent individually via struct mmc_ioc_cmd
* and fields like is_acmd that are not needed for rpmb operations will be
* ignored.
*/
#define MMC_IOC_MAX_RPMB_CMD 3
struct mmc_ioc_rpmb {
struct mmc_ioc_cmd cmds[MMC_IOC_MAX_RPMB_CMD];
};
/*
* This ioctl is meant for use with rpmb partitions. This is needed since the
* access procedure for this particular partition is different from regular
* or normal partitions.
*/
#define MMC_IOC_RPMB_CMD _IOWR(MMC_BLOCK_MAJOR, 0, struct mmc_ioc_rpmb)
/*
* Since this ioctl is only meant to enhance (and not replace) normal access
* to the mmc bus device, an upper data transfer limit of MMC_IOC_MAX_BYTES
* is enforced per ioctl call. For larger data transfers, use the normal
* block device operations.
*/
#define MMC_IOC_MAX_BYTES (512L * 256)
#endif /* LINUX_MMC_IOCTL_H */
|
