T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

238 CHAPTER 5. T-KERNEL/SM evtmbfid designates the system default message buffer ID for event notification. If there is no system default event notification message buffer, 0 is set. Notification like the following is made to each subsystem when a device is registered or deleted. devid is the device ID of the physical device registered or deleted. Device registration or update: Device deletion: E LIMIT E NOEXS tk_evt_ssy(0, TSEVT_DEVICE_REGIST, 0, devid) tk_evt_ssy(0, TSEVT_DEVICE_DELETE, 0, devid) Number of registrations exceeds the system limit The device designated in devnm does not exist (when ddev = NULL) • ER tk_ref_idv( T_IDEV *idev ) idev return code Returns device initialization information Error Gets device initialization information. The contents are the same as the information obtained by tk dev def(). 5.3.4 Device Driver Interface The device driver interface consists of processing functions designated when registering a device. These functions are called by device management and run as a quasi-task portion. They must be reentrant. The mutually exclusive calling of these processing functions is not guaranteed. If, for example, there are simultaneous requests from multiple devices for the same device, different tasks might call the same processing function at the same time. The device driver must apply mutual exclusion control in such cases as necessary. IO requests to a device driver are made by means of the following request packet mapped to a request ID. typedef struct t_devreq { struct t_devreq *next; /* I: Link to request packet (NULL: termination) */ VP exinf; /* X: Extended information */ ID devid; /* I: Target device ID */ INT cmd:4; /* I: Request command */ BOOL abort:1; /* I: TRUE if abort request */ BOOL nolock:1; /* I: TRUE if lock (making resident) not needed */ INT rsv:26; /* I: reserved (always 0) */ T_TSKSPC tskspc; /* I: Task space of requesting task */ INT start; /* I: Starting data number */ INT size; /* I: Request size */ VP buf; /* I: IO buffer address */ INT asize; /* O: Size of result */ ER error; /* O: Error result */ /* Implementation-dependent information may be added beyond this point. */ } T_DEVREQ; I indicates an input parameter and O an output parameter. Input parameters must not be changed by the device driver. Parameters other than input parameters (I) are initially cleared to 0 by device management. After that, device management does not modify them. next is used to link the request packet. In addition to use for keeping track of request packets in device management, it is used also by the completion wait function (waitfn) and abort function (abortfn). Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
5.3. DEVICE MANAGEMENT FUNCTIONS 239 exinf can be used freely by the device driver. Device management does not pay attention to the contents. The device ID of the device to which the request is issued is designated in devid. The request command is designated in cmd as follows. cmd := (TDC_READ || TDC_WRITE) #define TDC_READ 1 /* read request */ #define TDC_WRITE 2 /* write request */ If abort processing is to be carried out, abort is set to TRUE right before calling the abort function (abortfn). abort is a flag indicating whether abort processing was requested, and does not indicate that processing was aborted. In some cases abort is set to TRUE even when the abort function (abortfn) is not called. Abort processing is performed when a request with abort set to TRUE is actually passed to the device driver. nolock indicates that the memory space designated in buf has already been locked (made resident) and does not need to be locked by the device driver. In this case the device driver must not lock the memory space. (nolock is designated when there is a possibility of wrong operation if the device driver performs a lock. Accordingly, when nolock = TRUE, the device driver must not lock the space.) tskspc sets the task space of the requesting task. Since processing functions are called in the context of the requesting task, tskspc is the same as the task space of the processing function. If, however, the actual IO processing (read/write in the space designated in buf) is performed by a separate task in the device driver, it is necessary to switch the task space of the task performing the IO processing to the task space of the requesting task. The start and size parameters designated with tk rea dev or tk wri dev are set transparently in start and size here. The buf parameter designated with tk rea dev or tk wri dev is set in buf here. The memory space designated in buf may be nonresident in some cases or task space in others. Care must therefore be taken regarding the following points. • Nonresident memory cannot be accessed from a task-independent portion or while dispatching or interrupts are disabled. • Task space memory cannot be accessed from another task space. For these reasons, switching of task space or making memory space resident must be performed as necessary. Special attention is needed when access is made by an interrupt handler. Generally it is best not to access buf directly from an interrupt handler. Before accessing the buf memory space, the validity of buf must be checked using an address space check function (ChkSpace—, described later below). The device driver sets in asize the value returned in asize by tk wai dev. The device driver sets in error the error code passed by tk wai dev in its return code. E OK indicates a normal result. • Open Function: ER openfn( ID devid, UINT omode, VP exinf ) devid omode exinf return code Device ID of the device to open Open mode (same as tk opn dev) Extended information set at device registration Error The open function openfn is called when tk opn dev is invoked. Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
Page 1 and 2:
T-Kernel Specification T-Kernel 1.B
Page 3 and 4:
Contents 1 T-Kernel Overview 1 1.1
Page 5 and 6:
CONTENTS v tk set flg (Set Event Fl
Page 7 and 8:
CONTENTS vii 5.2.2 Address Space Ch
Page 9 and 10:
CONTENTS ix td cal que (Reference Q
Page 11 and 12:
List of Figures 1.1 Position of T-K
Page 13 and 14:
List of Tables 2.1 State Transition
Page 15 and 16:
System Call Notation In the parts o
Page 17 and 18:
Index of T-Kernel/OS System Calls T
Page 19 and 20:
INDEX OF T-KERNEL/OS SYSTEM CALLS x
Page 21 and 22:
Index of T-Kernel/SM Extended SVC L
Page 23 and 24:
Index of T-Kernel/DS System Calls T
Page 25 and 26:
Chapter 1 T-Kernel Overview 1.1 Pos
Page 27 and 28:
1.2. SCALABILITY 3 • Middleware m
Page 29 and 30:
Chapter 2 Concepts Underlying the T
Page 31 and 32:
2.2. TASK STATES AND SCHEDULING RUL
Page 33 and 34:
2.2. TASK STATES AND SCHEDULING RUL
Page 35 and 36:
2.3. INTERRUPT HANDLING 11 preceden
Page 37 and 38:
2.5. SYSTEM STATES 13 Transient sta
Page 39 and 40:
2.7. MEMORY 15 which the upper and
Page 41 and 42:
Chapter 3 Common T-Kernel Specifica
Page 43 and 44:
3.2. SYSTEM CALLS 19 /* * Common co
Page 45 and 46:
3.2. SYSTEM CALLS 21 Ordinarily a f
Page 47 and 48:
3.3. HIGH-LEVEL LANGUAGE SUPPORT RO
Page 49 and 50:
Chapter 4 T-Kernel/OS Functions Thi
Page 51 and 52:
4.1. TASK MANAGEMENT FUNCTIONS 27 t
Page 53 and 54:
4.1. TASK MANAGEMENT FUNCTIONS 29 #
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
4.2. TASK-DEPENDENT SYNCHRONIZATION
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
4.3. TASK EXCEPTION HANDLING FUNCTI
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
4.4. SYNCHRONIZATION AND COMMUNICAT
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
4.5. EXTENDED SYNCHRONIZATION AND C
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
4.7. TIME MANAGEMENT FUNCTIONS 163
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
4.8. INTERRUPT MANAGEMENT FUNCTIONS
Page 211 and 212: 4.8. INTERRUPT MANAGEMENT FUNCTIONS
Page 215 and 216: 4.9. SYSTEM MANAGEMENT FUNCTIONS 19
Page 229 and 230: 4.10. SUBSYSTEM MANAGEMENT FUNCTION
Page 243 and 244: Chapter 5 T-Kernel/SM Details of th
Page 245 and 246: 5.1. SYSTEM MEMORY MANAGEMENT FUNCT
Page 247 and 248: 5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 249 and 250: 5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 251 and 252: 5.3. DEVICE MANAGEMENT FUNCTIONS 22
Page 261: 5.3. DEVICE MANAGEMENT FUNCTIONS 23
Page 275 and 276: 5.5. IO PORT ACCESS SUPPORT FUNCTIO
Page 277 and 278: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 279 and 280: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 281: 5.8. SUBSYSTEM AND DEVICE DRIVER ST
Page 284 and 285: 260 CHAPTER 6. T-KERNEL/DS FUNCTION
Page 308 and 309: 284 CHAPTER 7. REFERENCE INT tevptn
Page 310 and 311: 286 CHAPTER 7. REFERENCE ER ercd =
Page 312 and 313:
288 CHAPTER 7. REFERENCE INT ct = t
Page 314:
290 CHAPTER 7. REFERENCE E OACV ERC
show all

T-Kernel Specification (1.B0.02)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?