aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch
diff options
context:
space:
mode:
authorÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 16:43:19 +0200
committerÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 17:38:18 +0200
commit4f8b350be0b90554c93908458a27be34e8b722ca (patch)
tree8b39d985a590db8cc4eb275d68496cfa212d5ede /target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch
parentb400179ca66647944a26f4d4b7b4fd53a3d2f0d1 (diff)
downloadupstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.gz
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.bz2
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.zip
brcm2708: update to latest patches from RPi foundation
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch')
-rw-r--r--target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch b/target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch
index 04f705ac7d..ea5044c1f7 100644
--- a/target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch
+++ b/target/linux/brcm2708/patches-4.19/950-0580-drm-v3d-Skip-MMU-flush-if-the-device-is-currently-of.patch
@@ -1,7 +1,7 @@
-From 82abb69d99441fde0d3c5400131aa1d1565f2f3d Mon Sep 17 00:00:00 2001
+From f389abea861f9bd3165f98a8d3a1f3407e9fc01a Mon Sep 17 00:00:00 2001
From: Eric Anholt <eric@anholt.net>
Date: Mon, 14 Jan 2019 12:35:43 -0800
-Subject: [PATCH 580/782] drm/v3d: Skip MMU flush if the device is currently
+Subject: [PATCH 580/806] drm/v3d: Skip MMU flush if the device is currently
off.
If it's off, we know it will be reset on poweron, so the MMU won't