projects/linux/mm/done/bsp41x_rcar-du-Force-VGA-connector-status.yaml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

title: "BSP 4.1.x upport: rcar-du: Force VGA connector status"
team: MM
key: 849f1c56-7958-4e2c-bbe4-bc77a29504f1
status: Abandoned
assignee: Laurent

bsp41x:
 - 7e6a484db71f1a0b936d62671ca64c5845bb52b0 # drm/bridge: dumb-vga-dac: Add connector status setting option
 - 100b9c3cdb870203098d2d5e531c208d231ac63f # arm64: dts: r8a77995-draak: Add no use ddc option for VGA connector
 - d713bb0b4dff0d4439d282253232634adb3f023a # arm64: dts: r8a77990-ebisu: Add no use ddc option for VGA connector
 - ca7c7682bb2c4a1fb169465d71233f3bb33daafa # arm64: dts: salvator-common: Add no use ddc option for VGA connector

bsp51x:
 - 08bb2c164a6272712e6a481d46c1e506f4f14f66 # arm64: dts: renesas: salvator-common: Add no use ddc option for VGA connector

comments:
 - The kernel shouldn't cheat when it can't detect the monitor, userspace
   should be able to cope with connectors have an unknown state. If there's a
   valid reason why userspace can't handle these connectors correctly, the
   exact reason and use case needs to be reported, to be discussed with
   upstream.