Method test regression - bisected

[Jeffrey Hugo]

Started seeing several failures while validating _CRS as part of the 
method test -

PASSED: Test 17, \_SB_.UAR2._CRS (QWORD Address Space Descriptor) looks 
sane.
FAILED [MEDIUM] Method_CRS64BitQWordAddrSpaceLengthInvalid: Test 17,
\_SB_.AHC0._CRS QWORD Address Space Descriptor length 0x200 does not 
match the
difference between the minimum and maximum address ranges
0xff88000000-0xffffffffffffffff.

ADVICE: See section '6.4.3.5 Address Space Resource Descriptors' table 
6-179 of
the ACPI specification for more details about how the _MIF, _MAF and memory
range and granularity rules apply. Typically the kernel does not care about
these being correct, so this is a minor issue.

I bisected the issue to -

ACPICA: Update to version 20170629
Changes in this release of ACPICA are detailed at the following
link on the ACPICA developer mailing list:

https://lists.acpica.org/pipermail/devel/2017-June/001333.html

Signed-off-by: Colin Ian King <colin.king at canonical.com>
Acked-by: Ivan Hu <ivan.hu at canonical.com>
Acked-by: Alex Hung <alex.hung at canonical.com>

Using acpi_call [1] I see that the failing _CRS methods return the 
expected values (ie the valid and expected max address)

I'll try to dig in more as time permits, but if anyone has some 
pointers, I'd appreciate it.

[1] https://github.com/mkottman/acpi_call
-- 
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm 
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.