]> git.proxmox.com Git - mirror_edk2.git/blame_incremental - MdeModulePkg/Universal/Variable/RuntimeDxe/VariableStandaloneMm.c
IntelFsp2WrapperPkg: Apply uncrustify changes
[mirror_edk2.git] / MdeModulePkg / Universal / Variable / RuntimeDxe / VariableStandaloneMm.c
... / ...
CommitLineData
1/** @file\r
2\r
3 Parts of the SMM/MM implementation that are specific to standalone MM\r
4\r
5Copyright (c) 2011 - 2018, Intel Corporation. All rights reserved. <BR>\r
6Copyright (c) 2018, Linaro, Ltd. All rights reserved. <BR>\r
7SPDX-License-Identifier: BSD-2-Clause-Patent\r
8\r
9**/\r
10\r
11#include "Variable.h"\r
12\r
13/**\r
14 This function checks if the buffer is valid per processor architecture and\r
15 does not overlap with SMRAM.\r
16\r
17 @param Buffer The buffer start address to be checked.\r
18 @param Length The buffer length to be checked.\r
19\r
20 @retval TRUE This buffer is valid per processor architecture and does not\r
21 overlap with SMRAM.\r
22 @retval FALSE This buffer is not valid per processor architecture or overlaps\r
23 with SMRAM.\r
24**/\r
25BOOLEAN\r
26VariableSmmIsBufferOutsideSmmValid (\r
27 IN EFI_PHYSICAL_ADDRESS Buffer,\r
28 IN UINT64 Length\r
29 )\r
30{\r
31 return TRUE;\r
32}\r
33\r
34/**\r
35 Notify the system that the SMM variable driver is ready.\r
36**/\r
37VOID\r
38VariableNotifySmmReady (\r
39 VOID\r
40 )\r
41{\r
42}\r
43\r
44/**\r
45 Notify the system that the SMM variable write driver is ready.\r
46**/\r
47VOID\r
48VariableNotifySmmWriteReady (\r
49 VOID\r
50 )\r
51{\r
52}\r
53\r
54/**\r
55 Variable service MM driver entry point.\r
56\r
57 @param[in] ImageHandle A handle for the image that is initializing this\r
58 driver\r
59 @param[in] MmSystemTable A pointer to the MM system table\r
60\r
61 @retval EFI_SUCCESS Variable service successfully initialized.\r
62**/\r
63EFI_STATUS\r
64EFIAPI\r
65VariableServiceInitialize (\r
66 IN EFI_HANDLE ImageHandle,\r
67 IN EFI_MM_SYSTEM_TABLE *MmSystemTable\r
68 )\r
69{\r
70 return MmVariableServiceInitialize ();\r
71}\r
72\r
73/**\r
74 Whether the TCG or TCG2 protocols are installed in the UEFI protocol database.\r
75 This information is used by the MorLock code to infer whether an existing\r
76 MOR variable is legitimate or not.\r
77\r
78 @retval TRUE Either the TCG or TCG2 protocol is installed in the UEFI\r
79 protocol database\r
80 @retval FALSE Neither the TCG nor the TCG2 protocol is installed in the UEFI\r
81 protocol database\r
82**/\r
83BOOLEAN\r
84VariableHaveTcgProtocols (\r
85 VOID\r
86 )\r
87{\r
88 return FALSE;\r
89}\r