1 | /** @file
|
---|
2 | EFI MM Control Protocol as defined in the PI 1.5 specification.
|
---|
3 |
|
---|
4 | This protocol is used initiate synchronous MMI activations. This protocol could be published by a
|
---|
5 | processor driver to abstract the MMI IPI or a driver which abstracts the ASIC that is supporting the
|
---|
6 | APM port. Because of the possibility of performing MMI IPI transactions, the ability to generate this
|
---|
7 | event from a platform chipset agent is an optional capability for both IA-32 and x64-based systems.
|
---|
8 |
|
---|
9 | The EFI_MM_CONTROL_PROTOCOL is produced by a runtime driver. It provides an
|
---|
10 | abstraction of the platform hardware that generates an MMI. There are often I/O ports that, when
|
---|
11 | accessed, will generate the MMI. Also, the hardware optionally supports the periodic generation of
|
---|
12 | these signals.
|
---|
13 |
|
---|
14 | Copyright (c) 2017, Intel Corporation. All rights reserved.<BR>
|
---|
15 | SPDX-License-Identifier: BSD-2-Clause-Patent
|
---|
16 |
|
---|
17 | **/
|
---|
18 |
|
---|
19 | #ifndef _MM_CONTROL_H_
|
---|
20 | #define _MM_CONTROL_H_
|
---|
21 |
|
---|
22 | #include <PiDxe.h>
|
---|
23 |
|
---|
24 | #define EFI_MM_CONTROL_PROTOCOL_GUID \
|
---|
25 | { \
|
---|
26 | 0x843dc720, 0xab1e, 0x42cb, {0x93, 0x57, 0x8a, 0x0, 0x78, 0xf3, 0x56, 0x1b} \
|
---|
27 | }
|
---|
28 |
|
---|
29 | typedef struct _EFI_MM_CONTROL_PROTOCOL EFI_MM_CONTROL_PROTOCOL;
|
---|
30 | typedef UINTN EFI_MM_PERIOD;
|
---|
31 |
|
---|
32 | /**
|
---|
33 | Invokes MMI activation from either the preboot or runtime environment.
|
---|
34 |
|
---|
35 | This function generates an MMI.
|
---|
36 |
|
---|
37 | @param[in] This The EFI_MM_CONTROL_PROTOCOL instance.
|
---|
38 | @param[in,out] CommandPort The value written to the command port.
|
---|
39 | @param[in,out] DataPort The value written to the data port.
|
---|
40 | @param[in] Periodic Optional mechanism to engender a periodic stream.
|
---|
41 | @param[in] ActivationInterval Optional parameter to repeat at this period one
|
---|
42 | time or, if the Periodic Boolean is set, periodically.
|
---|
43 |
|
---|
44 | @retval EFI_SUCCESS The MMI/PMI has been engendered.
|
---|
45 | @retval EFI_DEVICE_ERROR The timing is unsupported.
|
---|
46 | @retval EFI_INVALID_PARAMETER The activation period is unsupported.
|
---|
47 | @retval EFI_INVALID_PARAMETER The last periodic activation has not been cleared.
|
---|
48 | @retval EFI_NOT_STARTED The MM base service has not been initialized.
|
---|
49 | **/
|
---|
50 | typedef
|
---|
51 | EFI_STATUS
|
---|
52 | (EFIAPI *EFI_MM_ACTIVATE)(
|
---|
53 | IN CONST EFI_MM_CONTROL_PROTOCOL *This,
|
---|
54 | IN OUT UINT8 *CommandPort OPTIONAL,
|
---|
55 | IN OUT UINT8 *DataPort OPTIONAL,
|
---|
56 | IN BOOLEAN Periodic OPTIONAL,
|
---|
57 | IN UINTN ActivationInterval OPTIONAL
|
---|
58 | );
|
---|
59 |
|
---|
60 | /**
|
---|
61 | Clears any system state that was created in response to the Trigger() call.
|
---|
62 |
|
---|
63 | This function acknowledges and causes the deassertion of the MMI activation source.
|
---|
64 |
|
---|
65 | @param[in] This The EFI_MM_CONTROL_PROTOCOL instance.
|
---|
66 | @param[in] Periodic Optional parameter to repeat at this period one time
|
---|
67 |
|
---|
68 | @retval EFI_SUCCESS The MMI/PMI has been engendered.
|
---|
69 | @retval EFI_DEVICE_ERROR The source could not be cleared.
|
---|
70 | @retval EFI_INVALID_PARAMETER The service did not support the Periodic input argument.
|
---|
71 | **/
|
---|
72 | typedef
|
---|
73 | EFI_STATUS
|
---|
74 | (EFIAPI *EFI_MM_DEACTIVATE)(
|
---|
75 | IN CONST EFI_MM_CONTROL_PROTOCOL *This,
|
---|
76 | IN BOOLEAN Periodic OPTIONAL
|
---|
77 | );
|
---|
78 |
|
---|
79 | ///
|
---|
80 | /// The EFI_MM_CONTROL_PROTOCOL is produced by a runtime driver. It provides an
|
---|
81 | /// abstraction of the platform hardware that generates an MMI. There are often I/O ports that, when
|
---|
82 | /// accessed, will generate the MMI. Also, the hardware optionally supports the periodic generation of
|
---|
83 | /// these signals.
|
---|
84 | ///
|
---|
85 | struct _EFI_MM_CONTROL_PROTOCOL {
|
---|
86 | EFI_MM_ACTIVATE Trigger;
|
---|
87 | EFI_MM_DEACTIVATE Clear;
|
---|
88 | ///
|
---|
89 | /// Minimum interval at which the platform can set the period. A maximum is not
|
---|
90 | /// specified in that the MM infrastructure code can emulate a maximum interval that is
|
---|
91 | /// greater than the hardware capabilities by using software emulation in the MM
|
---|
92 | /// infrastructure code.
|
---|
93 | ///
|
---|
94 | EFI_MM_PERIOD MinimumTriggerPeriod;
|
---|
95 | };
|
---|
96 |
|
---|
97 | extern EFI_GUID gEfiMmControlProtocolGuid;
|
---|
98 |
|
---|
99 | #endif
|
---|