RE: [EXT] Re: [v2 06/10] drm: bridge: cadence: Add MHDP HDMI driver for i.MX8MQ

Hi Alexander, > -Original Message- > From: Alexander Stein > Sent: 2022年11月10日 23:44 > To: Sandor Yu > Cc: jo...@kwiboo.se; dri-devel@lists.freedesktop.org; > devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > linux-ker...@vger.kernel.org; linux-...@lists.infradead.org;

Re: [PATCH v8 09/14] drm: bridge: samsung-dsim: Add atomic_get_input_bus_fmts

On Sun, Nov 13, 2022 at 5:51 AM Marek Vasut wrote: > > On 11/10/22 19:38, Jagan Teki wrote: > > Finding the right input bus format throughout the pipeline is hard > > so add atomic_get_input_bus_fmts callback and initialize with the > > proper input format from list of supported output formats. >

Re: [PATCH] fbdev: smscufx: fix error handling code in ufx_usb_probe

On 11/11/22 06:49, Dongliang Mu wrote: The current error handling code in ufx_usb_probe have many unmatching issues, e.g., missing ufx_free_usb_list, destroy_modedb label should only include framebuffer_release, fb_dealloc_cmap only matches fb_alloc_cmap. My local syzkaller reports a memory

Re: [PATCH] video: fbdev: via: Fix error in via_core_init()

On 11/14/22 02:08, Shang XiaoJing wrote: via_core_init() won't exit the driver when pci_register_driver() failed. Exit the viafb-i2c and the viafb-gpio in failed path to prevent error. VIA Graphics Integration Chipset framebuffer 2.4 initializing Error: Driver 'viafb-i2c' is already registered,

Re: [PATCH v2] udmabuf: add vmap method to udmabuf_ops

On Sun, Nov 13, 2022 at 07:35:20PM +0300, Dmitry Osipenko wrote: > On 11/13/22 18:05, Lukasz Wiecaszek wrote: > > +static int vmap_udmabuf(struct dma_buf *buf, struct iosys_map *map) > > +{ > > + struct udmabuf *ubuf = buf->priv; > > + > > + if (!ubuf->vaddr) { > > + ubuf->vaddr =

Re: [PATCH v8 01/14] drm: exynos: dsi: Fix MIPI_DSI*_NO_* mode flags

On 11/14/22 02:11, Nicolas Boichat wrote: On Sun, Nov 13, 2022 at 8:29 AM Marek Vasut wrote: On 11/11/22 13:12, Nicolas Boichat wrote: [...] BTW, are you sure DSIM_HSE_MODE is correct now? Yes, we have tested in imx8m platforms as well. Sébastien Szymanski initially observed this issue

Re: [syzbot] possible deadlock in vfs_fileattr_set

syzbot has bisected this issue to: commit 6dd6b7643e723b4779e59c8ad97bd5db6ff3bb12 Author: Thomas Zimmermann Date: Mon Jan 18 13:14:19 2021 + drm/vmwgfx: Remove reference to struct drm_device.pdev bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1418e6a588 start

Re: [PATCH v8 01/14] drm: exynos: dsi: Fix MIPI_DSI*_NO_* mode flags

On Sun, Nov 13, 2022 at 8:29 AM Marek Vasut wrote: > > On 11/11/22 13:12, Nicolas Boichat wrote: > > [...] > > >>> BTW, are you sure DSIM_HSE_MODE is correct now? > >> > >> Yes, we have tested in imx8m platforms as well. Sébastien Szymanski > >> initially observed this issue on the imx8m

Re: [PATCH 1/2] drm/vc4: hdmi: Enforce the minimum rate at runtime_resume

Am 11.11.22 um 22:08 schrieb Stefan Wahren: Hi Maxime, Am 29.09.22 um 11:21 schrieb Maxime Ripard: This is a revert of commit fd5894fa2413 ("drm/vc4: hdmi: Remove clock rate initialization"), with the code slightly moved around. It turns out that we can't downright remove that code from the

Re: [PATCH 06/26] drm: sun4i: Use the dev_pm_ops provided by modeset helper

On 11/7/22 11:50, Paul Cercueil wrote: > Use the drm_mode_config_pm_ops structure exported by > drm_modeset_helper.c, which provides the exact same PM callbacks. > > Signed-off-by: Paul Cercueil > --- > Cc: Maxime Ripard > Cc: Chen-Yu Tsai > Cc: Jernej Skrabec > Cc: Samuel Holland > Cc:

Re: [PATCH] drm/mediatek: Fix return type of mtk_hdmi_bridge_mode_valid()

Hi, Nathan: Nathan Chancellor 於 2022年11月2日 週三 晚上11:47寫道： > > With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), > indirect call targets are validated against the expected function > pointer prototype to make sure the call target is valid to help mitigate > ROP attacks. If they

Re: [PATCH v2] drm/mediatek: make eDP panel as the first connected connector

Hi Gil: Gil Dekel 於 2022年11月11日 週五 凌晨2:49寫道： > > [Why] > Some userspaces assume that the first connected connector is the "main" > display, which supposed to display, for example, the login screen. > For laptops, this should be the internal connector. > > [How] > This patch calls

[PATCH v1] drm/gem-vram: Fix deadlock in drm_gem_vram_vmap()

Recently DRM framebuffer core and all drivers were moved to unlocked vmapping functions that take the reservation lock. The drm_gem_vram_vmap() was missed out by accident and now deadlocks drivers that use drm_gem_vram helpers when framebuffer is updated, like Bochs driver. Remove the locking from

Re: [PATCH v4] drm: mediatek: Modify dpi power on/off sequence.

Hi, Xinlei: 於 2022年11月9日 週三 下午6:01寫道： > > From: Xinlei Lee > > Modify dpi power on/off sequence so that the first gpio operation will take > effect. Applied to mediatek-drm-next [1], thanks. [1] https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-next

linux-next: manual merge of the drm-intel tree with Linus' tree

Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/display/intel_backlight.c between commit: b1d36e73cc1c ("drm/i915: Don't register backlight when another backlight should be used (v2)") from Linus' tree and commit: 801543b2593b ("drm/i915:

Re: dealock in drm_fb_helper_damage_work

On 11/13/22 23:48, Dmitry Vyukov wrote: >> Hi, >> >> I am getting the following deadlock on reservation_ww_class_mutex >> while trying to boot next-2022 kernel: > The code is recently added by this commit: > > commit 79e2cf2e7a193473dfb0da3b9b869682b43dc60f > Author: Dmitry Osipenko > Date:

Re: dealock in drm_fb_helper_damage_work

On Sun, 13 Nov 2022 at 21:42, Dmitry Vyukov wrote: > > Hi, > > I am getting the following deadlock on reservation_ww_class_mutex > while trying to boot next-2022 kernel: The code is recently added by this commit: commit 79e2cf2e7a193473dfb0da3b9b869682b43dc60f Author: Dmitry Osipenko Date:

dealock in drm_fb_helper_damage_work

Hi, I am getting the following deadlock on reservation_ww_class_mutex while trying to boot next-2022 kernel: WARNING: possible recursive locking detected 6.1.0-rc4-next-2022 #193 Not tainted

Re: [PATCH] drm/edid/firmware: stop using throwaway platform device

Hi, I've tested the patch and I can confirm that it fixed the issue. Tested on Fedora 36 with kernel 6.0.8. Thanks, Matthieu On Tue, Nov 8 2022 at 04:40:52 PM +0100, Matthieu CHARETTE wrote: I didn't test the patch yet. I will do. But even without testing I can tell you that it will work

Re: [PATCH] drm/amd/display: add parameter backlight_min

On Tue, Nov 01, 2022 at 12:06:55PM -0400, Alex Deucher wrote: > On Tue, Nov 1, 2022 at 11:42 AM Filip Moc wrote: > > > > Hello Alex, > > > > thank you for your response. > > > > Yes, I have HP ENVY x360 Convertible 13-ay1xxx, and backlight_min=2 > > seems to work the best in my case. > > > > I

Re: [PATCH] drm/amd/display: don't enable DRM CRTC degamma property for DCE

On 11/3/22 14:45, Melissa Wen wrote: DM maps DRM CRTC degamma to DPP (pre-blending) degamma block, but DCE doesn't support programmable degamma curve anywhere. Currently, a custom degamma is accepted by DM but just ignored by DCE driver and degamma correction isn't actually applied. There is

Re: [PATCH v2] udmabuf: add vmap method to udmabuf_ops

On 11/13/22 18:05, Lukasz Wiecaszek wrote: > +static int vmap_udmabuf(struct dma_buf *buf, struct iosys_map *map) > +{ > + struct udmabuf *ubuf = buf->priv; > + > + if (!ubuf->vaddr) { > + ubuf->vaddr = vm_map_ram(ubuf->pages, ubuf->pagecount, -1); > + if

Re: [PATCH v2] udmabuf: add vmap method to udmabuf_ops

On 11/13/22 18:05, Lukasz Wiecaszek wrote: > The reason behind that patch is associated with videobuf2 subsystem > (or more genrally with v4l2 framework) and user created > dma buffers (udmabuf). In some circumstances > when dealing with V4L2_MEMORY_DMABUF buffers videobuf2 subsystem > wants to

[PATCH v2] udmabuf: add vmap method to udmabuf_ops

The reason behind that patch is associated with videobuf2 subsystem (or more genrally with v4l2 framework) and user created dma buffers (udmabuf). In some circumstances when dealing with V4L2_MEMORY_DMABUF buffers videobuf2 subsystem wants to use dma_buf_vmap() method on the attached dma buffer.

Re: [RFC PATCH v3 0/3] new subsystem for compute accelerator devices

On Sat, Nov 12, 2022 at 12:04 AM Christopher Friedt wrote: > > Hi Oded, > > On Sun, Nov 6, 2022 at 4:03 PM Oded Gabbay wrote: > > The patches are in the following repo: > > https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/accel.git/log/?h=accel_v3 > > > > As in v2, The HEAD of that branch

Re: [PATCH v2.5] drm/msm/dsi: switch to DRM_PANEL_BRIDGE

Hi Caleb, On Fri, 11 Nov 2022 at 18:30, Caleb Connolly wrote: > > Hi, > > This patch has caused a regression on 6.1-rc for some devices that use > DSI panels. The new behaviour results in the DSI controller being > switched off before the panel unprepare hook is called. As a result, > panel

[PATCH 1/1] drm/shmem: Dual licence the files as GPL-2 and MIT

Contributors to these files are: Noralf Trønnes Liu Zixian Dave Airlie Thomas Zimmermann Lucas De Marchi Gerd Hoffmann Rob Herring Jakub Kicinski Marcel Ziswiler Stephen Rothwell Daniel Vetter Cai Huoqing Neil Roberts Marek Szyprowski Emil Velikov Sam Ravnborg Boris Brezillon Dan

[PATCH 0/1] drm/shmem: Dual licence the files as GPL-2 and MIT

There was some earlier discussion on dual licencing as GPL-2 and MIT some files that were previously just GPL-2: Would it be possible to dual licence two more of the files?

Re: [PATCH] udmabuf: add vmap method to udmabuf_ops

On Fri, Nov 11, 2022 at 03:31:15PM +0300, Dmitry Osipenko wrote: > On 11/11/22 15:05, Christian König wrote: > > Adding Dmitry as well. > > > > Am 11.11.22 um 12:45 schrieb Lukasz Wiecaszek: > >> The reason behind that patch is associated with videobuf2 subsystem > >> (or more genrally with v4l2

Re: [PATCH V2 0/3] DSI host and peripheral initialisation ordering

Hi Dave, On 19/07/2022 16:45, Dave Stevenson wrote: Hi Sam On Mon, 18 Jul 2022 at 21:52, Sam Ravnborg wrote: Hi Dave, a long overdue reply on this series. On Fri, Mar 04, 2022 at 03:17:55PM +, Dave Stevenson wrote: Hi All Changes from v1: - New patch to refactor

[PATCH] drm/radeon: fix potential racing issue due to mmap_lock

Both find_vma() and get_user_pages() need explicit protection of mmap lock, fix them by mmap_lock and get_user_pages_fast(). Fixes: ddd00e33e17a ("drm/radeon: add userptr flag to limit it to anonymous memory v2") Fixes: f72a113a71ab ("drm/radeon: add userptr support v8") Signed-off-by: Dawei Li

Re: [PATCH v2.5] drm/msm/dsi: switch to DRM_PANEL_BRIDGE #forregzbot

[Note: this mail is primarily send for documentation purposes and/or for regzbot, my Linux kernel regression tracking bot. That's why I removed most or all folks from the list of recipients, but left any that looked like a mailing lists. These mails usually contain '#forregzbot' in the subject, to