提交 · 6dab9102dd7b144e5723915438e0d6c473018cd0 · openeuler / Kernel

06 6月, 2019 13 次提交

drm: panel-orientation-quirks: Add quirk for GPD pocket2 · 6dab9102

由 Hans de Goede 提交于 5月 24, 2019

GPD has done it again, make a nice device (good), use way too generic
DMI strings (bad) and use a portrait screen rotated 90 degrees (ugly).

Because of the too generic DMI strings this entry is also doing bios-date
matching, so the gpd_pocket2 data struct may very well need to be updated
with some extra bios-dates in the future.

Changes in v2:
-Add one more known BIOS date to the list of BIOS dates

Cc: Jurgen Kramer <gtmkramer@xs4all.nl>
Reported-by: NJurgen Kramer <gtmkramer@xs4all.nl>
Acked-by: NMaxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: NHans de Goede <hdegoede@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190524125759.14131-1-hdegoede@redhat.com

6dab9102

drm/crc-debugfs: User irqsafe spinlock in drm_crtc_add_crc_entry · 1882018a

由 Daniel Vetter 提交于 6月 05, 2019

We can be called from any context, we need to be prepared.

Noticed this while hacking on vkms, which calls this function from a
normal worker. Which really upsets lockdep.

Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Emil Velikov <emil.velikov@collabora.com>
Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Reviewed-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
Reviewed-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190605194556.16744-1-daniel.vetter@ffwll.ch

1882018a

drm: Ignore drm_gem_vram_mm_funcs in generated documentation · 1a1e5c0f

由 Thomas Zimmermann 提交于 6月 04, 2019

The documentation tools interpret drm_gem_vram_mm_funcs as function and
there appears to be no way of inline-documenting constants. This results
in a warning by 'make htmldocs'. For now, removing drm_gem_vram_mm_funcs
from generated documentation works around the issue.
Signed-off-by: NThomas Zimmermann <tzimmermann@suse.de>
Link: http://patchwork.freedesktop.org/patch/msgid/20190604111330.25324-1-tzimmermann@suse.de
Fixes: 5c9dcacf ("drm: Add default instance for VRAM MM callback functions")
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>

1a1e5c0f

drm/virtio: Fix cache entry creation race. · 5934ce99

由 David Riley 提交于 6月 05, 2019

virtio_gpu_cmd_get_capset would check for the existence of an entry
under lock. If it was not found, it would unlock and call
virtio_gpu_cmd_get_capset to create a new entry. The new entry would
be added it to the list without checking if it was added by another
task during the period where the lock was not held resulting in
duplicate entries.

Compounding this issue, virtio_gpu_cmd_capset_cb would stop iterating
after find the first matching entry. Multiple callbacks would modify
the first entry, but any subsequent entries and their associated waiters
would eventually timeout since they don't become valid, also wasting
memory along the way.
Signed-off-by: NDavid Riley <davidriley@chromium.org>
Link: http://patchwork.freedesktop.org/patch/msgid/20190605234423.11348-3-davidriley@chromium.orgSigned-off-by: NGerd Hoffmann <kraxel@redhat.com>

5934ce99

drm/virtio: Wake up all waiters when capset response comes in. · 676a905b

由 David Riley 提交于 6月 05, 2019

If multiple callers occur simultaneously, wake them all up.
Signed-off-by: NDavid Riley <davidriley@chromium.org>
Link: http://patchwork.freedesktop.org/patch/msgid/20190605234423.11348-2-davidriley@chromium.orgSigned-off-by: NGerd Hoffmann <kraxel@redhat.com>

676a905b

drm/virtio: Ensure cached capset entries are valid before copying. · 7fdf478a

由 David Riley 提交于 6月 05, 2019

virtio_gpu_get_caps_ioctl could return success with invalid data if a
second caller to the function occurred after the entry was created in
virtio_gpu_cmd_get_capset but prior to the virtio_gpu_cmd_capset_cb
callback being called. This could leak contents of memory as well
since the caps_cache allocation is done without zeroing.
Signed-off-by: NDavid Riley <davidriley@chromium.org>
Link: http://patchwork.freedesktop.org/patch/msgid/20190605234423.11348-1-davidriley@chromium.orgSigned-off-by: NGerd Hoffmann <kraxel@redhat.com>

7fdf478a

drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus · 50f9495e

由 Douglas Anderson 提交于 5月 02, 2019

See the PhD thesis in the comments in this patch for details, but to
summarize this adds a hacky "unwedge" feature to the dw_hdmi i2c bus to
workaround what appears to be a hardware errata. This relies on a
pinctrl entry to help change around muxing to perform the unwedge.

NOTE that the specific TV this was tested on was the "Samsung
UN40HU6950FXZA" and the specific port was the "STB" port.
Signed-off-by: NDouglas Anderson <dianders@chromium.org>
Signed-off-by: NSean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20190502225336.206885-2-dianders@chromium.org

50f9495e

dt-bindings: drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus · c6036250

由 Douglas Anderson 提交于 5月 02, 2019

In certain situations it was seen that we could wedge up the DDC bus
on the HDMI adapter on rk3288.  The only way to unwedge was to mux one
of the pins over to GPIO output-driven-low temporarily and then
quickly mux back.  Full details can be found in the patch
("drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus").

Since unwedge requires remuxing the pins, we first need to add to the
bindings so that we can specify what state the pins should be in for
unwedging.
Reviewed-by: NRob Herring <robh@kernel.org>
Signed-off-by: NDouglas Anderson <dianders@chromium.org>
Signed-off-by: NSean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20190502225336.206885-1-dianders@chromium.org

c6036250

drm/r128: drop use of drmP.h · 7f1d39ef