Revert "EFI: Add memory map lookup support for AcpiOsMapMemory()."

This reverts commit 853e4d227f5eccb5044d24d91b87bf5f62698fa2.

Test code not intended for upstream. Lv Zheng
ASLTS: Fixes for SMBUS/GSBUS region access tests

This patch makes corrections to serveral region tests that check operations on
GenericSerialBus and SMBus fields. These changes are required after commit
36a1179 corrected the size of the buffer that was calculated for each of the
different bus protocols.

Signed-off-by: David E. Box <david.e.box@linux.intel.com>
Acpiexec: Set correct access length for SMBUS/GSBUS region test handler

Fixes a bug in the test handler for the SMBUS/GSBUS regions where the access
length for certain protocols was being incorrectly decremented by 2 to account
for the Status and Length bytes. This value already excludes the 2 bytes.

Signed-off-by: David E. Box <david.e.box@linux.intel.com>
OSL: Cleanup conflict namings.

The "Register" will be converted into "register" by the ACPICA release
scripts. This triggers a build issue for Linux kernel, as "register" is a
C language keyword and cannot be used as C variables.
This patch fixes this issue by renaming "Register" to "PciRegister".
Lv Zheng.

Signed-off-by: Lv Zheng <lv.zheng@intel.com>
ACPI: Clean up AcpiOsMap/UnmapMemory() to eliminate __iomem.

ACPICA doesn't include protections around address space checking, Linux
build tests always complain increased sparse warnings around ACPICA
internal AcpiOsMap/UnmapMemory() invocations.  This patch tries to fix
this issue permanently.

There are 2 choices left for us to solve this issue:
 1. Add __iomem address space awareness into ACPICA.
 2. Remove sparse checker of __iomem from ACPICA source code.

This patch chooses solution 2, because:
 1.  Most of the AcpiOsMap/UnmapMemory() invocations are used for ACPICA.
     table mappings, which in fact are not IO addresses.
 2.  The only IO addresses usage is for "system memory space" mapping code in:
      exregion.c
      evrgnini.c
      exregion.c
    The mapped address is accessed in the handler of "system memory space"
    - AcpiExSystemMemorySpaceHandler().  This function in fact can be
    changed to invoke AcpiOsRead/WriteMemory() so that __iomem can
    always be type-casted in the OSL layer.

According to the above investigation, we drew the following conclusion:
It is not a good idea to introduce __iomem address space awareness into
ACPICA mostly in order to protect non-IO addresses.

We can simply remove __iomem for AcpiOsMap/UnmapMemory() to remove
__iomem checker for ACPICA code. Then we need to enforce external usages
to invoke other APIs that are aware of __iomem address space.

This patch thus performs cleanups in this way:
 1. Add Linux specific acpi_os_map/unmap_iomem() to be invoked by
    non-ACPICA code. This function is not included in this ACPICA patch.
 2. Remove __iomem from AcpiOsMap/UnmapMemory().

Signed-off-by: Lv Zheng <lv.zheng@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tables: Merge DMAR table structure updates.

This patch back ports the following Linux commit with sligh modification to
improve portability:
  Author: David Woodhouse <David.Woodhouse@intel.com>
  Subject: iommu/vt-d: Add ACPI namespace device reporting structures

Signed-off-by: Lv Zheng <lv.zheng@intel.com>
Events: Fix edge-triggered GPE by disabling before acknowledging it.

Due to ACPI specificiation 5, chapter 5.6.4 General-Purpose Event Hnadling,
OSPMs need to disable GPE before clearing the status bit for edge-triggered
GPEs. Lv Zheng.

Signed-off-by: Lv Zheng <lv.zheng@intel.com>