diff options
author | Heikki Krogerus <heikki.krogerus@linux.intel.com> | 2018-06-21 16:43:17 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-06-25 21:30:12 +0800 |
commit | d2d2e3c46be5d6dd8001d0eebdf7cafb9bc7006b (patch) | |
tree | aee1a8848b304a049284d0a5b7532c7b6f1355f7 /scripts | |
parent | 305886ca87be480ae159908c2affd135c04215cf (diff) | |
download | linux-stable-d2d2e3c46be5d6dd8001d0eebdf7cafb9bc7006b.tar.gz linux-stable-d2d2e3c46be5d6dd8001d0eebdf7cafb9bc7006b.tar.bz2 linux-stable-d2d2e3c46be5d6dd8001d0eebdf7cafb9bc7006b.zip |
acpi: Add helper for deactivating memory region
Sometimes memory resource may be overlapping with
SystemMemory Operation Region by design, for example if the
memory region is used as a mailbox for communication with a
firmware in the system. One occasion of such mailboxes is
USB Type-C Connector System Software Interface (UCSI).
With regions like that, it is important that the driver is
able to map the memory with the requirements it has. For
example, the driver should be allowed to map the memory as
non-cached memory. However, if the operation region has been
accessed before the driver has mapped the memory, the memory
has been marked as write-back by the time the driver is
loaded. That means the driver will fail to map the memory
if it expects non-cached memory.
To work around the problem, introducing helper that the
drivers can use to temporarily deactivate (unmap)
SystemMemory Operation Regions that overlap with their
IO memory.
Fixes: 8243edf44152 ("usb: typec: ucsi: Add ACPI driver")
Cc: stable@vger.kernel.org
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions