T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

236 CHAPTER 5. T-KERNEL/SM Gets information about registered devices. Registered devices are managed per physical device. The registered device information is therefore also obtained per physical device. When the number of registered devices is N, number are assigned serially to devices from 0 to N − 1. Starting from the number designated in start in accord with this scheme, the number of registrations designated in ndev is acquired and put in ldev. The space designated in ldev must be large enough to hold ndev registration information. The number of remaining registrations after start ( N − start ) is passed in the return code. If the number of registrations from start is fewer than ndev, all remaining registrations are stored. A value passed in return code less than or equal to ndev means all remaining registrations were obtained. Note that this numbering changes as devices are registered and deleted. For this reason, accurate information may not always be obtained if the acquisition is carried out over multiple operations. E NOEXS start exceeds the number of registered devices • INT tk_evt_dev( ID devid, INT evttyp, VP evtinf ) devid evttyp evtinf return code Event destination device ID Driver request event type Information for each event type Return code from device driver or error Sends a driver request event to the device (device driver) designated in devid. The following driver request events are defined. #define TDV_CARDEVT 1 /* PC Card event (see Card Manager) */ #define TDV_USBEVT 2 /* USB event (see USB Manager) */ The functioning of driver request events and the contents of evtinf are defined for each event type. E NOEXS E PAR The device designated in devid does not exist Internal device manager events (evttyp < 0) cannot be designated 5.3.3 Device Registration The following device registration information is defined in registering a device. Device registration is performed for each physical device. typedef struct t_ddev { VP exinf; /* extended information */ ATR drvatr; /* driver attributes */ ATR devatr; /* device attributes */ INT nsub; /* subunits */ INT blksz; /* block size of device-specific data (-1: unknown) */ FP openfn; /* open count */ FP closefn; /* close count */ FP execfn; /* processing start function */ FP waitfn; /* completion wait function */ FP abortfn; /* abort processing function */ FP eventfn; /* event function */ /* Implementation-dependent information may be added beyond this point. */ } T\_DDEV; Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
5.3. DEVICE MANAGEMENT FUNCTIONS 237 exinf is used to store any desired information. The value is passed to the processing functions. Device management pays no attention to the contents. drvatr sets device driver attribute information. The low bits indicate system attributes, and the high bits are used for implementation-dependent attributes. The implementation-dependent attribute portion is used, for example, to indicate validity flags when implementation-dependent data is added to T DDEV. drvatr := [TDA_OPENREQ] #define TDA_OPENREQ 0x0001 /* open/close each time */ TDA OPENREQ When a device is opened multiple times, normally openfn is called the first time it is opened and closefn the last time it is closed. If TDA OPENREQ is designated, then openfn/closefn will be called for all open/close operations even in case of multiple openings. Device attributes are designated in devatr. The details of device attribute setting are as noted above. The number of subunits is set in nsub. If there are no subunits, 0 is designated. blksz sets the block size of device-specific data in bytes. In the case of a disk device, this is the physical block size. It is set to 1 byte for a serial port, etc. For a device with no device-specific data it is set to 0. For an unformatted disk or other device whose block size is unknown, −1 is set. If blksz ≤ 0, device-specific data cannot be accessed. When device-specific data is accessed by tk rea dev or tk wri dev, size × blksz must be the size of the area being accessed, that is, the size of buf. openfn, closefn, execfn, waitfn, abortfn, and eventfn set the entry address of processing functions. Details of the processing functions are discussed later. • ID tk_def_dev( UB *devnm, T_DDEV *ddev, T_IDEV *idev ) devnm ddev idev return code Physical device name Device registration information Returns device initialization information Device ID or error Registers a device with the device name set in devnm. If a device with device name devnm is already registered, the registration is updated with new information, in which case the device ID does not change. When ddev = NULL is designated, device devnm registration is deleted. The device initialization information is returned in idev. This includes information set by default when the device driver is started, and can be used as necessary. When idev = NULL is set, device initialization information is not stored. typedef struct t_idev { ID evtmbfid; /* event notification message buffer ID */ /* Implementation-dependent information may be added beyond this point.*/ } T_IDEV; 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 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 259: 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)

Create successful ePaper yourself

Delete template?

Save as template?