https://bugzilla.kernel.org/show_bug.cgi?id=199475
Bug ID: 199475
Summary: AMDGPU Failed to blank
Product: Drivers
Version: 2.5
Kernel Version: 4.15.18
Hardware: Other
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: andreassx0(a)gmail.…
[View More]com
Regression: No
Im getting this error on starup:
drm:hwss_wait_for_blank_complete [amdgpu] *ERROR* DC: failed to blank crtc!
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
Hi all,
With Wayland compositors and DRM leases, the number of DRM userspace
programs has increased (and will probably continue to increase).
However it's been pretty hard to find good DRM docs for userspace.
The resources currently available are:
- The kernel docs, although only the high level overview is useful to
userspace.
- User-contributed tutorials, like [1] and [2].
- To help userspace understand hardware capabilities and limitations,
I've recently started a DRM database dump …
[View More]project [3].
(Anything else I've missed?)
We still lack docs that describe how to properly use the KMS API and
the KMS properties. There is a deprecated list at [4], and another list
mixed with kernel structs at [5]. This is not great for userspace
developers.
So I wanted to know if there's interest from the kernel community to
maintain documentation for userspace? Or should userspace maintain its
own docs of the kernel API?
I don't know what would be the best place for these docs. If they live
in kernel doc comments, then references to kernel functions and
guidelines for kernel devs will appear (just like in the current docs).
If they live outside of the kernel source code or outside of the kernel
tree, they might get outdated.
Thoughts?
Thanks,
[1]: https://github.com/ascent12/drm_doc
[2]: https://gitlab.freedesktop.org/daniels/kms-quads
[3]: https://drmdb.emersion.fr/
[4]: https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms.html#standard-connect…
[5]: https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms.html#existing-kms-pro…
--
Simon Ser
https://emersion.fr
[View Less]
From: Yongqiang Niu <yongqiang.niu(a)mediatek.com>
This series are based on 5.3-rc1 and provid 32 patch
to support mediatek SOC MT8183
Change since v4
- fix reviewed issue in v4
Change since v3
- fix reviewed issue in v3
- fix type error in v3
- fix conflict with iommu patch
Change since v2
- fix reviewed issue in v2
- add mutex node into dts file
Changes since v1:
- fix reviewed issue in v1
- add dts for mt8183 display nodes
- adjust display clock control flow in patch 22
- add vmap …
[View More]support for mediatek drm in patch 23
- fix page offset issue for mmap function in patch 24
- enable allow_fb_modifiers for mediatek drm in patch 25
Yongqiang Niu (32):
dt-bindings: mediatek: add binding for mt8183 display
dt-bindings: mediatek: add ovl_2l description for mt8183 display
dt-bindings: mediatek: add ccorr description for mt8183 display
dt-bindings: mediatek: add dither description for mt8183 display
dt-bindings: mediatek: add mutex description for mt8183 display
arm64: dts: add display nodes for mt8183
drm/mediatek: add mutex mod into ddp private data
drm/mediatek: add mutex mod register offset into ddp private data
drm/mediatek: add mutex sof into ddp private data
drm/mediatek: add mutex sof register offset into ddp private data
drm/mediatek: split DISP_REG_CONFIG_DSI_SEL setting into another use
case
drm/mediatek: add mmsys private data for ddp path config
drm/mediatek: move rdma sout from mtk_ddp_mout_en into
mtk_ddp_sout_sel
drm/mediatek: add ddp component CCORR
drm/mediatek: add commponent OVL_2L0
drm/mediatek: add component OVL_2L1
drm/mediatek: add component DITHER
drm/mediatek: add gmc_bits for ovl private data
drm/medaitek: add layer_nr for ovl private data
drm/mediatek: add function to background color input select for
ovl/ovl_2l direct link
drm/mediatek: add background color input select function for
ovl/ovl_2l
drm/mediatek: add ovl0/ovl_2l0 usecase
drm/mediatek: distinguish ovl and ovl_2l by layer_nr
drm/mediatek: add clock property check before get it
drm/mediatek: add connection from OVL0 to OVL_2L0
drm/mediatek: add connection from RDMA0 to COLOR0
drm/mediatek: add connection from RDMA1 to DSI0
drm/mediatek: add connection from OVL_2L0 to RDMA0
drm/mediatek: add connection from OVL_2L1 to RDMA1
drm/mediatek: add connection from DITHER0 to DSI0
drm/mediatek: add connection from RDMA0 to DSI0
drm/mediatek: add support for mediatek SOC MT8183
.../bindings/display/mediatek/mediatek,disp.txt | 30 +-
.../bindings/display/mediatek/mediatek,display.txt | 21 ++
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 111 ++++++
drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 79 +++-
drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 27 +-
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 42 ++-
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 410 ++++++++++++++++-----
drivers/gpu/drm/mediatek/mtk_drm_ddp.h | 6 +
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 67 ++++
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 21 ++
drivers/gpu/drm/mediatek/mtk_drm_drv.c | 50 +++
drivers/gpu/drm/mediatek/mtk_drm_drv.h | 3 +
12 files changed, 745 insertions(+), 122 deletions(-)
create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,display.txt
--
1.8.1.1.dirty
[View Less]
This patch originally started out just as a way for platform drivers to
easily add a sysfs group in a race-free way, but thanks to Dmitry's
patch, this series now is for all drivers in the kernel (hey, a unified
driver model works!!!)
I've only converted a few platform drivers here in this series to show
how it works, but other busses can be converted after the first patch
goes into the tree.
Here's the original 00 message, for people to get an idea of what is
going on here:
If a platform …
[View More]driver wants to add a sysfs group, it has to do so in a
racy way, adding it after the driver is bound. To resolve this issue,
have the platform driver core do this for the driver, making the
individual drivers logic smaller and simpler, and solving the race at
the same time.
All of these patches depend on the first patch. I'll take the first one
through my driver-core tree, and any subsystem maintainer can either ack
their individul patch and I will be glad to also merge it, or they can
wait until after 5.4-rc1 when the core patch hits Linus's tree and then
take it, it's up to them.
Thank to Richard Gong for the idea and the testing of the platform
driver patch and to Dmitry Torokhov for rewriting the first patch to
work well for all busses.
-----
V2 - work for all busses and not just platform drivers.
Dmitry Torokhov (1):
driver core: add dev_groups to all drivers
Greg Kroah-Hartman (9):
uio: uio_fsl_elbc_gpcm: convert platform driver to use dev_groups
input: keyboard: gpio_keys: convert platform driver to use dev_groups
input: axp20x-pek: convert platform driver to use dev_groups
firmware: arm_scpi: convert platform driver to use dev_groups
olpc: x01: convert platform driver to use dev_groups
platform: x86: hp-wmi: convert platform driver to use dev_groups
video: fbdev: wm8505fb: convert platform driver to use dev_groups
video: fbdev: w100fb: convert platform driver to use dev_groups
video: fbdev: sm501fb: convert platform driver to use dev_groups
arch/x86/platform/olpc/olpc-xo1-sci.c | 17 ++++------
drivers/base/dd.c | 14 ++++++++
drivers/firmware/arm_scpi.c | 5 +--
drivers/input/keyboard/gpio_keys.c | 13 ++------
drivers/input/misc/axp20x-pek.c | 15 ++-------
drivers/platform/x86/hp-wmi.c | 47 +++++++--------------------
drivers/uio/uio_fsl_elbc_gpcm.c | 23 +++++--------
drivers/video/fbdev/sm501fb.c | 37 +++++----------------
drivers/video/fbdev/w100fb.c | 23 ++++++-------
drivers/video/fbdev/wm8505fb.c | 13 ++++----
include/linux/device.h | 3 ++
11 files changed, 76 insertions(+), 134 deletions(-)
--
2.22.0
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=201505
Bug ID: 201505
Summary: Resume from suspend does not power up the display
Product: Drivers
Version: 2.5
Kernel Version: 4.19
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
…
[View More]Reporter: 0xe2.0x9a.0x9b(a)gmail.com
Regression: No
Resuming the machine from suspend-to-ram no longer restores power to the
display attached to an AMD GPU in Linux 4.19 (assuming the display has switched
to sleep mode by itself because the computer hasn't been in use for a while).
If the display is still powered on when resuming, it ends up blank.
Linux 4.18 did not contain this bug.
Kernel: 4.19
Module: amdgpu
GPU: R9 390
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
The -modesetting ddx has a totally broken idea of how atomic works:
- doesn't disable old connectors, assuming they get auto-disable like
with the legacy setcrtc
- assumes ASYNC_FLIP is wired through for the atomic ioctl
- not a single call to TEST_ONLY
Iow the implementation is a 1:1 translation of legacy ioctls to
atomic, which is a) broken b) pointless.
We already have bugs in both i915 and amdgpu-DC where this prevents us
from enabling neat features.
If anyone ever cares about atomic …
[View More]in X we can easily add a new atomic
level (req->value == 2) for X to get back the shiny toys.
Since these broken versions of -modesetting have been shipping,
there's really no other way to get out of this bind.
References: https://gitlab.freedesktop.org/xorg/xserver/issues/629
References: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/180
Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com>
Cc: Michel Dänzer <michel(a)daenzer.net>
Cc: Alex Deucher <alexdeucher(a)gmail.com>
Cc: Adam Jackson <ajax(a)redhat.com>
Cc: Sean Paul <sean(a)poorly.run>
Cc: David Airlie <airlied(a)linux.ie>
Cc: stable(a)vger.kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter(a)intel.com>
---
drivers/gpu/drm/drm_ioctl.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/drm_ioctl.c b/drivers/gpu/drm/drm_ioctl.c
index 2c120c58f72d..1cb7b4c3c87c 100644
--- a/drivers/gpu/drm/drm_ioctl.c
+++ b/drivers/gpu/drm/drm_ioctl.c
@@ -334,6 +334,9 @@ drm_setclientcap(struct drm_device *dev, void *data, struct drm_file *file_priv)
file_priv->universal_planes = req->value;
break;
case DRM_CLIENT_CAP_ATOMIC:
+ /* The modesetting DDX has a totally broken idea of atomic. */
+ if (strstr(current->comm, "X"))
+ return -EOPNOTSUPP;
if (!drm_core_check_feature(dev, DRIVER_ATOMIC))
return -EOPNOTSUPP;
if (req->value > 1)
--
2.23.0
[View Less]