SetupDesignGuide.pdf - Firmware Encoding Index
SetupDesignGuide.pdf - Firmware Encoding Index
SetupDesignGuide.pdf - Firmware Encoding Index
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Setup Design Guide<br />
DRAFT<br />
7.3.3 EFI_FORM_CALLBACK_PROTOCOL.CallBack()<br />
Summary<br />
This is the function that is called to provide results data to the driver. This data consists of a unique key<br />
which is used to identify what data is either being passed back or being asked for.<br />
Prototype<br />
EFI_STATUS<br />
(EFIAPI *EFI_FORM_CALLBACK) (<br />
IN EFI_FORM_CALLBACK_PROTOCOL *This,<br />
IN UINT16<br />
KeyValue,<br />
IN VOID<br />
*Data<br />
);<br />
Parameters<br />
This<br />
KeyValue<br />
Data<br />
A pointer to the EFI_NV_ACCESS_PROTOCOL instance.<br />
A unique value which is sent to the original exporting driver so that<br />
it can identify the type of data to expect. The format of the data<br />
tends to vary based on the op-code that generated the callback.<br />
A pointer to the data being sent to the original exporting driver.<br />
Related Definitions<br />
The Data format will be based on the op-code type that the KeyValue<br />
references.<br />
If OneOf op-code the following is being passed in the Data pointer:<br />
UINT16<br />
Value<br />
If Text op-code there is no user initiated data to be sent other<br />
than the KeyValue. There should be a reasonable expectation that a<br />
response to this callback will be that a message gets posted with a<br />
particular key value and string. This would be done in the<br />
EFI_FORM_CONFIGURATION_PROTOCOL.<br />
NULL<br />
If String op-code the following is being passed in the Data pointer:<br />
CHAR16<br />
*String<br />
If Numeric op-code the following is being passed in the Data<br />
pointer:<br />
UINT16<br />
Value<br />
76