MM IO Trap Dispatch Protocol as defined in PI 1.5 Specification Volume 4 Management Mode Core Interface.
This protocol provides a parent dispatch service for IO trap MMI sources.
Copyright (c) 2017, Intel Corporation. All rights reserved.
SPDX-License-Identifier: BSD-2-Clause-Patent
- Revision Reference:
- This protocol is from PI Version 1.5.
Register an IO trap MMI child handler for a specified MMI.
This service registers a function (DispatchFunction) which will be called when an MMI is generated because of an access to an I/O port specified by RegisterContext. On return, DispatchHandle contains a unique handle which may be used later to unregister the function using UnRegister(). If the base of the I/O range specified is zero, then an I/O range with the specified length and characteristics will be allocated and the Address field in RegisterContext updated. If no range could be allocated, then EFI_OUT_OF_RESOURCES will be returned.
The service will not perform GCD allocation if the base address is non-zero or EFI_MM_READY_TO_LOCK has been installed. In this case, the caller is responsible for the existence and allocation of the specific IO range. An error may be returned if some or all of the requested resources conflict with an existing IO trap child handler.
It is not required that implementations will allow multiple children for a single IO trap MMI source. Some implementations may support multiple children. The DispatchFunction will be called with Context updated to contain information concerning the I/O action that actually happened and is passed in RegisterContext, with CommBuffer pointing to the data actually written and CommBufferSize pointing to the size of the data in CommBuffer.
- Parameters
-
[in] | This | Pointer to the EFI_MM_IO_TRAP_DISPATCH_PROTOCOL instance. |
[in] | DispatchFunction | Function to register for handler when I/O trap location is accessed. |
[in] | RegisterContext | Pointer to the dispatch function's context. The caller fills this context in before calling the register function to indicate to the register function the IO trap MMI source for which the dispatch function should be invoked. |
[out] | DispatchHandle | Handle of the dispatch function, for when interfacing with the parent MM driver. |
- Return values
-
EFI_SUCCESS | The dispatch function has been successfully registered. |
EFI_DEVICE_ERROR | The driver was unable to complete due to hardware error. |
EFI_OUT_OF_RESOURCES | Insufficient resources are available to fulfill the IO trap range request. |
EFI_INVALID_PARAMETER | RegisterContext is invalid. The input value is not within a valid range. |