dri-devel July 2018

dri-devel@lists.freedesktop.org

277 participants
1883 discussions

[PATCH v5 00/40] drm/i915: Implement HDCP2.2
by Ramalingam C 12 Jul '18

12 Jul '18

The sequence for HDCP2.2 authentication and encryption is implemented in I915. Encoder specific implementations are moved into hdcp_shim. Intel HWs supports HDCP2.2 through ME FW. Hence this series introduces a client driver for mei bus, so that for HDCP2.2 authentication, HDCP2.2 stack in I915 can avail the services from ME FW. DRM_I915 selects INTEL_MEI_HDCP, which selects INTEL_MEI_ME and INTEL_MEI. If we are interested in disabling the MEI_HDCP and MEI Bus then we need an option to disable the HDCP2.2 in I915 (like DRM_I915_HDCP2.2!?). Till then they are binded. Userspace interface remains unchanged as version agnostic. When userspace request for HDCP enable, Kernel will detect the HDCP source and sink's HDCP version(1.4/2.2)capability and enable the best capable version for that combination. This series enables the HDCP2.2 for Type0 content streams. Thanks a lot for Daniel vetter for reviewing v4. Major Changes in v5: - Component is used for I915-MEI HDCP interface [Daniel]. - Patches are restructured for bisecting. - Lookup tables are used for DP and HDMI HDCP2.2 messages [Daniel]. GMBus changes are added here for completeness of the series. They are in review at https://patchwork.freedesktop.org/series/41632/ also. Complete series is hosted at https://github.com/ramalingampc2008/drm-tip.git hdcp2_2_v5 Ramalingam C (39): drm: hdcp2.2 authentication msg definitions drm: HDMI and DP specific HDCP2.2 defines linux/mei: Header for mei_hdcp driver interface drm/i915: wrapping all hdcp var into intel_hdcp drm/i915: Define HDCP2.2 related variables drm/i915: Define Intel HDCP2.2 registers drm/i915: Initialize HDCP2.2 and its MEI interface drm/i915: Schedule hdcp_check_link in _intel_hdcp_enable drm/i915: Pullout the bksv read and validation drm/i915: Enable superior HDCP ver that is capable drm/i915: Enable HDCP1.4 incase of HDCP2.2 failure drm/i915: Implement HDCP2.2 Enable and Disable drm/i915: Enable and Disable HDCP2.2 port encryption drm/i915: Implement HDCP2.2 receiver authentication drm/i915: Implement HDCP2.2 repeater authentication drm/i915: Implement HDCP2.2 link integrity check drm/i915: Handle HDCP2.2 downstream topology change drm/i915: hdcp_check_link only on CP_IRQ drm/i915: Check HDCP 1.4 and 2.2 link on CP_IRQ drm/i915/gmbus: Increase the Bytes per Rd/Wr Op drm/i915/gmbus: Enable burst read drm/i915: Implement the HDCP2.2 support for DP drm/i915: Implement the HDCP2.2 support for HDMI drm/i915: Add HDCP2.2 support for DP connectors drm/i915: Add HDCP2.2 support for HDMI connectors misc/mei/hdcp: Client driver for HDCP application misc/mei/hdcp: Component framework for I915 Interface misc/mei/hdcp: Define ME FW interface for HDCP2.2 misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session misc/mei/hdcp: Verify Receiver Cert and prepare km misc/mei/hdcp: Verify H_prime misc/mei/hdcp: Store the HDCP Pairing info misc/mei/hdcp: Initiate Locality check misc/mei/hdcp: Verify L_prime misc/mei/hdcp: Prepare Session Key misc/mei/hdcp: Repeater topology verification and ack misc/mei/hdcp: Verify M_prime misc/mei/hdcp: Enabling the HDCP authentication misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Tomas Winkler (1): mei: bus: whitelist hdcp client drivers/gpu/drm/i915/Kconfig | 1 + drivers/gpu/drm/i915/i915_drv.h | 5 + drivers/gpu/drm/i915/i915_reg.h | 34 + drivers/gpu/drm/i915/intel_display.c | 7 +- drivers/gpu/drm/i915/intel_dp.c | 345 ++++++++- drivers/gpu/drm/i915/intel_drv.h | 88 ++- drivers/gpu/drm/i915/intel_hdcp.c | 1289 ++++++++++++++++++++++++++++++++-- drivers/gpu/drm/i915/intel_hdmi.c | 190 ++++- drivers/gpu/drm/i915/intel_i2c.c | 71 +- drivers/misc/mei/Kconfig | 7 + drivers/misc/mei/Makefile | 2 + drivers/misc/mei/bus-fixup.c | 16 + drivers/misc/mei/hdcp/Makefile | 6 + drivers/misc/mei/hdcp/mei_hdcp.c | 862 +++++++++++++++++++++++ drivers/misc/mei/hdcp/mei_hdcp.h | 408 +++++++++++ include/drm/drm_dp_helper.h | 51 ++ include/drm/drm_hdcp.h | 232 ++++++ include/drm/i915_component.h | 88 +++ include/linux/mei_hdcp.h | 100 +++ 19 files changed, 3710 insertions(+), 92 deletions(-) create mode 100644 drivers/misc/mei/hdcp/Makefile create mode 100644 drivers/misc/mei/hdcp/mei_hdcp.c create mode 100644 drivers/misc/mei/hdcp/mei_hdcp.h create mode 100644 include/linux/mei_hdcp.h -- 2.7.4

6 69

[PATCH] i915/intel_tv_get_modes: fix strncpy truncation warning
by Dominique Martinet 12 Jul '18

12 Jul '18

This is effectively no-op as the next line writes a nul at the final byte of the buffer, so copying one letter less does not change the behaviour. Signed-off-by: Dominique Martinet <asmadeus(a)codewreck.org> --- gcc 8 gives the following warning, which I am not sure why is treated as error for this file, thus making me fix it: drivers/gpu/drm/i915/intel_tv.c: In function ‘intel_tv_get_modes’: drivers/gpu/drm/i915/intel_tv.c:1358:3: error: ‘strncpy’ specified bound 32 equals destination size [-Werror=stringop-truncation] strncpy(mode_ptr->name, input->name, DRM_DISPLAY_MODE_LEN); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors Also, as a side note, while checking if this was already sent I stumbled uppon this: https://lists.freedesktop.org/archives/intel-gfx/2018-July/170638.html ([Intel-gfx] [PATCH i-g-t 6/7] Fix truncate string in the strncpy) which replaces strncpy(dest, src, sizeof(dest)) by strncpy(dest, src, strlen(dest))... This isn't for linux but this looks like a pretty bad idea to me... (I'm not on the list to reply there, sorry) drivers/gpu/drm/i915/intel_tv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/intel_tv.c b/drivers/gpu/drm/i915/intel_tv.c index b55b5c157e38..f5614d07b10d 100644 --- a/drivers/gpu/drm/i915/intel_tv.c +++ b/drivers/gpu/drm/i915/intel_tv.c @@ -1355,7 +1355,7 @@ intel_tv_get_modes(struct drm_connector *connector) mode_ptr = drm_mode_create(connector->dev); if (!mode_ptr) continue; - strncpy(mode_ptr->name, input->name, DRM_DISPLAY_MODE_LEN); + strncpy(mode_ptr->name, input->name, DRM_DISPLAY_MODE_LEN - 1); mode_ptr->name[DRM_DISPLAY_MODE_LEN - 1] = '\0'; mode_ptr->hdisplay = hactive_s; -- 2.17.1

3 8

[PATCH V4 0/4] Add infrastructure for vblank and page flip events in vkms
by Rodrigo Siqueira 12 Jul '18

12 Jul '18

Currently, we are working to make VKMS pass in the kms_flip test (IGT). As a result, we made a series of changes in the module with the goal to meet some of the necessary steps required by kms_flip. This patchset comprises all the modifications needed to make kms_flip partially pass. Finally, this patchset is based on: - [PATCH V2 0/5] drm/vkms: Updates to meet basic kms_flip requirements (https://www.spinics.net/lists/dri-devel/msg180544.html) - [PATCH V3] drm/vkms: Add vblank events simulated by hrtimers (https://www.spinics.net/lists/dri-devel/msg182600.html) Rodrigo Siqueira (4): drm/vkms: Add dumb operations drm/vkms: Add framebuffer and plane helpers drm/vkms: Add connectors helpers drm/vkms: Add vblank events simulated by hrtimers drivers/gpu/drm/vkms/Makefile | 2 +- drivers/gpu/drm/vkms/vkms_crtc.c | 95 +++++++++++++++ drivers/gpu/drm/vkms/vkms_drv.c | 28 ++++- drivers/gpu/drm/vkms/vkms_drv.h | 47 ++++++++ drivers/gpu/drm/vkms/vkms_gem.c | 179 +++++++++++++++++++++++++++++ drivers/gpu/drm/vkms/vkms_output.c | 20 ++++ drivers/gpu/drm/vkms/vkms_plane.c | 11 ++ 7 files changed, 375 insertions(+), 7 deletions(-) create mode 100644 drivers/gpu/drm/vkms/vkms_gem.c -- 2.18.0

2 5

[PATCH] ARM: dts: imx6sl: Add vivante gpu nodes
by Leonard Crestez 12 Jul '18

12 Jul '18

The imx6sl soc has gpu_2d and gpu_vg, no 3d support: etnaviv-gpu 2200000.gpu: model: GC320, revision: 5007 etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 The IP blocks are close enough to supported hardware that they "just work" with etnaviv and x11. Signed-off-by: Leonard Crestez <leonard.crestez(a)nxp.com> --- arch/arm/boot/dts/imx6sl.dtsi | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) Tested by using yocto fsl community bsp built in "mainline" mode. This patch makes x11 start up and turning on drm.debug shows that the etnaviv driver is being used. I don't know if such a patch requires much more testing: all it really does is "describe the hardware". Patch is against shawguo/imx/dt, it depends on newly accepted commit 13211eec7b0e ("ARM: dts: imx6sl: Convert gpc to new bindings") This is only because of the way it references the PU power domain. diff --git a/arch/arm/boot/dts/imx6sl.dtsi b/arch/arm/boot/dts/imx6sl.dtsi index a6bc21433839..49a56b4fd393 100644 --- a/arch/arm/boot/dts/imx6sl.dtsi +++ b/arch/arm/boot/dts/imx6sl.dtsi @@ -130,10 +130,30 @@ cache-level = <2>; arm,tag-latency = <4 2 3>; arm,data-latency = <4 2 3>; }; + gpu_2d: gpu@2200000 { + compatible = "vivante,gc"; + reg = <0x02200000 0x4000>; + interrupts = <0 10 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clks IMX6SL_CLK_MMDC_ROOT>, + <&clks IMX6SL_CLK_GPU2D_OVG>; + clock-names = "bus", "core"; + power-domains = <&pd_pu>; + }; + + gpu_vg: gpu@2204000 { + compatible = "vivante,gc"; + reg = <0x02204000 0x4000>; + interrupts = <0 11 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clks IMX6SL_CLK_MMDC_ROOT>, + <&clks IMX6SL_CLK_GPU2D_OVG>; + clock-names = "bus", "core"; + power-domains = <&pd_pu>; + }; + aips1: aips-bus@2000000 { compatible = "fsl,aips-bus", "simple-bus"; #address-cells = <1>; #size-cells = <1>; reg = <0x02000000 0x100000>; -- 2.17.1

3 2

[PATCH] drm/client: Fix double free in error path
by Noralf Trønnes 12 Jul '18

12 Jul '18

This fixes a static checker warning: drivers/gpu/drm/drm_client.c:289 drm_client_buffer_create() error: double free of 'buffer' drm_client_buffer_delete() frees the buffer so remove the extra free. Fixes: c76f0f7cb546 ("drm: Begin an API for in-kernel clients") Reported-by: Dan Carpenter <dan.carpenter(a)oracle.com> Cc: Daniel Vetter <daniel.vetter(a)ffwll.ch> Signed-off-by: Noralf Trønnes <noralf(a)tronnes.org> --- drivers/gpu/drm/drm_client.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/drm_client.c b/drivers/gpu/drm/drm_client.c index 9b142f58d489..83b294ae3e4e 100644 --- a/drivers/gpu/drm/drm_client.c +++ b/drivers/gpu/drm/drm_client.c @@ -242,8 +242,10 @@ drm_client_buffer_create(struct drm_client_dev *client, u32 width, u32 height, u dumb_args.height = height; dumb_args.bpp = drm_format_plane_cpp(format, 0) * 8; ret = drm_mode_create_dumb(dev, &dumb_args, client->file); - if (ret) - goto err_free; + if (ret) { + kfree(buffer); + return ERR_PTR(ret); + } buffer->handle = dumb_args.handle; buffer->pitch = dumb_args.pitch; @@ -276,8 +278,6 @@ drm_client_buffer_create(struct drm_client_dev *client, u32 width, u32 height, u err_delete: drm_client_buffer_delete(buffer); -err_free: - kfree(buffer); return ERR_PTR(ret); } -- 2.15.1

2 1

[PATCH] drm: mali-dp: Set encoder possible_clones
by Alexandru Gheorghe 12 Jul '18

12 Jul '18

Set possible_clones field to report that the writeback connector and the one driving the display could be enabled at the same time. Signed-off-by: Alexandru Gheorghe <alexandru-cosmin.gheorghe(a)arm.com> --- drivers/gpu/drm/arm/malidp_drv.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/gpu/drm/arm/malidp_drv.c b/drivers/gpu/drm/arm/malidp_drv.c index 5b72605..3664da9 100644 --- a/drivers/gpu/drm/arm/malidp_drv.c +++ b/drivers/gpu/drm/arm/malidp_drv.c @@ -616,6 +616,8 @@ static int malidp_bind(struct device *dev) struct malidp_hw_device *hwdev; struct platform_device *pdev = to_platform_device(dev); struct of_device_id const *dev_id; + struct drm_encoder *encoder; + int num_encoders = 0; /* number of lines for the R, G and B output */ u8 output_width[MAX_OUTPUT_CHANNELS]; int ret = 0, i; @@ -737,6 +739,14 @@ static int malidp_bind(struct device *dev) goto bind_fail; } + list_for_each_entry(encoder, &drm->mode_config.encoder_list, head) { + num_encoders++; + } + + list_for_each_entry(encoder, &drm->mode_config.encoder_list, head) { + encoder->possible_clones = (1 << num_encoders) - 1; + } + ret = malidp_irq_init(pdev); if (ret < 0) goto irq_init_fail; -- 2.7.4

3 3

[PATCH] drm/probe-helper: Fix modes reporting for writeback connector
by Alexandru Gheorghe 12 Jul '18

12 Jul '18

Writeback connector is reported as disconnected, currently this causes the setting of the edid property to null and then exit. In order to properly get the modes for writeback we need to add an exception when connector type is DRM_MODE_CONNECTOR_WRITEBACK. Signed-off-by: Alexandru Gheorghe <alexandru-cosmin.gheorghe(a)arm.com> --- drivers/gpu/drm/drm_probe_helper.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_probe_helper.c b/drivers/gpu/drm/drm_probe_helper.c index 52774339..c7bdbe2 100644 --- a/drivers/gpu/drm/drm_probe_helper.c +++ b/drivers/gpu/drm/drm_probe_helper.c @@ -472,7 +472,8 @@ int drm_helper_probe_single_connector_modes(struct drm_connector *connector, dev->mode_config.poll_running = drm_kms_helper_poll; - if (connector->status == connector_status_disconnected) { + if (connector->status == connector_status_disconnected && + connector->connector_type != DRM_MODE_CONNECTOR_WRITEBACK) { DRM_DEBUG_KMS("[CONNECTOR:%d:%s] disconnected\n", connector->base.id, connector->name); drm_mode_connector_update_edid_property(connector, NULL); -- 2.7.4

3 3

[PATCH v2] drm: Replace NULL with error value in drm_prime_pages_to_sg
by Oleksandr Andrushchenko 12 Jul '18

12 Jul '18

From: Oleksandr Andrushchenko <oleksandr_andrushchenko(a)epam.com> Dan Carpenter has reported that there is the following static checker warning: drivers/gpu/drm/drm_prime.c:317 drm_gem_map_dma_buf() warn: 'sgt' can also be NULL 314 sgt = obj->dev->driver->gem_prime_get_sg_table(obj); 315 316 if (!IS_ERR(sgt)) { 317 if (!dma_map_sg_attrs(attach->dev, sgt->sgl, sgt->nents, dir, Problematic functions are xen_drm_front_gem_get_sg_table and drm_gem_cma_prime_get_sg_table. Fix those by replacing NULL with error value. Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko(a)epam.com> Reported-by: Dan Carpenter <dan.carpenter(a)oracle.com> --- drivers/gpu/drm/drm_gem_cma_helper.c | 2 +- drivers/gpu/drm/xen/xen_drm_front_gem.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_gem_cma_helper.c b/drivers/gpu/drm/drm_gem_cma_helper.c index 80a5115c3846..ce868ce288fb 100644 --- a/drivers/gpu/drm/drm_gem_cma_helper.c +++ b/drivers/gpu/drm/drm_gem_cma_helper.c @@ -436,7 +436,7 @@ struct sg_table *drm_gem_cma_prime_get_sg_table(struct drm_gem_object *obj) sgt = kzalloc(sizeof(*sgt), GFP_KERNEL); if (!sgt) - return NULL; + return ERR_PTR(-ENOMEM); ret = dma_get_sgtable(obj->dev->dev, sgt, cma_obj->vaddr, cma_obj->paddr, obj->size); diff --git a/drivers/gpu/drm/xen/xen_drm_front_gem.c b/drivers/gpu/drm/xen/xen_drm_front_gem.c index c85bfe7571cb..47ff019d3aef 100644 --- a/drivers/gpu/drm/xen/xen_drm_front_gem.c +++ b/drivers/gpu/drm/xen/xen_drm_front_gem.c @@ -179,7 +179,7 @@ struct sg_table *xen_drm_front_gem_get_sg_table(struct drm_gem_object *gem_obj) struct xen_gem_object *xen_obj = to_xen_gem_obj(gem_obj); if (!xen_obj->pages) - return NULL; + return ERR_PTR(-ENOMEM); return drm_prime_pages_to_sg(xen_obj->pages, xen_obj->num_pages); } -- 2.17.1

3 5

[Bug 106258] AMD Xorg start failes with non-4K page sizes
by bugzilla-daemon＠freedesktop.org 12 Jul '18

12 Jul '18

https://bugs.freedesktop.org/show_bug.cgi?id=106258 Bug ID: 106258 Summary: AMD Xorg start failes with non-4K page sizes Product: DRI Version: unspecified Hardware: PowerPC OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktop(a)bluematt.me Have two nearly-identical boxes, both running Debian testing with a 4.16 kernel, only major difference is one is configured with a 4k page size, one with Debian's default 64K page size (on PPC64LE). This results in a corrupted output when running X (with a non-corrupt mouse overlayed on top) and the following WARN in dmesg: [ 33.990146] WARNING: CPU: 8 PID: 1401 at /build/linux-z743uR/linux-4.16/drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c:326 amdgpu_sa_bo_new+0x630/0x6b0 [amdgpu] [ 33.990148] Modules linked in: ext4 crc16 mbcache jbd2 fscrypto amdgpu chash evdev ast gpu_sched ttm snd_hda_codec_hdmi drm_kms_helper snd_hda_intel ghash_generic snd_hda_codec gf128mul drm ctr snd_hda_core snd_hwdep cbc sg snd_pcm vmx_crypto drm_panel_orientation_quirks syscopyarea ofpart snd_timer sysfillrect ipmi_powernv sysimgblt snd powernv_flash ipmi_devintf fb_sys_fops mtd ipmi_msghandler i2c_algo_bit opal_prd soundcore at24 ip_tables x_tables autofs4 btrfs crc32c_generic xor zstd_decompress zstd_compress xxhash raid6_pq ecb xts algif_skcipher af_alg hid_generic usbhid hid sd_mod dm_crypt dm_mod xhci_pci xhci_hcd mpt3sas usbcore tg3 raid_class scsi_transport_sas libphy usb_common [ 33.990187] CPU: 8 PID: 1401 Comm: gnome-shell Not tainted 4.16.0-trunk-powerpc64le #1 Debian 4.16-1~exp1 [ 33.990189] NIP: c00800000e08bfe8 LR: c00800000e0940d4 CTR: 0000000000000000 [ 33.990190] REGS: c000000fac573260 TRAP: 0700 Not tainted (4.16.0-trunk-powerpc64le Debian 4.16-1~exp1) [ 33.990191] MSR: 9000000000029033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 24828848 XER: 20040000 [ 33.990196] CFAR: c00800000e08ba14 SOFTE: 0 GPR00: c00800000e0940d4 c000000fac5734e0 c00800000e2e1c00 c000000ff4673318 GPR04: c000000feedc5a58 0000000009fff138 0000000000000100 0000000ffacf0000 GPR08: 0000000000000010 0000000000100000 0000000000000000 c00800000e246b98 GPR12: 0000000000008000 c00000000fa85800 c000000ff4670000 c000000ff45067e0 GPR16: 00000000000e69ff c000000feedc5a58 00000000fffe2000 ffffffffffffffef GPR20: 0000000009fff138 c000000ff4670000 0000000000000100 0000000000000000 GPR24: 00000000000e69ff 0000000000104a00 c000000ff4673318 0000000116000000 GPR28: c000000ff4670000 0000000000000000 c000000feedc5a58 0000000009fff138 [ 33.990228] NIP [c00800000e08bfe8] amdgpu_sa_bo_new+0x630/0x6b0 [amdgpu] [ 33.990244] LR [c00800000e0940d4] amdgpu_ib_get+0x8c/0x120 [amdgpu] [ 33.990245] Call Trace: [ 33.990261] [c000000fac5734e0] [c00800000e08bae4] amdgpu_sa_bo_new+0x12c/0x6b0 [amdgpu] (unreliable) [ 33.990278] [c000000fac573740] [c00800000e0940d4] amdgpu_ib_get+0x8c/0x120 [amdgpu] [ 33.990298] [c000000fac5737c0] [c00800000e176db8] amdgpu_job_alloc_with_ib+0x90/0x110 [amdgpu] [ 33.990316] [c000000fac573800] [c00800000e090be8] amdgpu_vm_bo_update_mapping+0x360/0x4b0 [amdgpu] [ 33.990332] [c000000fac5738f0] [c00800000e091084] amdgpu_vm_bo_update+0x34c/0x710 [amdgpu] [ 33.990350] [c000000fac573a00] [c00800000e0768b0] amdgpu_gem_va_ioctl+0x5f8/0x620 [amdgpu] [ 33.990356] [c000000fac573b50] [c00800000cd88f48] drm_ioctl_kernel+0xa0/0x140 [drm] [ 33.990361] [c000000fac573ba0] [c00800000cd89424] drm_ioctl+0x1bc/0x4f0 [drm] [ 33.990376] [c000000fac573cf0] [c00800000e050078] amdgpu_drm_ioctl+0x70/0xd0 [amdgpu] [ 33.990379] [c000000fac573d40] [c0000000003dd8dc] do_vfs_ioctl+0xdc/0x8a0 [ 33.990381] [c000000fac573de0] [c0000000003de164] SyS_ioctl+0xc4/0x130 [ 33.990383] [c000000fac573e30] [c00000000000b8e0] system_call+0x58/0x6c [ 33.990384] Instruction dump: [ 33.990386] 7fc3f378 38210260 e8010010 81810008 ea21ff88 ea81ffa0 eac1ffb0 eb41ffd0 [ 33.990389] ebc1fff0 7c0803a6 7d908120 4e800020 <0fe00000> 3bc0ffea 7fc3f378 38210260 [ 33.990393] ---[ end trace 59adbd4db83fa3b4 ]--- [ 33.990397] amdgpu 0000:01:00.0: failed to get a new IB (-22) [ 33.990501] amdgpu 0000:01:00.0: failed to get a new IB (-22) [ 34.007673] amdgpu 0000:01:00.0: failed to get a new IB (-22) -- You are receiving this mail because: You are the assignee for the bug.

1 42

[PATCH v5 0/3] console/fbcon: Add support for deferred console takeover
by Hans de Goede 12 Jul '18

12 Jul '18

Hi All, Here is v5 of my patch-set, to delay fbcon taking over the console (and binding to fbdev devices) until there actually is some text output to the console. This is intended for use with the "quiet" cmdline option, in combination with a bootloader which leaves the vendor's logo / EFI bootgraphics put up by the firmware intact on the EFI framebuffer. The end goal here is a boot where the firmware shows its boot graphics and these stay in place for a couple of seconds until the GUI loads and the GUI then smoothly takes over the framebuffer without any distruptions. Bartlomiej, I believe that this patch-set is ready for merging now and the first patch has Petr's ack, so can we get this merged now? Also please create an inmutable (or topic) branch for this, so that the drm people can merge it into drm-tip for additional testing. Changelog: Changes in v5: -Improve commit message, explain why dummy_con.c is used to detect the first printout, instead of handling this entirely inside the fbcon code (no code changes, only updated the commit message) Changes in v4: -Keep the comments about which fbcon functions need locks in place Changes in v3: -Export is_console_locke() for use in modules (as fbcon may be built as a .ko) -Use WARN_CONSOLE_UNLOCKED() in several places in the fbcon code to assert proper locking (requested by Daniel) -Unregister the fbcon-dummycon-output-notifier on fbcon_exit() (req. by Daniel) -Document the fbcon=nodefer commandline option (req. by Emil) Changes in v2: -Check the whole string when checking for erases in putcs, instead of just the first char -Make dummycon_blank return 1, so that a redraw gets triggered and any text rendered while blanked gets output so that it can trigger a deferred takeover if one is pending Regards, Hans

8 27

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2018