diff options
| author | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2021-03-21 19:18:43 +0200 |
|---|---|---|
| committer | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2021-03-31 13:43:21 +0300 |
| commit | 86eb19ec6813a15cb4e25797581f7f85be9e1056 (patch) | |
| tree | 1341fae94906eac685bc0b32cfa7ec860762f3c0 /projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml | |
| parent | 6e035e53e0223ad7f9a1dec426b2d07f22d6d251 (diff) | |
linux: mm: Triage non-applicable BSP 4.1.x display commits as Abandoned tasks
Move display-related BSP 4.1.x upport candidates that are considered not
to be applicable to upstream to abandoned tasks. This allows grouping
commits logically, providing more detailed comments than the non-target
file.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml')
| -rw-r--r-- | projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml b/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml new file mode 100644 index 0000000..6e39b5a --- /dev/null +++ b/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml @@ -0,0 +1,16 @@ +title: "BSP 4.1.x upport: r8a779xx-ulcb: Fix source clock for DU" +team: MM +key: 194edb13-53ca-436d-aa57-7b56a38c2b68 +status: Abandoned +assignee: Laurent + +bsp41x: + - ac9c016b8ed5d22c76d1caa389a2ce9895ddbbd3 # arm64: dts: r8a77965-m3nulcb: Fix source clock for DU + - dcd9de3348cb79719c79eef6f7eb98b86ec5a8dc # arm64: dts: r8a7796-m3ulcb: Fix souce clock for DU + - 0dd514568ab43a3dbb12d6841190062f459f0705 # arm64: dts: r8a7795-h3ulcb: Fix souce clock for DU + - 95d2ee008fb96ac8def7471a4870a16f8bbf2f32 # arm64: dts: r8a7795-h3ulcb: Fix source clock for DU2 + +comments: + - These commits are workarounds, as stated in the commit messages. If the + issue is still present, it should be addressed in the clk-versaclock5 + driver. More information is needed about what is broken. |