dri-devel November 2020

dri-devel@lists.freedesktop.org

316 participants
811 discussions

[PATCH v2 1/2] dt-bindings: drm/bridge: anx7625: Add power supplies
by Hsin-Yi Wang 25 Dec '20

25 Dec '20

anx7625 requires 3 power supply regulators. Signed-off-by: Hsin-Yi Wang <hsinyi(a)chromium.org> --- Change: v2: remove maxItems for supplies --- .../bindings/display/bridge/analogix,anx7625.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml index 60585a4fc22b..3ae97d9523e5 100644 --- a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml +++ b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml @@ -34,6 +34,15 @@ properties: description: used for reset chip control, RESET_N pin B7. maxItems: 1 + vdd10-supply: + description: Regulator that provides the supply 1.0V power. + + vdd18-supply: + description: Regulator that provides the supply 1.8V power. + + vdd33-supply: + description: Regulator that provides the supply 3.3V power. + ports: type: object @@ -55,6 +64,9 @@ properties: required: - compatible - reg + - vdd10-supply + - vdd18-supply + - vdd33-supply - ports additionalProperties: false @@ -72,6 +84,9 @@ examples: reg = <0x58>; enable-gpios = <&pio 45 GPIO_ACTIVE_HIGH>; reset-gpios = <&pio 73 GPIO_ACTIVE_HIGH>; + vdd10-supply = <&pp1000_mipibrdg>; + vdd18-supply = <&pp1800_mipibrdg>; + vdd33-supply = <&pp3300_mipibrdg>; ports { #address-cells = <1>; -- 2.29.2.454.gaff20da3a2-goog

2 4

[Bug 210429] New: AMDGPU - DRM connector force-probe after DPMS causes monitor to reconnect
by bugzilla-daemon＠bugzilla.kernel.org 22 Dec '20

22 Dec '20

https://bugzilla.kernel.org/show_bug.cgi?id=210429 Bug ID: 210429 Summary: AMDGPU - DRM connector force-probe after DPMS causes monitor to reconnect Product: Drivers Version: 2.5 Kernel Version: 5.4.80 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: jordanleppert(a)gmail.com Regression: No This is with a Vega64 card, connected to two monitors via DisplayPort 1.2. When the connector is force-probed with a call to drmModeGetConnector, this is causing the connection to the monitor to disconnect, and reconnect. I'm seeing this issue using Wayland, specifically a wlroots based compositor. This patch to wlroots (which unfortunately needs to be reverted) stopped the problem happening: https://github.com/swaywm/wlroots/pull/2482/files -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

Re: [PATCH v1 17/30] mmc: sdhci-tegra: Support OPP and core voltage scaling
by Viresh Kumar 22 Dec '20

22 Dec '20

On 06-11-20, 21:41, Frank Lee wrote: > On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko <digetx(a)gmail.com> wrote: > > > > 06.11.2020 09:15, Viresh Kumar пишет: > > > Setting regulators for count as 0 doesn't sound good to me. > > > > > > But, I understand that you don't want to have that if (have_regulator) > > > check, and it is a fair request. What I will instead do is, allow all > > > dev_pm_opp_put*() API to start accepting a NULL pointer for the OPP > > > table and fail silently. And so you won't be required to have this > > > unwanted check. But you will be required to save the pointer returned > > > back by dev_pm_opp_set_regulators(), which is the right thing to do > > > anyways. > > > > Perhaps even a better variant could be to add a devm versions of the OPP > > API functions, then drivers won't need to care about storing the > > opp_table pointer if it's unused by drivers. > > I think so. The consumer may not be so concerned about the status of > these OPP tables. > If the driver needs to manage the release, it needs to add a pointer > to their driver global structure. > > Maybe it's worth having these devm interfaces for opp. Sure if there are enough users of this, I am all for it. I was fine with the patches you sent, just that there were not a lot of users of it and so I pushed them back. If we find that we have more users of it now, we can surely get that back. -- viresh

3 8

[PATCH] drm: bridge: adv7511: Remove redundant null check before clk_disable_unprepare
by Xu Wang 20 Dec '20

20 Dec '20

Because clk_disable_unprepare() already checked NULL clock parameter, so the additional check is unnecessary, just remove them. Signed-off-by: Xu Wang <vulab(a)iscas.ac.cn> --- drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c index a0d392c338da..76555ae64e9c 100644 --- a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c +++ b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c @@ -1292,8 +1292,7 @@ static int adv7511_probe(struct i2c_client *i2c, const struct i2c_device_id *id) err_unregister_cec: i2c_unregister_device(adv7511->i2c_cec); - if (adv7511->cec_clk) - clk_disable_unprepare(adv7511->cec_clk); + clk_disable_unprepare(adv7511->cec_clk); err_i2c_unregister_packet: i2c_unregister_device(adv7511->i2c_packet); err_i2c_unregister_edid: @@ -1311,8 +1310,7 @@ static int adv7511_remove(struct i2c_client *i2c) if (adv7511->type == ADV7533 || adv7511->type == ADV7535) adv7533_detach_dsi(adv7511); i2c_unregister_device(adv7511->i2c_cec); - if (adv7511->cec_clk) - clk_disable_unprepare(adv7511->cec_clk); + clk_disable_unprepare(adv7511->cec_clk); adv7511_uninit_regulators(adv7511); -- 2.17.1

2 1

[PATCH] drm: bridge: dw-hdmi: Remove redundant null check before clk_disable_unprepare
by Xu Wang 20 Dec '20

20 Dec '20

Because clk_disable_unprepare() already checked NULL clock parameter, so the additional check is unnecessary, just remove them. Signed-off-by: Xu Wang <vulab(a)iscas.ac.cn> --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c index 0c79a9ba48bb..dda4fa9a1a08 100644 --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c @@ -3440,8 +3440,7 @@ struct dw_hdmi *dw_hdmi_probe(struct platform_device *pdev, err_iahb: clk_disable_unprepare(hdmi->iahb_clk); - if (hdmi->cec_clk) - clk_disable_unprepare(hdmi->cec_clk); + clk_disable_unprepare(hdmi->cec_clk); err_isfr: clk_disable_unprepare(hdmi->isfr_clk); err_res: @@ -3465,8 +3464,7 @@ void dw_hdmi_remove(struct dw_hdmi *hdmi) clk_disable_unprepare(hdmi->iahb_clk); clk_disable_unprepare(hdmi->isfr_clk); - if (hdmi->cec_clk) - clk_disable_unprepare(hdmi->cec_clk); + clk_disable_unprepare(hdmi->cec_clk); if (hdmi->i2c) i2c_del_adapter(&hdmi->i2c->adap); -- 2.17.1

2 1

kernel BUG at drivers/dma-buf/dma-buf.c:LINE!
by syzbot 19 Dec '20

19 Dec '20

Hello, syzbot found the following crash on: HEAD commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=177bf331e00000 kernel config: https://syzkaller.appspot.com/x/.config?x=9833e26bab355358 dashboard link: https://syzkaller.appspot.com/bug?extid=d6734079f30f7fc39021 compiler: gcc (GCC) 9.0.0 20181231 (experimental) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109d3ac3e00000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+d6734079f30f7fc39021(a)syzkaller.appspotmail.com ------------[ cut here ]------------ kernel BUG at drivers/dma-buf/dma-buf.c:99! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 18500 Comm: syz-executor.0 Not tainted 5.6.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:dma_buf_release+0x35b/0x420 drivers/dma-buf/dma-buf.c:99 Code: 00 00 e8 f8 d3 ec fc 4c 89 e7 45 31 e4 e8 ed 7a 35 fd e8 38 25 f7 fc 44 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 25 25 f7 fc <0f> 0b e8 1e 25 f7 fc 4c 89 ef e8 46 eb 00 00 eb 97 e8 0f 25 f7 fc RSP: 0018:ffffc9000296fdc8 EFLAGS: 00010293 RAX: ffff888094086300 RBX: 0000000000000004 RCX: ffffffff847e6fc5 RDX: 0000000000000000 RSI: ffffffff847e722b RDI: 0000000000000005 RBP: ffffc9000296fdf0 R08: ffff888094086300 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff88808c6ec800 R13: ffff88808e6ecd7c R14: ffff88808e6ecd28 R15: ffff888097011940 FS: 0000000002b7b940(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000008a9e80 CR3: 00000000916f0000 CR4: 00000000001406e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __fput+0x2ff/0x890 fs/file_table.c:280 ____fput+0x16/0x20 fs/file_table.c:313 task_work_run+0x145/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:188 [inline] exit_to_usermode_loop+0x316/0x380 arch/x86/entry/common.c:164 prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline] syscall_return_slowpath arch/x86/entry/common.c:278 [inline] do_syscall_64+0x676/0x790 arch/x86/entry/common.c:304 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x416011 Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01 RSP: 002b:00007fff23e39030 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000009 RCX: 0000000000416011 RDX: 0000000000000000 RSI: 0000000000000081 RDI: 0000000000000008 RBP: 0000000000000000 R08: 0000000000000000 R09: 01ffffffffffffff R10: 0000000000770938 R11: 0000000000000293 R12: 000000000076bf20 R13: 0000000000770948 R14: 0000000000000000 R15: 000000000076bf2c Modules linked in: ---[ end trace 432bc1955550b75d ]--- RIP: 0010:dma_buf_release+0x35b/0x420 drivers/dma-buf/dma-buf.c:99 Code: 00 00 e8 f8 d3 ec fc 4c 89 e7 45 31 e4 e8 ed 7a 35 fd e8 38 25 f7 fc 44 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 25 25 f7 fc <0f> 0b e8 1e 25 f7 fc 4c 89 ef e8 46 eb 00 00 eb 97 e8 0f 25 f7 fc RSP: 0018:ffffc9000296fdc8 EFLAGS: 00010293 RAX: ffff888094086300 RBX: 0000000000000004 RCX: ffffffff847e6fc5 RDX: 0000000000000000 RSI: ffffffff847e722b RDI: 0000000000000005 RBP: ffffc9000296fdf0 R08: ffff888094086300 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff88808c6ec800 R13: ffff88808e6ecd7c R14: ffff88808e6ecd28 R15: ffff888097011940 FS: 0000000002b7b940(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000008a9e80 CR3: 00000000916f0000 CR4: 00000000001406e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- 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#status for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches

2 2

[PATCH 0/3] drm/panel: ABT Y030XX067A panel support
by Paul Cercueil 18 Dec '20

18 Dec '20

Hi, This patchset is for adding support for the Asia Better Technology (aka. ABT) Y030XX067A 3.0" 320x480 24-bit LCD IPS panel. While being 320x480 it is actually 4:3 with non-square pixels, and requires a specific bus format, as the pixel ordering changes each line (RGB on odd lines, GRB on even lines). Patch #1 adds the abt,* vendor prefix. Patch #2 adds the abt,y030xx067a panel binding documentation. Patch #3 adds the MEDIA_BUS_FMT_RGB888_3X8_DELTA media bus format. Patch #4 adds the driver itself. Cheers, -Paul Paul Cercueil (4): dt-bindings: vendor-prefixes: Add abt vendor prefix dt-bindings: display: Add ABT Y030XX067A panel bindings media: uapi: Add MEDIA_BUS_FMT_RGB888_3X8_DELTA media bus format drm/panel: Add ABT Y030XX067A 3.0" 320x480 panel .../display/panel/abt,y030xx067a.yaml | 54 +++ .../devicetree/bindings/vendor-prefixes.yaml | 2 + drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + drivers/gpu/drm/panel/panel-abt-y030xx067a.c | 363 ++++++++++++++++++ include/uapi/linux/media-bus-format.h | 3 +- 6 files changed, 431 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/display/panel/abt,y030xx067a.yaml create mode 100644 drivers/gpu/drm/panel/panel-abt-y030xx067a.c -- 2.28.0

4 16

BUG: unable to handle kernel paging request in cfb_imageblit
by syzbot 18 Dec '20

18 Dec '20

Hello, syzbot found the following issue on: HEAD commit: 22fbc037 Merge tag 'for-linus' of git://git.kernel.org/pub.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=133731eb900000 kernel config: https://syzkaller.appspot.com/x/.config?x=4e672827d2ffab1f dashboard link: https://syzkaller.appspot.com/bug?extid=dfd0b1c6705301cc4847 compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11ba9a5d900000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17cfd4af900000 Bisection is inconclusive: the issue happens on the oldest tested release. bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1536a750500000 final oops: https://syzkaller.appspot.com/x/report.txt?x=1736a750500000 console output: https://syzkaller.appspot.com/x/log.txt?x=1336a750500000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+dfd0b1c6705301cc4847(a)syzkaller.appspotmail.com BUG: unable to handle page fault for address: ffff888001000018 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD c801067 P4D c801067 PUD c802067 PMD 80000000010001e1 Oops: 0003 [#1] PREEMPT SMP KASAN CPU: 0 PID: 8241 Comm: syz-executor265 Not tainted 5.9.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__writel arch/x86/include/asm/io.h:71 [inline] RIP: 0010:slow_imageblit drivers/video/fbdev/core/cfbimgblt.c:178 [inline] RIP: 0010:cfb_imageblit+0xb15/0x11e0 drivers/video/fbdev/core/cfbimgblt.c:302 Code: 89 e6 89 e9 41 d3 e6 41 09 de 89 ef 8b 5c 24 28 89 de e8 0e db 81 fd 39 dd 73 0a e8 65 d9 81 fd eb 42 0f 1f 00 48 8b 44 24 30 <44> 89 30 48 83 c0 04 48 89 44 24 30 89 ef 89 de e8 e6 da 81 fd 39 RSP: 0018:ffffc9000a037558 EFLAGS: 00010246 RAX: ffff888001000018 RBX: 000000000000001c RCX: 000000000000001c RDX: ffff8880a79880c0 RSI: 000000000000001c RDI: 000000000000001c RBP: 000000000000001c R08: ffffffff83f32412 R09: ffffffff83f31b7c R10: 0000000000000002 R11: ffff8880a79880c0 R12: 0000000000000000 R13: ffff888218a81f72 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f8534532700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888001000018 CR3: 00000000a80b4000 CR4: 00000000001506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: soft_cursor+0xb44/0xdb0 drivers/video/fbdev/core/softcursor.c:74 bit_cursor+0x1753/0x2110 drivers/video/fbdev/core/bitblit.c:377 set_cursor drivers/tty/vt/vt.c:919 [inline] con_flush_chars+0x4e1/0x640 drivers/tty/vt/vt.c:3330 con_write+0x2a/0x40 drivers/tty/vt/vt.c:3251 do_output_char+0x63b/0x940 drivers/tty/n_tty.c:447 __process_echoes+0x2a3/0x930 drivers/tty/n_tty.c:739 flush_echoes drivers/tty/n_tty.c:829 [inline] __receive_buf drivers/tty/n_tty.c:1648 [inline] n_tty_receive_buf_common+0x29fa/0x3100 drivers/tty/n_tty.c:1742 paste_selection+0x32c/0x450 drivers/tty/vt/selection.c:408 vt_ioctl+0x105a/0x3d70 drivers/tty/vt/vt_ioctl.c:862 tty_ioctl+0xee4/0x15c0 drivers/tty/tty_io.c:2656 vfs_ioctl fs/ioctl.c:48 [inline] __do_sys_ioctl fs/ioctl.c:753 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:739 do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x449809 Code: e8 8c e7 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 00 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 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f8534531db8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00000000006dec68 RCX: 0000000000449809 RDX: 0000000020000080 RSI: 000000000000541c RDI: 0000000000000007 RBP: 00000000006dec60 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dec6c R13: 00007ffe8074321f R14: 00007f85345329c0 R15: 0000000000000064 Modules linked in: CR2: ffff888001000018 ---[ end trace 4ec628432d38a26a ]--- RIP: 0010:__writel arch/x86/include/asm/io.h:71 [inline] RIP: 0010:slow_imageblit drivers/video/fbdev/core/cfbimgblt.c:178 [inline] RIP: 0010:cfb_imageblit+0xb15/0x11e0 drivers/video/fbdev/core/cfbimgblt.c:302 Code: 89 e6 89 e9 41 d3 e6 41 09 de 89 ef 8b 5c 24 28 89 de e8 0e db 81 fd 39 dd 73 0a e8 65 d9 81 fd eb 42 0f 1f 00 48 8b 44 24 30 <44> 89 30 48 83 c0 04 48 89 44 24 30 89 ef 89 de e8 e6 da 81 fd 39 RSP: 0018:ffffc9000a037558 EFLAGS: 00010246 RAX: ffff888001000018 RBX: 000000000000001c RCX: 000000000000001c RDX: ffff8880a79880c0 RSI: 000000000000001c RDI: 000000000000001c RBP: 000000000000001c R08: ffffffff83f32412 R09: ffffffff83f31b7c R10: 0000000000000002 R11: ffff8880a79880c0 R12: 0000000000000000 R13: ffff888218a81f72 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f8534532700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888001000018 CR3: 00000000a80b4000 CR4: 00000000001506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- This report 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 issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches

2 2

[PATCH v3 0/9] Xilinx AI engine kernel driver
by Wendy Liang 17 Dec '20

17 Dec '20

AI engine is the acceleration engine provided by Xilinx. These engines provide high compute density for vector-based algorithms, and flexible custom compute and data movement. It has core tiles for compute and shim tiles to interface the FPGA fabric. You can check the AI engine architecture document for more hardware details: https://www.xilinx.com/support/documentation/architecture-manuals/am009-ver… This patch series adds a Linux kernel driver to manage the Xilinx AI engine array device and AI engine partitions (groups of AI engine tiles dedicated to an application). v3: * unlock AIE dev mutex after failed to gain the partition lock in errors handing * replace pointer with __u64 and enum with __u32 in ioctl v2: * Fix dtschema check errors * Fix test bot warning on interrupt implementation. Removed set but unused varaible. * Fix compilation unused function warning of firmware change in case ZynqMP firmware is not configured * There are other warning on ZynqMP firmware reported from testbot which is not introduced by this patch set. "[PATCH] firmware: xlnx-zynqmp: fix compilation warning" is submitted for those fixes. Izhar Ameer Shaikh (1): firmware: xilinx: Add IOCTL support for AIE ISR Clear Nishad Saraf (2): misc: xilinx-ai-engine: Add support to request device management services misc: xilinx-ai-engine: Add support for servicing error interrupts Wendy Liang (6): dt-binding: soc: xilinx: ai-engine: Add AI engine binding misc: Add Xilinx AI engine device driver misc: xilinx-ai-engine: Implement AI engine cleanup sequence misc: xilinx-ai-engine: expose AI engine tile memories to userspace misc: xilinx-ai-engine: add setting shim dma bd operation misc: xilinx-ai-engine: add request and release tiles .../bindings/soc/xilinx/xlnx,ai-engine.yaml | 126 ++++ MAINTAINERS | 8 + drivers/firmware/xilinx/zynqmp.c | 14 + drivers/misc/Kconfig | 12 + drivers/misc/Makefile | 1 + drivers/misc/xilinx-ai-engine/Makefile | 16 + drivers/misc/xilinx-ai-engine/ai-engine-aie.c | 608 +++++++++++++++++++ drivers/misc/xilinx-ai-engine/ai-engine-clock.c | 245 ++++++++ drivers/misc/xilinx-ai-engine/ai-engine-dev.c | 496 ++++++++++++++++ drivers/misc/xilinx-ai-engine/ai-engine-dma.c | 481 +++++++++++++++ drivers/misc/xilinx-ai-engine/ai-engine-internal.h | 519 ++++++++++++++++ .../misc/xilinx-ai-engine/ai-engine-interrupt.c | 659 +++++++++++++++++++++ drivers/misc/xilinx-ai-engine/ai-engine-mem.c | 275 +++++++++ drivers/misc/xilinx-ai-engine/ai-engine-part.c | 635 ++++++++++++++++++++ drivers/misc/xilinx-ai-engine/ai-engine-res.c | 219 +++++++ drivers/misc/xilinx-ai-engine/ai-engine-reset.c | 159 +++++ include/linux/firmware/xlnx-zynqmp.h | 8 + include/uapi/linux/xlnx-ai-engine.h | 238 ++++++++ 18 files changed, 4719 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/xilinx/xlnx,ai-engine.yaml create mode 100644 drivers/misc/xilinx-ai-engine/Makefile create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-aie.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-clock.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-dev.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-dma.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-internal.h create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-interrupt.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-mem.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-part.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-res.c create mode 100644 drivers/misc/xilinx-ai-engine/ai-engine-reset.c create mode 100644 include/uapi/linux/xlnx-ai-engine.h -- 2.7.4

5 18

[PATCH v7 0/5] dma-buf: Code rework and performance improvements for system heap
by John Stultz 16 Dec '20

16 Dec '20

Hey All, So Sumit noted a flub I made in adapting the last series to the new dma-buf-map code that is in drm-misc-next. Thus I wanted to send this (hopefully) last revision of my patch series of performance optimizations to the dma-buf system heap, once again against drm-misc-next. This series reworks the system heap to use sgtables, and then consolidates the pagelist method from the heap-helpers into the CMA heap. After which the heap-helpers logic is removed (as it is unused). I'd still like to find a better way to avoid some of the logic duplication in implementing the entire dma_buf_ops handlers per heap. But unfortunately that code is tied somewhat to how the buffer's memory is tracked. As more heaps show up I think we'll have a better idea how to best share code, so for now I think this is ok. After this, the series introduces an optimization that Ørjan Eide implemented for ION that avoids calling sync on attachments that don't have a mapping. Finally, an optimization to use larger order pages for the system heap. This change brings us closer to the current performance of the ION allocation code (though there still is a gap due to ION using a mix of deferred-freeing and page pools, I'll be looking at integrating those eventually). This version of the series does not include the system-uncached heap as Daniel wanted further demonstration that it is useful with devices that use the mesa stack. I'm working on such a justification but I don't want to hold up these rework patches in the meantime. thanks -john New in v7: * Fixed the incorrect adaptation to the dma-buf-map usage Cc: Sumit Semwal <sumit.semwal(a)linaro.org> Cc: Liam Mark <lmark(a)codeaurora.org> Cc: Laura Abbott <labbott(a)kernel.org> Cc: Brian Starkey <Brian.Starkey(a)arm.com> Cc: Hridya Valsaraju <hridya(a)google.com> Cc: Suren Baghdasaryan <surenb(a)google.com> Cc: Sandeep Patil <sspatil(a)google.com> Cc: Daniel Mentz <danielmentz(a)google.com> Cc: Chris Goldsworthy <cgoldswo(a)codeaurora.org> Cc: Ørjan Eide <orjan.eide(a)arm.com> Cc: Robin Murphy <robin.murphy(a)arm.com> Cc: Ezequiel Garcia <ezequiel(a)collabora.com> Cc: Simon Ser <contact(a)emersion.fr> Cc: James Jones <jajones(a)nvidia.com> Cc: linux-media(a)vger.kernel.org Cc: dri-devel(a)lists.freedesktop.org John Stultz (5): dma-buf: system_heap: Rework system heap to use sgtables instead of pagelists dma-buf: heaps: Move heap-helper logic into the cma_heap implementation dma-buf: heaps: Remove heap-helpers code dma-buf: heaps: Skip sync if not mapped dma-buf: system_heap: Allocate higher order pages if available drivers/dma-buf/heaps/Makefile | 1 - drivers/dma-buf/heaps/cma_heap.c | 329 +++++++++++++++++---- drivers/dma-buf/heaps/heap-helpers.c | 274 ------------------ drivers/dma-buf/heaps/heap-helpers.h | 53 ---- drivers/dma-buf/heaps/system_heap.c | 414 ++++++++++++++++++++++++--- 5 files changed, 647 insertions(+), 424 deletions(-) delete mode 100644 drivers/dma-buf/heaps/heap-helpers.c delete mode 100644 drivers/dma-buf/heaps/heap-helpers.h -- 2.17.1

3 9

← Newer
1
...
9
10
11
12
13
14
15
...
82
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2020