dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 76223] New: [radeonsi] luxmark segfault
by bugzilla-daemon＠freedesktop.org 21 Feb '15

21 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=76223 Priority: medium Bug ID: 76223 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] luxmark segfault Severity: normal Classification: Unclassified OS: All Reporter: grantipak(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa ArchLinux x32. mesa-git, llvm-svn, clang-svn, Radeon HD 7950 Luxmark Segmentation fault on mesa OpenCL. (gdb) bt #0 0x08108656 in slg::PathOCLRenderEngine::StopLockLess() () #1 0x080c0ad4 in slg::RenderEngine::Stop() () #2 0x080bab42 in slg::RenderSession::Stop() () #3 0x080bb08e in slg::RenderSession::~RenderSession() () #4 0x080a43ce in LuxMarkApp::Stop() () #5 0x080a4490 in LuxMarkApp::InitRendering(LuxMarkAppMode, char const*) () #6 0x080a535a in LuxMarkApp::SetMode(LuxMarkAppMode) () #7 0x080ac734 in MainWindow::event(QEvent*) () #8 0xb76149a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #9 0xb761b3b3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0xb736e33a in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #11 0xb737166d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #12 0xb7371b7c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #13 0xb739e06e in ?? () from /usr/lib/libQtCore.so.4 #14 0xb698b60e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0xb698b9b8 in ?? () from /usr/lib/libglib-2.0.so.0 #16 0xb698ba78 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #17 0xb739d85f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #18 0xb76c43de in ?? () from /usr/lib/libQtGui.so.4 #19 0xb736cda3 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #20 0xb736d0c9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #21 0xb737285e in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #22 0xb7612e44 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #23 0x0809868a in main () -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 62721] New: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec...
by bugzilla-daemon＠bugzilla.kernel.org 20 Feb '15

20 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=62721 Bug ID: 62721 Summary: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec... Product: Drivers Version: 2.5 Kernel Version: 3.11.4 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 Reporter: egorov_egor(a)bk.ru Regression: No After update kernel to 3.11.4 my system randomize hands: Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000000a2f1 last fence id 0x000000000000a2f0) Oct 08 19:09:32 localhost kernel: Failed to wait GUI idle while programming pipes. Bad things might happen. Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: Saved 27 dwords of commands on ring 0. Oct 08 19:09:33 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:401) RBBM_STATUS=0xD4110140 Oct 08 19:09:33 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:421) RBBM_STATUS=0x90010140 Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:429) RBBM_STATUS=0x10000140 Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:437) RBBM_STATUS=0x10000140 Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: GPU reset succeed Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: ffff880224f0f800 unpin not necessary Oct 08 19:09:39 localhost kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Oct 08 19:09:39 localhost kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing BA17 (len 676, WS 4, PS 0) @ 0xBC1E Oct 08 19:09:39 localhost kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B948 (len 200, WS 0, PS 8) @ 0xB950 Oct 08 19:09:39 localhost kernel: Failed to wait GUI idle while programming pipes. Bad things might happen. Oct 08 19:09:39 localhost kernel: [drm] radeon: 3 quad pipes, 1 z pipes initialized. Oct 08 19:09:40 localhost kernel: Failed to wait MC idle while programming pipes. Bad things might happen. Oct 08 19:09:40 localhost kernel: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: WB enabled Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000000 and cpu addr 0xffff880224965000 Oct 08 19:09:40 localhost kernel: [drm] radeon: ring at 0x0000000010001000 Oct 08 19:09:40 localhost kernel: [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E8)=0xCAFEDEAD) Oct 08 19:09:40 localhost kernel: [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: failed initializing CP (-22). after revert commit cb51bb7107aa040f9779be931e3bd6a7b50e0f69 all works fine. -- You are receiving this mail because: You are watching the assignee of the bug.

1 18

[Bug 43346] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=43346 Summary: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 Product: Drivers Version: 2.5 Kernel Version: 3.2.18 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: bjorn.ottervik(a)gmail.com Regression: No Happens about once a week, but I can't reproduce it at will. X is still running as before, but unbearably slow. GPU is an integrated HD4200 of an AMD 785G ASUS mainboard, model M4A785D-M Pro. [261062.255333] [TTM] Erroneous page count. Leaking pages. [261062.753541] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 [261062.753705] IP: [<ffffffff813f9a71>] ttm_bo_cleanup_memtype_use+0x51/0x80 [261062.753830] PGD 214e12067 PUD 214e64067 PMD 0 [261062.753918] Oops: 0000 [#1] SMP [261062.753981] CPU 0 [261062.754007] Modules linked in: sata_sil [261062.754007] [261062.754007] Pid: 2467, comm: xbmc.bin Not tainted 3.2.18 #1 System manufacturer System Product Name/M4A785D-M PRO [261062.754007] RIP: 0010:[<ffffffff813f9a71>] [<ffffffff813f9a71>] ttm_bo_cleanup_memtype_use+0x51/0x80 [261062.754007] RSP: 0018:ffff88021fbd7c58 EFLAGS: 00010256 [261062.754007] RAX: 0000000000000000 RBX: ffff88003c8c6c48 RCX: ffff8802267f0548 [261062.754007] RDX: 0000000000000000 RSI: ffff88003c8c6ca8 RDI: ffff8802267f0570 [261062.754007] RBP: 0000000000000002 R08: 0000000000000000 R09: ffffffff813f9a41 [261062.754007] R10: 0000000000000039 R11: 0000000000000246 R12: ffff8802267f0548 [261062.754007] R13: ffff8802259853c0 R14: ffff88003c8c6c8c R15: 00000000fffffff2 [261062.754007] FS: 00007fe3f3cba720(0000) GS:ffff88022fc00000(0000) knlGS:0000000000000000 [261062.754007] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [261062.754007] CR2: 0000000000000018 CR3: 0000000214e0d000 CR4: 00000000000006f0 [261062.754007] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [261062.754007] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [261062.754007] Process xbmc.bin (pid: 2467, threadinfo ffff88021fbd6000, task ffff880222120000) [261062.754007] Stack: [261062.754007] ffff88003c8c6c48 ffffffff813fad00 ffff88004421b200 ffff88004421b200 [261062.754007] ffff88021fbd7d74 0000000000000000 ffff880226ff5000 ffff88003c8c6c88 [261062.754007] ffffffff813faaa0 000000000000000a ffff88003c8c6e00 ffff880226ff5000 [261062.754007] Call Trace: [261062.754007] [<ffffffff813fad00>] ? ttm_bo_release+0x260/0x280 [261062.754007] [<ffffffff813faaa0>] ? ttm_bo_delayed_workqueue+0x30/0x30 [261062.754007] [<ffffffff813304e3>] ? kref_put+0x33/0x70 [261062.754007] [<ffffffff813f9ec5>] ? ttm_bo_unref+0x35/0x50 [261062.754007] [<ffffffff8142f902>] ? radeon_bo_unref+0x42/0x80 [261062.754007] [<ffffffff813e4f60>] ? drm_gem_object_ref_bug+0x10/0x10 [261062.754007] [<ffffffff8143fc1f>] ? radeon_gem_object_free+0x1f/0x30 [261062.754007] [<ffffffff813304e3>] ? kref_put+0x33/0x70 [261062.754007] [<ffffffff813e50c8>] ? drm_gem_handle_delete+0xa8/0xf0 [261062.754007] [<ffffffff813e374c>] ? drm_ioctl+0x3ec/0x4a0 [261062.754007] [<ffffffff8132d54d>] ? cpumask_any_but+0x2d/0x40 [261062.754007] [<ffffffff813e55f0>] ? drm_gem_destroy+0x50/0x50 [261062.754007] [<ffffffff810cda5e>] ? tlb_finish_mmu+0xe/0x50 [261062.754007] [<ffffffff810d468b>] ? unmap_region+0x10b/0x150 [261062.754007] [<ffffffff8110a7b6>] ? do_vfs_ioctl+0x96/0x540 [261062.754007] [<ffffffff810d4562>] ? remove_vma+0x52/0x70 [261062.754007] [<ffffffff810d5936>] ? do_munmap+0x2d6/0x360 [261062.754007] [<ffffffff8110aca9>] ? sys_ioctl+0x49/0x80 [261062.754007] [<ffffffff8175e73b>] ? system_call_fastpath+0x16/0x1b [261062.754007] Code: 00 00 00 00 00 00 48 83 7b 60 00 48 8b 4b 08 8b 93 84 00 00 00 74 17 89 d2 48 8d 73 60 48 c1 e2 07 48 8b 44 11 50 48 8d 7c 11 28 <ff> 50 18 c7 83 20 01 00 00 00 00 00 00 48 8d 7b 48 31 c9 31 d2 [261062.754007] RIP [<ffffffff813f9a71>] ttm_bo_cleanup_memtype_use+0x51/0x80 [261062.754007] RSP <ffff88021fbd7c58> [261062.754007] CR2: 0000000000000018 [261062.795877] ---[ end trace 4bb94fa28b7f787a ]--- -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 1

[Bug 44341] New: Radeon HD6990M: HDMI audio output works now! Kernel gives new warning
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44341 Summary: Radeon HD6990M: HDMI audio output works now! Kernel gives new warning Product: Drivers Version: 2.5 Kernel Version: 3.5.0-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: cfroemmel(a)web.de Regression: No Created an attachment (id=75061) --> (https://bugzilla.kernel.org/attachment.cgi?id=75061) kernel's warning It seems that hdmi audio is working now for radeon 69xx series. Thanks for that! It did not on rc3. But there is also a new warning loading the driver that may be interesting. Nevertheless system seems to run good (and with audio!) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 20

[Bug 44831] New: Radeon HD6970: HDMI audio doesn't work
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44831 Summary: Radeon HD6970: HDMI audio doesn't work Product: Drivers Version: 2.5 Kernel Version: 3.5.0-rc7 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: valentyn.pavliuchenko(a)gmail.com Regression: No Created an attachment (id=75441) --> (https://bugzilla.kernel.org/attachment.cgi?id=75441) dmesg Radeon Wiki says that HDMI audio should work with 3.5 kernel, however it doesn't. Sound device exists, but there's no actual sound. Video is ok. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 6

[Bug 44851] New: resume to black screen
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=44851 Summary: resume to black screen Product: Drivers Version: 2.5 Kernel Version: 3.5.0-3 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: energonic(a)gmail.com Regression: No System: iMac 11,2 (mid2010) with AMD radeon 4670. kernel 3.5.0-3 used on ubuntu 12.10. No swap partition. Boot requires nomodeset on kernel command line, else black screen (even for text-only boot. Radeon module disconnects wrong display port). Resume after suspend shows black screen, but reboots using Ctl-Alt-Del, so has resumed from suspend. Suspect kms invoked on resume and radeon disconnects wrong display port. Same behaviour on archlinux using kernel 3.4.4-1. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 12

[Bug 29842] New: Radeon runs very hot
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=29842 Summary: Radeon runs very hot Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: psusi(a)cfl.rr.com Regression: No The newer kernels read the temperature of my Radeon card, and report that it is running at around 80 C on an idle desktop. For comparison, my CPU is only 34 C. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

6 26

[Bug 76487] New: [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array, ARB_framebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes
by bugzilla-daemon＠freedesktop.org 19 Feb '15

19 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=76487 Priority: medium Bug ID: 76487 Assignee: dri-devel(a)lists.freedesktop.org Summary: [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array,ARB_f ramebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kai(a)dev.carbon-project.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 96212 --> https://bugs.freedesktop.org/attachment.cgi?id=96212&action=edit GDB backtrace and register info of the crash For the first time ever, since I'm having a PITCAIRN GPU I was able to run a full Piglit quick test without crashing my X (hooray for that). During the test I came across two similar crashes in "spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5" and "spec/ARB_framebuffer_object/fbo-generatemipmap-3d RGB9_E5" (see the attached GDB backtrace; the backtrace is for spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5", but the second crashed in the same function on the same line and as it's the same format, that is tested, I guess, these are related, if not, I'm happy to provide a backtrace for the second case as well and split the bugs). I can't tell whether this is a regression or not, since this was the first time I was able to run Piglit on this machine without getting a corrupted results file, due to the crash of the X server. My graphics stack is: GPU: "PITCAIRN" (ChipID = 0x6819) Linux: 3.13.6 libdrm: 2.4.52-1 LLVM: SVN:trunk/r204517 libclc: Git:master/1e278a7b04 Mesa: Git:master/4c79f088c0 GLAMOR: Git:master/a4fbc7732a (Standalone) DDX: Git:master/ea6d0affe5 X: 1.15.0-2 Let me know if you need further information. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 60639] New: RV635: Kernel displays black screen when monitor is connect via DisplayPort
by bugzilla-daemon＠bugzilla.kernel.org 17 Feb '15

17 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=60639 Bug ID: 60639 Summary: RV635: Kernel displays black screen when monitor is connect via DisplayPort Product: Drivers Version: 2.5 Kernel Version: 3.10.3 (and earlier) 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 Reporter: kernspam(a)schreib-doch-mal-wieder.de Regression: No When the monitor is connected via DisplayPort I can see grub but once the kernel takes over, the screen goes black. When the same monitor is connected via DVI everything works. Adding the kernel option "video=DP-1:1920x1200@75" makes at least the kernel messages and virtual consoles work. However, when X starts the screen goes black again. This might be related to the bug reported here: https://bugzilla.novell.com/show_bug.cgi?id=752593 Modeline from EDID: Detailed mode: Clock 154.000 MHz, 518 mm x 324 mm 1920 1968 2000 2080 hborder 0 1200 1203 1209 1235 vborder 0 +hsync -vsync Monitor ranges (GTF): 50-61Hz V, 30-83kHz H, max dotclock 170MHz Kernel 3.10.3 (but also tested with 3.9.x and 3.8.x) Graphic chip: ATI Mobility FireGL V5700 (the second intel chip should be disabled) -- You are receiving this mail because: You are watching the assignee of the bug.

1 24

[PATCH 00/12] Renesas R-Car DU HDMI support
by Laurent Pinchart 09 Feb '15

09 Feb '15

Hello, This patch set adds support for the HDMI output port present on the Renesas Koelsch board. Doing so requires two components, a driver for the external ADV7511W HDMI encoder, and support for HDMI encoders in the DU driver. The HDMI encoder drivers uses the DRM slave encoder framework and the component framework to communicate with the DU driver. The DT bindings are based on the OF graph bindings to link the display controller and encoder. The first two patches have been taken from Philipp Zabel's "[PATCH v3 0/8] Add of-graph helpers to loop over endpoints and find ports by id" series. Philipp, I don't see that series in linux-next, what's the merge status ? The R-Car DU patches start with a bit of refactoring, to finally add HDMI support in patch 08/12. The new adv7511 driver (patch 11/12) depends on decoupling EDID parsing from the DDC I2C adapter (patch 09/12). It supports DT instantiation only (bindings are documented in patch 10/12) for now. Platform data support could be added later if needed. The code is based on Lars-Peter Clausen's adv7511 driver, with heavy modifications. The last patch instantiates the HDMI encoder in the Koelsch board DT file and connects it to the DU output. The patch series depends on R-Car DU DT support (scheduled for merge in v3.18-rc1) and on Koelsch DU DT enablement (hopefully scheduled for merge in v3.19-rc1). For ease of testing and review I've pushed this series and its dependencies to a git branch on git://linuxtv.org/pinchartl/fbdev.git drm/du/adv7511 Cc: Philipp Zabel <p.zabel(a)pengutronix.de> Cc: devicetree(a)vger.kernel.org Lars-Peter Clausen (2): drm: Decouple EDID parsing from I2C adapter drm: Add adv7511 encoder driver Laurent Pinchart (8): drm: rcar-du: Remove platform data support drm: rcar-du: Use for_each_endpoint_of_node() drm: rcar-du: Pass the encoder DT node to rcar_du_encoder_init() drm: rcar-du: Replace direct DRM encoder access with cast macro drm: rcar-du: Replace drm_encoder with drm_slave_encoder drm: rcar-du: Add HDMI encoder and connector support video: Add ADV751[13] DT bindings documentation ARM: shmobile: koelsch: Add DU HDMI output support Philipp Zabel (2): of: Decrement refcount of previous endpoint in of_graph_get_next_endpoint of: Add for_each_endpoint_of_node helper macro .../devicetree/bindings/video/adi,adv7511.txt | 87 ++ arch/arm/boot/dts/r8a7791-koelsch.dts | 50 +- drivers/gpu/drm/drm_edid.c | 26 +- drivers/gpu/drm/i2c/Kconfig | 6 + drivers/gpu/drm/i2c/Makefile | 2 + drivers/gpu/drm/i2c/adv7511.c | 1007 ++++++++++++++++++++ drivers/gpu/drm/i2c/adv7511.h | 289 ++++++ drivers/gpu/drm/rcar-du/Kconfig | 11 +- drivers/gpu/drm/rcar-du/Makefile | 2 + drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 10 +- drivers/gpu/drm/rcar-du/rcar_du_drv.c | 4 +- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 45 +- drivers/gpu/drm/rcar-du/rcar_du_encoder.h | 23 +- drivers/gpu/drm/rcar-du/rcar_du_hdmicon.c | 118 +++ drivers/gpu/drm/rcar-du/rcar_du_hdmicon.h | 31 + drivers/gpu/drm/rcar-du/rcar_du_hdmienc.c | 151 +++ drivers/gpu/drm/rcar-du/rcar_du_hdmienc.h | 35 + drivers/gpu/drm/rcar-du/rcar_du_kms.c | 65 +- drivers/gpu/drm/rcar-du/rcar_du_lvdscon.c | 31 +- drivers/gpu/drm/rcar-du/rcar_du_lvdscon.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_lvdsenc.h | 1 - drivers/gpu/drm/rcar-du/rcar_du_vgacon.c | 5 +- drivers/of/base.c | 9 +- include/drm/drm_edid.h | 4 + include/linux/of_graph.h | 11 + include/linux/platform_data/rcar-du.h | 74 -- 27 files changed, 1902 insertions(+), 199 deletions(-) create mode 100644 Documentation/devicetree/bindings/video/adi,adv7511.txt create mode 100644 drivers/gpu/drm/i2c/adv7511.c create mode 100644 drivers/gpu/drm/i2c/adv7511.h create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_hdmicon.c create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_hdmicon.h create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_hdmienc.c create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_hdmienc.h delete mode 100644 include/linux/platform_data/rcar-du.h -- Regards, Laurent Pinchart

5 24

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014