]>
Commit | Line | Data |
---|---|---|
f77e3faa AC |
1 | /** @file\r |
2 | This file defines the EFI REST EX Protocol interface. It is\r | |
3 | split into the following two main sections.\r | |
4 | \r | |
5 | - REST EX Service Binding Protocol\r | |
6 | - REST EX Protocol\r | |
7 | \r | |
8 | Copyright (c) 2019, Intel Corporation. All rights reserved.<BR>\r | |
9 | (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>\r | |
10 | \r | |
11 | SPDX-License-Identifier: BSD-2-Clause-Patent\r | |
12 | \r | |
13 | @par Revision Reference:\r | |
14 | This Protocol is introduced in UEFI Specification 2.8\r | |
15 | \r | |
16 | **/\r | |
17 | \r | |
18 | #ifndef EFI_REST_EX_PROTOCOL_H_\r | |
19 | #define EFI_REST_EX_PROTOCOL_H_\r | |
20 | \r | |
21 | #include <Protocol/Http.h>\r | |
22 | \r | |
23 | //\r | |
2f88bd3a | 24 | // GUID definitions\r |
f77e3faa AC |
25 | //\r |
26 | #define EFI_REST_EX_SERVICE_BINDING_PROTOCOL_GUID \\r | |
27 | { \\r | |
28 | 0x456bbe01, 0x99d0, 0x45ea, {0xbb, 0x5f, 0x16, 0xd8, 0x4b, 0xed, 0xc5, 0x59 } \\r | |
29 | }\r | |
30 | \r | |
31 | #define EFI_REST_EX_PROTOCOL_GUID \\r | |
32 | { \\r | |
33 | 0x55648b91, 0xe7d, 0x40a3, {0xa9, 0xb3, 0xa8, 0x15, 0xd7, 0xea, 0xdf, 0x97 } \\r | |
34 | }\r | |
35 | \r | |
36 | typedef struct _EFI_REST_EX_PROTOCOL EFI_REST_EX_PROTOCOL;\r | |
37 | \r | |
2f88bd3a MK |
38 | // *******************************************************\r |
39 | // EFI_REST_EX_SERVICE_INFO_VER\r | |
40 | // *******************************************************\r | |
f77e3faa | 41 | typedef struct {\r |
2f88bd3a MK |
42 | UINT8 Major;\r |
43 | UINT8 Minor;\r | |
f77e3faa AC |
44 | } EFI_REST_EX_SERVICE_INFO_VER;\r |
45 | \r | |
2f88bd3a MK |
46 | // *******************************************************\r |
47 | // EFI_REST_EX_SERVICE_INFO_HEADER\r | |
48 | // *******************************************************\r | |
f77e3faa | 49 | typedef struct {\r |
2f88bd3a MK |
50 | UINT32 Length;\r |
51 | EFI_REST_EX_SERVICE_INFO_VER RestServiceInfoVer;\r | |
f77e3faa AC |
52 | } EFI_REST_EX_SERVICE_INFO_HEADER;\r |
53 | \r | |
2f88bd3a | 54 | // *******************************************************\r |
f77e3faa | 55 | // EFI_REST_EX_SERVICE_TYPE\r |
2f88bd3a | 56 | // *******************************************************\r |
f77e3faa AC |
57 | typedef enum {\r |
58 | EfiRestExServiceUnspecific = 1,\r | |
59 | EfiRestExServiceRedfish,\r | |
60 | EfiRestExServiceOdata,\r | |
61 | EfiRestExServiceVendorSpecific = 0xff,\r | |
62 | EfiRestExServiceTypeMax\r | |
63 | } EFI_REST_EX_SERVICE_TYPE;\r | |
64 | \r | |
2f88bd3a | 65 | // *******************************************************\r |
f77e3faa | 66 | // EFI_REST_EX_SERVICE_ACCESS_MODE\r |
2f88bd3a | 67 | // *******************************************************\r |
f77e3faa | 68 | typedef enum {\r |
2f88bd3a | 69 | EfiRestExServiceInBandAccess = 1,\r |
f77e3faa AC |
70 | EfiRestExServiceOutOfBandAccess = 2,\r |
71 | EfiRestExServiceModeMax\r | |
72 | } EFI_REST_EX_SERVICE_ACCESS_MODE;\r | |
73 | \r | |
2f88bd3a | 74 | // *******************************************************\r |
f77e3faa | 75 | // EFI_REST_EX_CONFIG_TYPE\r |
2f88bd3a | 76 | // *******************************************************\r |
f77e3faa AC |
77 | typedef enum {\r |
78 | EfiRestExConfigHttp,\r | |
79 | EfiRestExConfigUnspecific,\r | |
80 | EfiRestExConfigTypeMax\r | |
81 | } EFI_REST_EX_CONFIG_TYPE;\r | |
82 | \r | |
2f88bd3a MK |
83 | // *******************************************************\r |
84 | // EFI_REST_EX_SERVICE_INFO v1.0\r | |
85 | // *******************************************************\r | |
f77e3faa | 86 | typedef struct {\r |
2f88bd3a MK |
87 | EFI_REST_EX_SERVICE_INFO_HEADER EfiRestExServiceInfoHeader;\r |
88 | EFI_REST_EX_SERVICE_TYPE RestServiceType;\r | |
89 | EFI_REST_EX_SERVICE_ACCESS_MODE RestServiceAccessMode;\r | |
90 | EFI_GUID VendorRestServiceName;\r | |
91 | UINT32 VendorSpecificDataLength;\r | |
92 | UINT8 *VendorSpecifcData;\r | |
93 | EFI_REST_EX_CONFIG_TYPE RestExConfigType;\r | |
94 | UINT8 RestExConfigDataLength;\r | |
f77e3faa AC |
95 | } EFI_REST_EX_SERVICE_INFO_V_1_0;\r |
96 | \r | |
2f88bd3a MK |
97 | // *******************************************************\r |
98 | // EFI_REST_EX_SERVICE_INFO\r | |
99 | // *******************************************************\r | |
f77e3faa | 100 | typedef union {\r |
2f88bd3a MK |
101 | EFI_REST_EX_SERVICE_INFO_HEADER EfiRestExServiceInfoHeader;\r |
102 | EFI_REST_EX_SERVICE_INFO_V_1_0 EfiRestExServiceInfoV10;\r | |
f77e3faa AC |
103 | } EFI_REST_EX_SERVICE_INFO;\r |
104 | \r | |
2f88bd3a | 105 | // *******************************************************\r |
f77e3faa | 106 | // EFI_REST_EX_HTTP_CONFIG_DATA\r |
2f88bd3a | 107 | // *******************************************************\r |
f77e3faa AC |
108 | typedef struct {\r |
109 | EFI_HTTP_CONFIG_DATA HttpConfigData;\r | |
110 | UINT32 SendReceiveTimeout;\r | |
111 | } EFI_REST_EX_HTTP_CONFIG_DATA;\r | |
112 | \r | |
2f88bd3a MK |
113 | // *******************************************************\r |
114 | // EFI_REST_EX_CONFIG_DATA\r | |
115 | // *******************************************************\r | |
f77e3faa AC |
116 | typedef UINT8 *EFI_REST_EX_CONFIG_DATA;\r |
117 | \r | |
2f88bd3a MK |
118 | // *******************************************************\r |
119 | // EFI_REST_EX_TOKEN\r | |
120 | // *******************************************************\r | |
f77e3faa | 121 | typedef struct {\r |
2f88bd3a MK |
122 | EFI_EVENT Event;\r |
123 | EFI_STATUS Status;\r | |
124 | EFI_HTTP_MESSAGE *ResponseMessage;\r | |
f77e3faa AC |
125 | } EFI_REST_EX_TOKEN;\r |
126 | \r | |
127 | /**\r | |
128 | Provides a simple HTTP-like interface to send and receive resources from a REST service.\r | |
129 | \r | |
130 | The SendReceive() function sends an HTTP request to this REST service, and returns a\r | |
131 | response when the data is retrieved from the service. RequestMessage contains the HTTP\r | |
132 | request to the REST resource identified by RequestMessage.Request.Url. The\r | |
133 | ResponseMessage is the returned HTTP response for that request, including any HTTP\r | |
134 | status.\r | |
135 | \r | |
136 | @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r | |
137 | REST service.\r | |
138 | @param[in] RequestMessage Pointer to the HTTP request data for this resource\r | |
139 | @param[out] ResponseMessage Pointer to the HTTP response data obtained for this requested.\r | |
140 | \r | |
141 | @retval EFI_SUCCESS operation succeeded.\r | |
142 | @retval EFI_INVALID_PARAMETER This, RequestMessage, or ResponseMessage are NULL.\r | |
143 | @retval EFI_DEVICE_ERROR An unexpected system or network error occurred.\r | |
144 | \r | |
145 | **/\r | |
146 | typedef\r | |
147 | EFI_STATUS\r | |
148 | (EFIAPI *EFI_REST_SEND_RECEIVE)(\r | |
149 | IN EFI_REST_EX_PROTOCOL *This,\r | |
150 | IN EFI_HTTP_MESSAGE *RequestMessage,\r | |
151 | OUT EFI_HTTP_MESSAGE *ResponseMessage\r | |
152 | );\r | |
153 | \r | |
154 | /**\r | |
155 | Obtain the current time from this REST service instance.\r | |
156 | \r | |
157 | The GetServiceTime() function is an optional interface to obtain the current time from\r | |
158 | this REST service instance. If this REST service does not support to retrieve the time,\r | |
159 | this function returns EFI_UNSUPPORTED. This function must returns EFI_UNSUPPORTED if\r | |
160 | EFI_REST_EX_SERVICE_TYPE returned in EFI_REST_EX_SERVICE_INFO from GetService() is\r | |
161 | EFI_REST_EX_SERVICE_UNSPECIFIC.\r | |
162 | \r | |
163 | @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r | |
164 | REST service.\r | |
165 | @param[out] Time A pointer to storage to receive a snapshot of the current time of\r | |
166 | the REST service.\r | |
167 | \r | |
168 | @retval EFI_SUCCESS operation succeeded.\r | |
169 | @retval EFI_INVALID_PARAMETER This or Time are NULL.\r | |
170 | @retval EFI_UNSUPPORTED The RESTful service does not support returning the time.\r | |
171 | @retval EFI_DEVICE_ERROR An unexpected system or network error occurred.\r | |
172 | @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must\r | |
173 | be executed and returns successfully prior to invoke this function.\r | |
174 | \r | |
175 | **/\r | |
176 | typedef\r | |
177 | EFI_STATUS\r | |
178 | (EFIAPI *EFI_REST_GET_TIME)(\r | |
179 | IN EFI_REST_EX_PROTOCOL *This,\r | |
180 | OUT EFI_TIME *Time\r | |
181 | );\r | |
182 | \r | |
183 | /**\r | |
184 | This function returns the information of REST service provided by this EFI REST EX driver instance.\r | |
185 | \r | |
186 | The information such as the type of REST service and the access mode of REST EX driver instance\r | |
187 | (In-band or Out-of-band) are described in EFI_REST_EX_SERVICE_INFO structure. For the vendor-specific\r | |
188 | REST service, vendor-specific REST service information is returned in VendorSpecifcData.\r | |
189 | REST EX driver designer is well know what REST service this REST EX driver instance intends to\r | |
190 | communicate with. The designer also well know this driver instance is used to talk to BMC through\r | |
191 | specific platform mechanism or talk to REST server through UEFI HTTP protocol. REST EX driver is\r | |
192 | responsible to fill up the correct information in EFI_REST_EX_SERVICE_INFO. EFI_REST_EX_SERVICE_INFO\r | |
193 | is referred by EFI REST clients to pickup the proper EFI REST EX driver instance to get and set resource.\r | |
194 | GetService() is a basic and mandatory function which must be able to use even Configure() is not invoked\r | |
195 | in previously.\r | |
196 | \r | |
197 | @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r | |
198 | REST service.\r | |
199 | @param[out] RestExServiceInfo Pointer to receive a pointer to EFI_REST_EX_SERVICE_INFO structure. The\r | |
200 | format of EFI_REST_EX_SERVICE_INFO is version controlled for the future\r | |
201 | extension. The version of EFI_REST_EX_SERVICE_INFO structure is returned\r | |
202 | in the header within this structure. EFI REST client refers to the correct\r | |
203 | format of structure according to the version number. The pointer to\r | |
204 | EFI_REST_EX_SERVICE_INFO is a memory block allocated by EFI REST EX driver\r | |
205 | instance. That is caller's responsibility to free this memory when this\r | |
206 | structure is no longer needed. Refer to Related Definitions below for the\r | |
207 | definitions of EFI_REST_EX_SERVICE_INFO structure.\r | |
208 | \r | |
209 | @retval EFI_SUCCESS EFI_REST_EX_SERVICE_INFO is returned in RestExServiceInfo. This function\r | |
210 | is not supported in this REST EX Protocol driver instance.\r | |
211 | @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.\r | |
212 | \r | |
213 | **/\r | |
214 | typedef\r | |
215 | EFI_STATUS\r | |
216 | (EFIAPI *EFI_REST_EX_GET_SERVICE)(\r | |
217 | IN EFI_REST_EX_PROTOCOL *This,\r | |
218 | OUT EFI_REST_EX_SERVICE_INFO **RestExServiceInfo\r | |
219 | );\r | |
220 | \r | |
221 | /**\r | |
222 | This function returns operational configuration of current EFI REST EX child instance.\r | |
223 | \r | |
224 | This function returns the current configuration of EFI REST EX child instance. The format of\r | |
225 | operational configuration depends on the implementation of EFI REST EX driver instance. For\r | |
226 | example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol as the undying protocol\r | |
227 | to communicate with REST service. In this case, the type of configuration is\r | |
228 | EFI_REST_EX_CONFIG_TYPE_HTTP returned from GetService(). EFI_HTTP_CONFIG_DATA is used as EFI REST\r | |
229 | EX configuration format and returned to EFI REST client. User has to type cast RestExConfigData\r | |
230 | to EFI_HTTP_CONFIG_DATA. For those non HTTP-aware REST EX driver instances, the type of configuration\r | |
231 | is EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC returned from GetService(). In this case, the format of\r | |
232 | returning data could be non industrial. Instead, the format of configuration data is system/platform\r | |
233 | specific definition such as BMC mechanism used in EFI REST EX driver instance. EFI REST client and\r | |
234 | EFI REST EX driver instance have to refer to the specific system /platform spec which is out of UEFI scope.\r | |
235 | \r | |
236 | @param[in] This This is the EFI_REST_EX_PROTOCOL instance.\r | |
237 | @param[out] RestExConfigData Pointer to receive a pointer to EFI_REST_EX_CONFIG_DATA.\r | |
238 | The memory allocated for configuration data should be freed\r | |
239 | by caller. See Related Definitions for the details.\r | |
240 | \r | |
241 | @retval EFI_SUCCESS EFI_REST_EX_CONFIG_DATA is returned in successfully.\r | |
242 | @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.\r | |
243 | @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be\r | |
244 | executed and returns successfully prior to invoke this function.\r | |
245 | \r | |
246 | **/\r | |
247 | typedef\r | |
248 | EFI_STATUS\r | |
249 | (EFIAPI *EFI_REST_EX_GET_MODE_DATA)(\r | |
250 | IN EFI_REST_EX_PROTOCOL *This,\r | |
251 | OUT EFI_REST_EX_CONFIG_DATA *RestExConfigData\r | |
252 | );\r | |
253 | \r | |
254 | /**\r | |
255 | This function is used to configure EFI REST EX child instance.\r | |
256 | \r | |
257 | This function is used to configure the setting of underlying protocol of REST EX child\r | |
258 | instance. The type of configuration is according to the implementation of EFI REST EX\r | |
259 | driver instance. For example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol\r | |
260 | as the undying protocol to communicate with REST service. The type of configuration is\r | |
261 | EFI_REST_EX_CONFIG_TYPE_HTTP and RestExConfigData is the same format with EFI_HTTP_CONFIG_DATA.\r | |
262 | Akin to HTTP configuration, REST EX child instance can be configure to use different HTTP\r | |
263 | local access point for the data transmission. Multiple REST clients may use different\r | |
264 | configuration of HTTP to distinguish themselves, such as to use the different TCP port.\r | |
265 | For those non HTTP-aware REST EX driver instance, the type of configuration is\r | |
266 | EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC. RestExConfigData refers to the non industrial standard.\r | |
267 | Instead, the format of configuration data is system/platform specific definition such as BMC.\r | |
268 | In this case, EFI REST client and EFI REST EX driver instance have to refer to the specific\r | |
269 | system/platform spec which is out of the UEFI scope. Besides GetService()function, no other\r | |
270 | EFI REST EX functions can be executed by this instance until Configure()is executed and returns\r | |
271 | successfully. All other functions must returns EFI_NOT_READY if this instance is not configured\r | |
272 | yet. Set RestExConfigData to NULL means to put EFI REST EX child instance into the unconfigured\r | |
273 | state.\r | |
274 | \r | |
275 | @param[in] This This is the EFI_REST_EX_PROTOCOL instance.\r | |
276 | @param[in] RestExConfigData Pointer to EFI_REST_EX_CONFIG_DATA. See Related Definitions in\r | |
277 | GetModeData() protocol interface.\r | |
278 | \r | |
279 | @retval EFI_SUCCESS EFI_REST_EX_CONFIG_DATA is set in successfully.\r | |
280 | @retval EFI_DEVICE_ERROR Configuration for this REST EX child instance is failed with the given\r | |
281 | EFI_REST_EX_CONFIG_DATA.\r | |
282 | @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.\r | |
283 | \r | |
284 | **/\r | |
285 | typedef\r | |
286 | EFI_STATUS\r | |
287 | (EFIAPI *EFI_REST_EX_CONFIGURE)(\r | |
288 | IN EFI_REST_EX_PROTOCOL *This,\r | |
289 | IN EFI_REST_EX_CONFIG_DATA RestExConfigData\r | |
290 | );\r | |
291 | \r | |
292 | /**\r | |
293 | This function sends REST request to REST service and signal caller's event asynchronously when\r | |
294 | the final response is received by REST EX Protocol driver instance.\r | |
295 | \r | |
296 | The essential design of this function is to handle asynchronous send/receive implicitly according\r | |
297 | to REST service asynchronous request mechanism. Caller will get the notification once the response\r | |
298 | is returned from REST service.\r | |
299 | \r | |
300 | @param[in] This This is the EFI_REST_EX_PROTOCOL instance.\r | |
301 | @param[in] RequestMessage This is the HTTP request message sent to REST service. Set RequestMessage\r | |
302 | to NULL to cancel the previous asynchronous request associated with the\r | |
303 | corresponding RestExToken. See descriptions for the details.\r | |
304 | @param[in] RestExToken REST EX token which REST EX Protocol instance uses to notify REST client\r | |
305 | the status of response of asynchronous REST request. See related definition\r | |
306 | of EFI_REST_EX_TOKEN.\r | |
307 | @param[in] TimeOutInMilliSeconds The pointer to the timeout in milliseconds which REST EX Protocol driver\r | |
308 | instance refers as the duration to drop asynchronous REST request. NULL\r | |
309 | pointer means no timeout for this REST request. REST EX Protocol driver\r | |
310 | signals caller's event with EFI_STATUS set to EFI_TIMEOUT in RestExToken\r | |
311 | if REST EX Protocol can't get the response from REST service within\r | |
312 | TimeOutInMilliSeconds.\r | |
313 | \r | |
314 | @retval EFI_SUCCESS Asynchronous REST request is established.\r | |
315 | @retval EFI_UNSUPPORTED This REST EX Protocol driver instance doesn't support asynchronous request.\r | |
316 | @retval EFI_TIMEOUT Asynchronous REST request is not established and timeout is expired.\r | |
317 | @retval EFI_ABORT Previous asynchronous REST request has been canceled.\r | |
318 | @retval EFI_DEVICE_ERROR Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.\r | |
319 | @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be executed\r | |
320 | and returns successfully prior to invoke this function.\r | |
321 | \r | |
322 | **/\r | |
323 | typedef\r | |
324 | EFI_STATUS\r | |
325 | (EFIAPI *EFI_REST_EX_ASYNC_SEND_RECEIVE)(\r | |
326 | IN EFI_REST_EX_PROTOCOL *This,\r | |
327 | IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL,\r | |
328 | IN EFI_REST_EX_TOKEN *RestExToken,\r | |
329 | IN UINTN *TimeOutInMilliSeconds OPTIONAL\r | |
330 | );\r | |
331 | \r | |
332 | /**\r | |
333 | This function sends REST request to a REST Event service and signals caller's event\r | |
334 | token asynchronously when the URI resource change event is received by REST EX\r | |
335 | Protocol driver instance.\r | |
336 | \r | |
337 | The essential design of this function is to monitor event implicitly according to\r | |
338 | REST service event service mechanism. Caller will get the notification if certain\r | |
339 | resource is changed.\r | |
340 | \r | |
341 | @param[in] This This is the EFI_REST_EX_PROTOCOL instance.\r | |
342 | @param[in] RequestMessage This is the HTTP request message sent to REST service. Set RequestMessage\r | |
343 | to NULL to cancel the previous event service associated with the corresponding\r | |
344 | RestExToken. See descriptions for the details.\r | |
345 | @param[in] RestExToken REST EX token which REST EX Protocol driver instance uses to notify REST client\r | |
346 | the URI resource which monitored by REST client has been changed. See the related\r | |
347 | definition of EFI_REST_EX_TOKEN in EFI_REST_EX_PROTOCOL.AsyncSendReceive().\r | |
348 | \r | |
349 | @retval EFI_SUCCESS Asynchronous REST request is established.\r | |
350 | @retval EFI_UNSUPPORTED This REST EX Protocol driver instance doesn't support asynchronous request.\r | |
351 | @retval EFI_ABORT Previous asynchronous REST request has been canceled or event subscription has been\r | |
352 | delete from service.\r | |
353 | @retval EFI_DEVICE_ERROR Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.\r | |
354 | @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be executed\r | |
355 | and returns successfully prior to invoke this function.\r | |
356 | \r | |
357 | **/\r | |
358 | typedef\r | |
359 | EFI_STATUS\r | |
360 | (EFIAPI *EFI_REST_EX_EVENT_SERVICE)(\r | |
361 | IN EFI_REST_EX_PROTOCOL *This,\r | |
362 | IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL,\r | |
363 | IN EFI_REST_EX_TOKEN *RestExToken\r | |
2f88bd3a | 364 | );\r |
f77e3faa AC |
365 | \r |
366 | ///\r | |
367 | /// EFI REST(EX) protocols are designed to support REST communication between EFI REST client\r | |
368 | /// applications/drivers and REST services. EFI REST client tool uses EFI REST(EX) protocols\r | |
369 | /// to send/receive resources to/from REST service to manage systems, configure systems or\r | |
370 | /// manipulate resources on REST service. Due to HTTP protocol is commonly used to communicate\r | |
371 | /// with REST service in practice, EFI REST(EX) protocols adopt HTTP as the message format to\r | |
372 | /// send and receive REST service resource. EFI REST(EX) driver instance abstracts EFI REST\r | |
373 | /// client functionality and provides underlying interface to communicate with REST service.\r | |
374 | /// EFI REST(EX) driver instance knows how to communicate with REST service through certain\r | |
375 | /// interface after the corresponding configuration is initialized.\r | |
376 | ///\r | |
377 | struct _EFI_REST_EX_PROTOCOL {\r | |
2f88bd3a MK |
378 | EFI_REST_SEND_RECEIVE SendReceive;\r |
379 | EFI_REST_GET_TIME GetServiceTime;\r | |
380 | EFI_REST_EX_GET_SERVICE GetService;\r | |
381 | EFI_REST_EX_GET_MODE_DATA GetModeData;\r | |
382 | EFI_REST_EX_CONFIGURE Configure;\r | |
383 | EFI_REST_EX_ASYNC_SEND_RECEIVE AyncSendReceive;\r | |
384 | EFI_REST_EX_EVENT_SERVICE EventService;\r | |
f77e3faa AC |
385 | };\r |
386 | \r | |
2f88bd3a MK |
387 | extern EFI_GUID gEfiRestExServiceBindingProtocolGuid;\r |
388 | extern EFI_GUID gEfiRestExProtocolGuid;\r | |
f77e3faa AC |
389 | \r |
390 | #endif\r |