dri-devel June 2018

dri-devel@lists.freedesktop.org

241 participants
1687 discussions

WARNING in ion_dma_buf_begin_cpu_access
by syzbot 10 Jun '18

10 Jun '18

Hello, syzbot found the following crash on: HEAD commit: a16afaf7928b Merge tag 'for-v4.18' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1480e36f800000 kernel config: https://syzkaller.appspot.com/x/.config?x=314f2150f36c16ca dashboard link: https://syzkaller.appspot.com/bug?extid=55b1d9f811650de944c6 compiler: gcc (GCC) 8.0.1 20180413 (experimental) syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=150b8abf800000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1204efdf800000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+55b1d9f811650de944c6(a)syzkaller.appspotmail.com 1965969 pages RAM 0 pages HighMem/MovableOnly 340001 pages reserved ------------[ cut here ]------------ heap->ops->map_kernel should return ERR_PTR on error WARNING: CPU: 1 PID: 4564 at drivers/staging/android/ion/ion.c:148 ion_buffer_kmap_get drivers/staging/android/ion/ion.c:147 [inline] WARNING: CPU: 1 PID: 4564 at drivers/staging/android/ion/ion.c:148 ion_dma_buf_begin_cpu_access+0x48e/0x5a0 drivers/staging/android/ion/ion.c:328 Kernel panic - not syncing: panic_on_warn set ... CPU: 1 PID: 4564 Comm: syz-executor145 Not tainted 4.17.0+ #93 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1b9/0x294 lib/dump_stack.c:113 panic+0x22f/0x4de kernel/panic.c:184 __warn.cold.8+0x163/0x1b3 kernel/panic.c:536 report_bug+0x252/0x2d0 lib/bug.c:186 fixup_bug arch/x86/kernel/traps.c:178 [inline] do_error_trap+0x1fc/0x4d0 arch/x86/kernel/traps.c:296 do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:992 RIP: 0010:ion_buffer_kmap_get drivers/staging/android/ion/ion.c:147 [inline] RIP: 0010:ion_dma_buf_begin_cpu_access+0x48e/0x5a0 drivers/staging/android/ion/ion.c:328 Code: ff 41 bc ea ff ff ff 89 de e8 8e b0 ba fb 84 db 75 a8 e8 b5 af ba fb 48 c7 c7 00 05 68 88 c6 05 39 8d d9 03 01 e8 02 c7 86 fb <0f> 0b eb 8c 48 c7 c7 40 09 ef 88 e8 12 a3 f7 fb e9 15 ff ff ff e8 RSP: 0018:ffff8801ac87fb08 EFLAGS: 00010286 RAX: 0000000000000034 RBX: 0000000000000000 RCX: ffffffff816191ea RDX: 0000000000000000 RSI: ffffffff8161f4e1 RDI: ffff8801ac87f7e0 RBP: ffff8801ac87fb60 R08: ffff8801d8856480 R09: 0000000000000006 R10: ffff8801d8856480 R11: 0000000000000000 R12: 00000000ffffffea R13: ffff8801d977d148 R14: 0000000000000001 R15: ffffffff89724b80 dma_buf_begin_cpu_access+0x7f/0x160 drivers/dma-buf/dma-buf.c:823 dma_buf_ioctl+0x1aa/0x240 drivers/dma-buf/dma-buf.c:314 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x1cf/0x16f0 fs/ioctl.c:684 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701 __do_sys_ioctl fs/ioctl.c:708 [inline] __se_sys_ioctl fs/ioctl.c:706 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x440479 Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 5b 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fff6df8d2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000440479 RDX: 0000000020fd3ff8 RSI: 0000000040086200 RDI: 0000000000000004 RBP: 00000000006cb018 R08: 0000000000000001 R09: 00007fff6df80031 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005 R13: ffffffffffffffff R14: 0000000000000000 R15: 0000000000000000 Dumping ftrace buffer: (ftrace buffer empty) Kernel Offset: disabled Rebooting in 86400 seconds.. --- This bug is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches

1 0

[Bug 199407] New: Radeon night light/redshift flickers
by bugzilla-daemon＠bugzilla.kernel.org 09 Jun '18

09 Jun '18

https://bugzilla.kernel.org/show_bug.cgi?id=199407 Bug ID: 199407 Summary: Radeon night light/redshift flickers Product: Drivers Version: 2.5 Kernel Version: 4.16 Hardware: Other OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: daniel(a)consultd.de Regression: No Hi, am no expert so cannot be more detailed...I love night light (GNOME 3.28/Redshift), am on AMDA9 with Radeon R2 on Ubuntu 18.04 and just reverted back to Kernel 4.14.34 bec with 4.16+ night light flickers when using mouse, but no replicable "system" or cause ... just when moving mouse it often flickers ... not sure if this is already in 4.15, jumped that when moving to Ubuntu 18.04... I have no idea how I can fix this, and by testing it is all fine even with GNOME 3.28 with kernel 4.14.34, also never had issue on this laptop before... some report this problem when using more than one screen, but I have this issue on my one (and only) laptop screen, not having testing dual screen yet Help pls THx Dan -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[Bug 106670] AMD GPU Error, random lockup, Ryzen 2500U Vega 8 GPU
by bugzilla-daemon＠freedesktop.org 09 Jun '18

09 Jun '18

https://bugs.freedesktop.org/show_bug.cgi?id=106670 --- Comment #5 from Jack Wolf <jackwolf2454(a)gmail.com> --- I have same issues. AMD Ryzen 1800x Sapphier Vega 56 amdgpu git kernel 4.17.0 This is what dmesg say from time to time beyond a hang up. [Sa Jun 9 17:34:54 2018] [drm:generic_reg_wait] *ERROR* REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:563 [Sa Jun 9 17:34:54 2018] WARNING: CPU: 14 PID: 175 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:195 generic_reg_wait+0xe2/0x160 [Sa Jun 9 17:34:54 2018] Modules linked in: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) [Sa Jun 9 17:34:54 2018] CPU: 14 PID: 175 Comm: kworker/14:1 Tainted: G O 4.17.0 #1 [Sa Jun 9 17:34:54 2018] Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 4011 04/19/2018 [Sa Jun 9 17:34:54 2018] Workqueue: events dm_irq_work_func [Sa Jun 9 17:34:54 2018] RIP: 0010:generic_reg_wait+0xe2/0x160 [Sa Jun 9 17:34:54 2018] RSP: 0018:ffffba1941e9fa88 EFLAGS: 00010297 [Sa Jun 9 17:34:54 2018] RAX: 0000000000000000 RBX: 0000000000000dad RCX: 0000000000000000 [Sa Jun 9 17:34:54 2018] RDX: 0000000000000000 RSI: ffff985a9ef953b8 RDI: ffff985a9ef953b8 [Sa Jun 9 17:34:54 2018] RBP: 000000000000000a R08: 0000000000000416 R09: 0000000000000002 [Sa Jun 9 17:34:54 2018] R10: 0000000000000002 R11: 0000000000000001 R12: ffff985a8c8b5280 [Sa Jun 9 17:34:54 2018] R13: 00000000000035af R14: 0000000000000010 R15: 0000000000000001 [Sa Jun 9 17:34:54 2018] FS: 0000000000000000(0000) GS:ffff985a9ef80000(0000) knlGS:0000000000000000 [Sa Jun 9 17:34:54 2018] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Sa Jun 9 17:34:54 2018] CR2: 000055e803d42c78 CR3: 00000003c621c000 CR4: 00000000003406e0 [Sa Jun 9 17:34:54 2018] Call Trace: [Sa Jun 9 17:34:54 2018] dce_mi_free_dmif+0x11c/0x1a0 [Sa Jun 9 17:34:54 2018] dce110_reset_hw_ctx_wrap+0x13b/0x1c0 [Sa Jun 9 17:34:54 2018] dce110_apply_ctx_to_hw+0x51/0x8c0 [Sa Jun 9 17:34:54 2018] ? amdgpu_pm_compute_clocks+0xa2/0x570 [Sa Jun 9 17:34:54 2018] dc_commit_state+0x333/0x5f0 [Sa Jun 9 17:34:54 2018] ? set_freesync_on_streams.part.6+0x48/0x240 [Sa Jun 9 17:34:54 2018] ? mod_freesync_set_user_enable+0x116/0x140 [Sa Jun 9 17:34:54 2018] amdgpu_dm_atomic_commit_tail+0x359/0xd10 [Sa Jun 9 17:34:54 2018] ? amdgpu_bo_pin_restricted+0x227/0x2e0 [Sa Jun 9 17:34:54 2018] ? _cond_resched+0x10/0x40 [Sa Jun 9 17:34:54 2018] ? wait_for_completion_timeout+0x2f/0x130 [Sa Jun 9 17:34:54 2018] ? _cond_resched+0x10/0x40 [Sa Jun 9 17:34:54 2018] ? wait_for_completion_interruptible+0x2c/0x160 [Sa Jun 9 17:34:54 2018] ? dm_plane_helper_prepare_fb+0xea/0x290 [Sa Jun 9 17:34:54 2018] commit_tail+0x38/0x70 [Sa Jun 9 17:34:54 2018] drm_atomic_helper_commit+0x11c/0x130 [Sa Jun 9 17:34:54 2018] dm_restore_drm_connector_state+0x100/0x190 [Sa Jun 9 17:34:54 2018] handle_hpd_irq+0x81/0xa0 [Sa Jun 9 17:34:54 2018] dm_irq_work_func+0x49/0x60 [Sa Jun 9 17:34:54 2018] process_one_work+0x1cc/0x3c0 [Sa Jun 9 17:34:54 2018] worker_thread+0x26/0x3f0 [Sa Jun 9 17:34:54 2018] ? trace_event_raw_event_workqueue_execute_start+0xc0/0xc0 [Sa Jun 9 17:34:54 2018] kthread+0x10e/0x130 [Sa Jun 9 17:34:54 2018] ? kthread_create_worker_on_cpu+0x70/0x70 [Sa Jun 9 17:34:54 2018] ret_from_fork+0x22/0x40 [Sa Jun 9 17:34:54 2018] Code: 24 58 48 8b 4c 24 50 89 ee 8b 54 24 48 48 c7 c7 48 1d 4b 9a 44 89 4c 24 08 e8 6b 70 eb ff 41 83 7c 24 20 01 44 8b 4c 24 08 74 02 <0f> 0b 48 83 c4 10 44 89 c8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f [Sa Jun 9 17:34:54 2018] ---[ end trace b03679a92b01c897 ]--- I can't give logs about hangups because i can't enter the machine via ssh. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[drm-intel:topic/core-for-CI 7/8] backtracetest.c:undefined reference to `save_stack_trace'
by kbuild test robot 09 Jun '18

09 Jun '18

tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI head: e2ea2db1734a0e38b89e4d706b5f9ad9f73b1543 commit: 72041f9847abb05b9d4d7dea17631b579191ca99 [7/8] RFC: debugobjects: capture stack traces at _init() time config: m68k-allyesconfig (attached as .config) compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross git checkout 72041f9847abb05b9d4d7dea17631b579191ca99 # save the attached .config to linux build tree GCC_VERSION=7.2.0 make.cross ARCH=m68k All errors (new ones prefixed by >>): kernel/backtracetest.o: In function `backtrace_regression_test': >> backtracetest.c:(.text+0xd8): undefined reference to `save_stack_trace' mm/slub.o: In function `set_track': slub.c:(.text+0x12d2): undefined reference to `save_stack_trace' fs/btrfs/ref-verify.o: In function `btrfs_ref_tree_mod': >> ref-verify.c:(.text+0x92e): undefined reference to `save_stack_trace' lib/debugobjects.o: In function `save_stack.isra.0': debugobjects.c:(.text+0x9f2): undefined reference to `save_stack_trace' --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation

1 0

[PATCH 1/3] Fix checkpatch warnings in goldfishfb.c
by rkir＠google.com 08 Jun '18

08 Jun '18

From: Roman Kiryanov <rkir(a)google.com> Address issues pointed by checkpatch.pl Signed-off-by: Roman Kiryanov <rkir(a)google.com> --- drivers/video/fbdev/goldfishfb.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/video/fbdev/goldfishfb.c b/drivers/video/fbdev/goldfishfb.c index 3b70044773b6..de29c4ff77e5 100644 --- a/drivers/video/fbdev/goldfishfb.c +++ b/drivers/video/fbdev/goldfishfb.c @@ -124,6 +124,7 @@ static int goldfish_fb_check_var(struct fb_var_screeninfo *var, static int goldfish_fb_set_par(struct fb_info *info) { struct goldfish_fb *fb = container_of(info, struct goldfish_fb, fb); + if (fb->rotation != fb->fb.var.rotate) { info->fix.line_length = info->var.xres * 2; fb->rotation = fb->fb.var.rotate; @@ -148,13 +149,14 @@ static int goldfish_fb_pan_display(struct fb_var_screeninfo *var, wait_event_timeout(fb->wait, fb->base_update_count != base_update_count, HZ / 15); if (fb->base_update_count == base_update_count) - pr_err("goldfish_fb_pan_display: timeout waiting for base update\n"); + pr_err("%s: timeout waiting for base update\n", __func__); return 0; } static int goldfish_fb_blank(int blank, struct fb_info *info) { struct goldfish_fb *fb = container_of(info, struct goldfish_fb, fb); + switch (blank) { case FB_BLANK_NORMAL: writel(1, fb->reg_base + FB_SET_BLANK); -- 2.17.0.921.gf22659ad46-goog

3 5

[PATCH 1/3] drm/v3d: Take a lock across GPU scheduler job creation and queuing.
by Eric Anholt 08 Jun '18

08 Jun '18

Between creation and queueing of a job, you need to prevent any other job from being created and queued. Otherwise the scheduler's fences may be signaled out of seqno order. Signed-off-by: Eric Anholt <eric(a)anholt.net> Fixes: 57692c94dcbe ("drm/v3d: Introduce a new DRM driver for Broadcom V3D V3.x+") --- ccing amd-gfx due to interaction of this series with the scheduler. drivers/gpu/drm/v3d/v3d_drv.h | 5 +++++ drivers/gpu/drm/v3d/v3d_gem.c | 11 +++++++++-- 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/v3d/v3d_drv.h b/drivers/gpu/drm/v3d/v3d_drv.h index a043ac3aae98..26005abd9c5d 100644 --- a/drivers/gpu/drm/v3d/v3d_drv.h +++ b/drivers/gpu/drm/v3d/v3d_drv.h @@ -85,6 +85,11 @@ struct v3d_dev { */ struct mutex reset_lock; + /* Lock taken when creating and pushing the GPU scheduler + * jobs, to keep the sched-fence seqnos in order. + */ + struct mutex sched_lock; + struct { u32 num_allocated; u32 pages_allocated; diff --git a/drivers/gpu/drm/v3d/v3d_gem.c b/drivers/gpu/drm/v3d/v3d_gem.c index b513f9189caf..9ea83bdb9a30 100644 --- a/drivers/gpu/drm/v3d/v3d_gem.c +++ b/drivers/gpu/drm/v3d/v3d_gem.c @@ -550,13 +550,16 @@ v3d_submit_cl_ioctl(struct drm_device *dev, void *data, if (ret) goto fail; + mutex_lock(&v3d->sched_lock); if (exec->bin.start != exec->bin.end) { ret = drm_sched_job_init(&exec->bin.base, &v3d->queue[V3D_BIN].sched, &v3d_priv->sched_entity[V3D_BIN], v3d_priv); - if (ret) + if (ret) { + mutex_unlock(&v3d->sched_lock); goto fail_unreserve; + } exec->bin_done_fence = dma_fence_get(&exec->bin.base.s_fence->finished); @@ -570,12 +573,15 @@ v3d_submit_cl_ioctl(struct drm_device *dev, void *data, &v3d->queue[V3D_RENDER].sched, &v3d_priv->sched_entity[V3D_RENDER], v3d_priv); - if (ret) + if (ret) { + mutex_unlock(&v3d->sched_lock); goto fail_unreserve; + } kref_get(&exec->refcount); /* put by scheduler job completion */ drm_sched_entity_push_job(&exec->render.base, &v3d_priv->sched_entity[V3D_RENDER]); + mutex_unlock(&v3d->sched_lock); v3d_attach_object_fences(exec); @@ -615,6 +621,7 @@ v3d_gem_init(struct drm_device *dev) spin_lock_init(&v3d->job_lock); mutex_init(&v3d->bo_lock); mutex_init(&v3d->reset_lock); + mutex_init(&v3d->sched_lock); /* Note: We don't allocate address 0. Various bits of HW * treat 0 as special, such as the occlusion query counters -- 2.17.0

3 9

[PATCH] fb_omap: add gpiolib dependency
by Arnd Bergmann 08 Jun '18

08 Jun '18

Building the omap sub-drivers when CONFIG_GPIOLIB is disabled causes lots of build failures, either from using gpiolib interfaces, or from including the wrong headers: drivers/video/fbdev/omap2/omapfb/displays/encoder-opa362.c: In function 'opa362_enable': drivers/video/fbdev/omap2/omapfb/displays/encoder-opa362.c:101:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c: In function 'panel_dpi_enable': drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c:86:2: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c: In function 'panel_dpi_probe_pdata': drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c:189:23: error: implicit declaration of function 'gpio_to_desc'; did you mean 'irq_to_desc'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c: In function 'panel_dpi_probe_of': drivers/video/fbdev/omap2/omapfb/displays/panel-dpi.c:210:9: error: implicit declaration of function 'devm_gpiod_get_optional'; did you mean 'devm_gpio_request_one'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c: In function 'sharp_ls_enable': drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c:120:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/displays/panel-lgphilips-lb035q02.c: In function 'lb035q02_enable': drivers/video/fbdev/omap2/omapfb/displays/panel-lgphilips-lb035q02.c:170:3: error: implicit declaration of function 'gpiod_set_value_cansleep'; did you mean 'gpio_set_value_cansleep'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/dss/hdmi5.c: In function 'hdmi_probe_of': drivers/video/fbdev/omap2/omapfb/dss/hdmi5.c:584:2: error: implicit declaration of function 'of_node_put'; did you mean 'node_set'? [-Werror=implicit-function-declaration] drivers/video/fbdev/omap2/omapfb/dss/hdmi4.c: In function 'hdmi_probe_of': drivers/video/fbdev/omap2/omapfb/dss/hdmi4.c:554:2: error: implicit declaration of function 'of_node_put'; did you mean 'node_set'? [-Werror=implicit-function-declaration] Rather than fixing up each one individually, this just marks all of it as depending on GPIOLIB. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> --- drivers/video/fbdev/omap2/omapfb/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/omap2/omapfb/Kconfig b/drivers/video/fbdev/omap2/omapfb/Kconfig index e6226aeed17e..3bf154e676d1 100644 --- a/drivers/video/fbdev/omap2/omapfb/Kconfig +++ b/drivers/video/fbdev/omap2/omapfb/Kconfig @@ -5,6 +5,7 @@ menuconfig FB_OMAP2 tristate "OMAP2+ frame buffer support" depends on FB depends on DRM_OMAP = n + depends on GPIOLIB select FB_OMAP2_DSS select OMAP2_VRFB if ARCH_OMAP2 || ARCH_OMAP3 -- 2.9.0

3 3

[PATCH] video/omap: add module license tags
by Arnd Bergmann 08 Jun '18

08 Jun '18

I got a bunch of warnings in a randconfig build: WARNING: modpost: missing MODULE_LICENSE() in drivers/video/fbdev/omap/lcd_ams_delta.o WARNING: modpost: missing MODULE_LICENSE() in drivers/video/fbdev/omap/lcd_inn1510.o WARNING: modpost: missing MODULE_LICENSE() in drivers/video/fbdev/omap/lcd_palmte.o WARNING: modpost: missing MODULE_LICENSE() in drivers/video/fbdev/omap/lcd_palmtt.o These come from an earlier patch of mine that turned all display drivers into separate modules. The fix is to add a MODULE_LICENSE tag. Since I'm doing that, adding a description and author field also makes sense. I went by the authors listed in the comment at the top of each file, but removed Imre's Nokia email address that I assume is not valid any more, since Imre is working at Intel these days. Fixes: 81c44c2b2ce3 ("video/omap: fix modular build") Cc: Imre Deak <imre.deak(a)intel.com> Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> --- drivers/video/fbdev/omap/lcd_ams_delta.c | 3 +++ drivers/video/fbdev/omap/lcd_h3.c | 3 +++ drivers/video/fbdev/omap/lcd_htcherald.c | 4 ++++ drivers/video/fbdev/omap/lcd_inn1510.c | 3 +++ drivers/video/fbdev/omap/lcd_inn1610.c | 3 +++ drivers/video/fbdev/omap/lcd_osk.c | 4 ++++ drivers/video/fbdev/omap/lcd_palmte.c | 3 +++ drivers/video/fbdev/omap/lcd_palmtt.c | 3 +++ drivers/video/fbdev/omap/lcd_palmz71.c | 3 +++ 9 files changed, 29 insertions(+) diff --git a/drivers/video/fbdev/omap/lcd_ams_delta.c b/drivers/video/fbdev/omap/lcd_ams_delta.c index a4ee947006c7..488b3e9a2646 100644 --- a/drivers/video/fbdev/omap/lcd_ams_delta.c +++ b/drivers/video/fbdev/omap/lcd_ams_delta.c @@ -197,3 +197,6 @@ static struct platform_driver ams_delta_panel_driver = { }; module_platform_driver(ams_delta_panel_driver); +MODULE_AUTHOR("Jonathan McDowell <noodles(a)earth.li>"); +MODULE_DESCRIPTION("LCD panel support for the Amstrad E3 (Delta) videophone"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_h3.c b/drivers/video/fbdev/omap/lcd_h3.c index 796f4634c4c6..146dd962c69e 100644 --- a/drivers/video/fbdev/omap/lcd_h3.c +++ b/drivers/video/fbdev/omap/lcd_h3.c @@ -89,3 +89,6 @@ static struct platform_driver h3_panel_driver = { }; module_platform_driver(h3_panel_driver); +MODULE_AUTHOR("Imre Deak"); +MODULE_DESCRIPTION("LCD panel support for the TI OMAP H3 board"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_htcherald.c b/drivers/video/fbdev/omap/lcd_htcherald.c index 9d692f5b8025..db4ff1c6add9 100644 --- a/drivers/video/fbdev/omap/lcd_htcherald.c +++ b/drivers/video/fbdev/omap/lcd_htcherald.c @@ -66,3 +66,7 @@ static struct platform_driver htcherald_panel_driver = { }; module_platform_driver(htcherald_panel_driver); + +MODULE_AUTHOR("Cory Maccarrone"); +MODULE_LICENSE("GPL"); +MODULE_DESCRIPTION("LCD panel support for the HTC Herald"); diff --git a/drivers/video/fbdev/omap/lcd_inn1510.c b/drivers/video/fbdev/omap/lcd_inn1510.c index b284050f5471..8c334858f441 100644 --- a/drivers/video/fbdev/omap/lcd_inn1510.c +++ b/drivers/video/fbdev/omap/lcd_inn1510.c @@ -73,3 +73,6 @@ static struct platform_driver innovator1510_panel_driver = { }; module_platform_driver(innovator1510_panel_driver); +MODULE_AUTHOR("Imre Deak"); +MODULE_DESCRIPTION("LCD panel support for the TI OMAP1510 Innovator board"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_inn1610.c b/drivers/video/fbdev/omap/lcd_inn1610.c index 1841710e796f..9ca17b33d382 100644 --- a/drivers/video/fbdev/omap/lcd_inn1610.c +++ b/drivers/video/fbdev/omap/lcd_inn1610.c @@ -106,3 +106,6 @@ static struct platform_driver innovator1610_panel_driver = { }; module_platform_driver(innovator1610_panel_driver); +MODULE_AUTHOR("Imre Deak"); +MODULE_DESCRIPTION("LCD panel support for the TI OMAP1610 Innovator board"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_osk.c b/drivers/video/fbdev/omap/lcd_osk.c index b0be5771fe90..6545de8f6390 100644 --- a/drivers/video/fbdev/omap/lcd_osk.c +++ b/drivers/video/fbdev/omap/lcd_osk.c @@ -93,3 +93,7 @@ static struct platform_driver osk_panel_driver = { }; module_platform_driver(osk_panel_driver); + +MODULE_LICENSE("GPL"); +MODULE_AUTHOR("Imre Deak"); +MODULE_DESCRIPTION("LCD panel support for the TI OMAP OSK board"); diff --git a/drivers/video/fbdev/omap/lcd_palmte.c b/drivers/video/fbdev/omap/lcd_palmte.c index cef96386cf80..1d442c19799c 100644 --- a/drivers/video/fbdev/omap/lcd_palmte.c +++ b/drivers/video/fbdev/omap/lcd_palmte.c @@ -59,3 +59,6 @@ static struct platform_driver palmte_panel_driver = { }; module_platform_driver(palmte_panel_driver); +MODULE_AUTHOR("Romain Goyet <r.goyet(a)gmail.com>"); +MODULE_DESCRIPTION("LCD panel support for the Palm Tungsten E"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_palmtt.c b/drivers/video/fbdev/omap/lcd_palmtt.c index 627f13dae5ad..0b9f17a0fafe 100644 --- a/drivers/video/fbdev/omap/lcd_palmtt.c +++ b/drivers/video/fbdev/omap/lcd_palmtt.c @@ -72,3 +72,6 @@ static struct platform_driver palmtt_panel_driver = { }; module_platform_driver(palmtt_panel_driver); +MODULE_AUTHOR("Marek Vasut <marek.vasut(a)gmail.com>"); +MODULE_DESCRIPTION("LCD panel support for Palm Tungsten|T"); +MODULE_LICENSE("GPL"); diff --git a/drivers/video/fbdev/omap/lcd_palmz71.c b/drivers/video/fbdev/omap/lcd_palmz71.c index c46d4db1f839..d7071578d70e 100644 --- a/drivers/video/fbdev/omap/lcd_palmz71.c +++ b/drivers/video/fbdev/omap/lcd_palmz71.c @@ -66,3 +66,6 @@ static struct platform_driver palmz71_panel_driver = { }; module_platform_driver(palmz71_panel_driver); +MODULE_AUTHOR("Marek Vasut"); +MODULE_LICENSE("GPL"); +MODULE_DESCRIPTION("LCD panel support for the Palm Zire71"); -- 2.9.0

2 1

[PATCH] MAINTAINERS: make omapfb orphan
by Tomi Valkeinen 08 Jun '18

08 Jun '18

omapfb is not maintained by me anymore, so drop my name from the maintainers, and mark omapfb as orphan. At some point in the future we should mark omapfb as obsolete, but there are still some features supported by omapfb which are not supported by omapdrm, so we're not there yet. Signed-off-by: Tomi Valkeinen <tomi.valkeinen(a)ti.com> --- MAINTAINERS | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 79bb02ff812f..1efa90eeaf5d 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10136,18 +10136,16 @@ F: arch/arm/boot/dts/*am5* F: arch/arm/boot/dts/*dra7* OMAP DISPLAY SUBSYSTEM and FRAMEBUFFER SUPPORT (DSS2) -M: Tomi Valkeinen <tomi.valkeinen(a)ti.com> L: linux-omap(a)vger.kernel.org L: linux-fbdev(a)vger.kernel.org -S: Maintained +S: Orphan F: drivers/video/fbdev/omap2/ F: Documentation/arm/OMAP/DSS OMAP FRAMEBUFFER SUPPORT -M: Tomi Valkeinen <tomi.valkeinen(a)ti.com> L: linux-fbdev(a)vger.kernel.org L: linux-omap(a)vger.kernel.org -S: Maintained +S: Orphan F: drivers/video/fbdev/omap/ OMAP GENERAL PURPOSE MEMORY CONTROLLER SUPPORT -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

2 1

[PULL] drm-intel-next-fixes for drm-next/v4.18
by Jani Nikula 08 Jun '18

08 Jun '18

Hi Dave, these missed the main drm-next pull request. drm-intel-next-fixes-2018-06-08-2: First batch of i915 fixes for v4.18: - gvt fixes that missed v4.17, potentially need to be backported - eDP resolution regression revert - remove broken nv12 special casing - remove stale asserts from find active requests BR, Jani. The following changes since commit 315852b422972e6ebb1dfddaadada09e46a2681a: drm: rcar-du: Fix build failure (2018-05-17 15:03:40 +1000) are available in the git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2018-06-08-2 for you to fetch changes up to 807cba6559cf333a74df1fbd74f0597e8e7fa020: Merge tag 'gvt-fixes-2018-04-19' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2018-06-07 12:06:07 +0300) ---------------------------------------------------------------- First batch of i915 fixes for v4.18: - gvt fixes that missed v4.17, potentially need to be backported - eDP resolution regression revert - remove broken nv12 special casing - remove stale asserts from find active requests ---------------------------------------------------------------- Changbin Du (2): drm/i915/gvt: Fix the validation on size field of dp aux header drm/i915/kvmgt: Check the pfn got from vfio_pin_pages Chris Wilson (2): drm/i915: Nul-terminate legacy debug string drm/i915: Remove stale asserts from i915_gem_find_active_request() Colin Ian King (1): drm/i915/gvt: fix memory leak of a cmd_entry struct on error exit path Jani Nikula (2): Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available." Merge tag 'gvt-fixes-2018-04-19' of https://github.com/intel/gvt-linux into drm-intel-next-fixes Mahesh Kumar (2): drm/i915/icl: fix icl_unmap/map_plls_to_ports drm/i915/icl: Don't update enabled dbuf slices struct until updated in hw Ville Syrjälä (1): drm/i915: Remove bogus NV12 PLANE_COLOR_CTL setup Xiong Zhang (1): drm/i915/gvt: Dereference msi eventfd_ctx when it isn't used anymore Zhenyu Wang (1): Back merge 'drm-intel-fixes' into gvt-fixes drivers/gpu/drm/i915/gvt/cmd_parser.c | 1 + drivers/gpu/drm/i915/gvt/display.h | 2 +- drivers/gpu/drm/i915/gvt/handlers.c | 13 ++++++++---- drivers/gpu/drm/i915/gvt/kvmgt.c | 34 +++++++++++++++++++++++++++++- drivers/gpu/drm/i915/i915_gem.c | 17 +++++++-------- drivers/gpu/drm/i915/intel_ddi.c | 6 ++++-- drivers/gpu/drm/i915/intel_display.c | 7 +------ drivers/gpu/drm/i915/intel_dp.c | 38 +++++----------------------------- drivers/gpu/drm/i915/intel_drv.h | 2 -- drivers/gpu/drm/i915/intel_dsi.c | 2 +- drivers/gpu/drm/i915/intel_dvo.c | 2 +- drivers/gpu/drm/i915/intel_engine_cs.c | 2 +- drivers/gpu/drm/i915/intel_lvds.c | 3 +-- drivers/gpu/drm/i915/intel_panel.c | 6 ------ drivers/gpu/drm/i915/intel_pm.c | 1 - 15 files changed, 66 insertions(+), 70 deletions(-) -- Jani Nikula, Intel Open Source Graphics Center

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2018