summaryrefslogtreecommitdiff
path: root/projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml')
-rw-r--r--projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml14
1 files changed, 14 insertions, 0 deletions
diff --git a/projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml b/projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml
new file mode 100644
index 0000000..0513d20
--- /dev/null
+++ b/projects/linux/mm/bsp41x_rcar-du-Handle-hotplug-during-suspend.yaml
@@ -0,0 +1,14 @@
+title: "BSP 4.1.x upport: rcar-du: Handle hotplug during suspend"
+team: MM
+key: 2eb2db24-8994-4ef8-aad4-be0bf37867ad
+status: New
+
+bsp41x:
+ - 7ec9182a4daa4f44db1061d36425f9347d898da7 # drm: rcar-du: Add hot plug event function at resume
+
+comments:
+ - The BSP commit seems to be have been developed to handle hotplug events that
+ occurred during system suspend, and thus didn't generate any interrupt. This
+ needs to be tested first.
+ - Most drivers are expected to be affected by this issue, a solution in the
+ DRM core may be best.