Re: [PATCH] drm/radeon: remove three set but not used variable

On Thu, Dec 26, 2019 at 08:07:50PM +0800, yu kuai wrote: > Fixes gcc '-Wunused-but-set-variable' warning: > > drivers/gpu/drm/radeon/radeon_atombios.c: In function > ‘radeon_get_atom_connector_info_from_object_table’: > drivers/gpu/drm/radeon/radeon_atombios.c:651:26: warning: variable > ‘grph_obj

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

On 24.12.2019 10:44, Boris Brezillon wrote: > On Tue, 24 Dec 2019 10:16:49 +0100 > Andrzej Hajda wrote: > >> On 23.12.2019 10:55, Marek Szyprowski wrote: >>> Hi Boris, >>> >>> On 16.12.2019 16:25, Boris Brezillon wrote: On Mon, 16 Dec 2019 16:02:36 +0100 Marek Szyprowski wrote:

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

Hi Boris, On 24.12.2019 11:03, Boris Brezillon wrote: > On Tue, 24 Dec 2019 10:49:36 +0100 > Boris Brezillon wrote: >> On Tue, 24 Dec 2019 10:44:22 +0100 >> Boris Brezillon wrote: >>> On Tue, 24 Dec 2019 10:16:49 +0100 >>> Andrzej Hajda wrote: On 23.12.2019 10:55, Marek Szyprowski wrote: >

KASAN: slab-out-of-bounds Write in fbcon_scroll

Hello, syzbot found the following crash on: HEAD commit:46cf053e Linux 5.5-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1376a2c6e0 kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35 dashboard link: https://syzkaller.appspo

[PATCH] dma-buf: free dmabuf->name in dma_buf_release()

dma-buff name can be set via DMA_BUF_SET_NAME ioctl, but once set it never gets freed. Free it in dma_buf_release(). Fixes: bb2bb9030425 ("dma-buf: add DMA_BUF_SET_NAME ioctls") Reported-by: syzbot+b2098bc44728a4efb...@syzkaller.appspotmail.com Cc: Greg Hackmann Cc: Chenbo Feng Cc: Sumit Semwal

Re: [Regression drm-tip] Internal audio device missing

Dear Takashi, Am 26.12.19 um 11:03 schrieb Takashi Iwai: On Thu, 26 Dec 2019 10:47:18 +0100, Paul Menzel wrote: With $ git describe --tags drm-tip/drm-tip v5.5-rc3-1481-ga20d8cd6901a the internal audio device is not available, and just a dummy device. Running `alsa-info.sh` [1],

BUG: unable to handle kernel paging request in vga16fb_imageblit

Hello, syzbot found the following crash on: HEAD commit:46cf053e Linux 5.5-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12e35351e0 kernel config: https://syzkaller.appspot.com/x/.config?x=ed9d672709340e35 dashboard link: https://syzkaller.appspo

Re: [PATCH v22 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Ezequiel, On 26/12/19 17:38, Ezequiel Garcia wrote: > Hi Enric, > > Note that this series is marked as v22, but it's really the 23th. > Some minor comments below, it's looking really now. > > Reviewed-by: Ezequiel Garcia > > On Mon, 2019-12-23 at 15:35 +0100, Enric Balletbo i Serra wrote: >

Re: [PATCH v22 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

Hi Ezequiel, On 26/12/19 15:27, Ezequiel Garcia wrote: > Hi Enric, Rob, > > On Mon, 2019-12-23 at 15:35 +0100, Enric Balletbo i Serra wrote: >> From: Jitao Shi >> >> Add documentation for DT properties supported by >> ps8640 DSI-eDP converter. >> >> Signed-off-by: Jitao Shi >> Acked-by: Rob Her

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

Hi Andrzej, On Fri, Dec 27, 2019 at 10:42:25AM +0100, Andrzej Hajda wrote: > On 24.12.2019 10:44, Boris Brezillon wrote: > > On Tue, 24 Dec 2019 10:16:49 +0100 Andrzej Hajda wrote: > >> On 23.12.2019 10:55, Marek Szyprowski wrote: > >>> On 16.12.2019 16:25, Boris Brezillon wrote: > On Mon,

[PATCH] drm/bridge: Fix Exynos DSI after making bridge chain a double-linked list

Exynos DSI DRM driver uses private calls to out bridge to force certain order of operations during init/exit sequences. This no longer works after conversion of bridge chain to a double-linked list. To fix the regression call bridge related operations manually instead of the generic drm_bridge_chai

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

Hi All, On 27.12.2019 11:25, Marek Szyprowski wrote: > On 24.12.2019 11:03, Boris Brezillon wrote: >> On Tue, 24 Dec 2019 10:49:36 +0100 >> Boris Brezillon wrote: >>> On Tue, 24 Dec 2019 10:44:22 +0100 >>> Boris Brezillon wrote: On Tue, 24 Dec 2019 10:16:49 +0100 Andrzej Hajda wrote:

Re: [PATCH] drm: replace IS_ERR and PTR_ERR with PTR_ERR_OR_ZERO

On Wed, Dec 25, 2019 at 09:20:42PM +0800, yu kuai wrote: > no functional change, just to make the code simpler > > Signed-off-by: yu kuai > --- > drivers/gpu/drm/omapdrm/dss/hdmi4.c | 5 + > drivers/gpu/drm/omapdrm/dss/hdmi4_core.c| 6 ++ > drivers/gpu/drm/omapdrm/dss/hdmi5_co

Re: [PATCH] drm/bridge: Fix Exynos DSI after making bridge chain a double-linked list

On Fri, 27 Dec 2019 12:01:35 +0100 Marek Szyprowski wrote: > Exynos DSI DRM driver uses private calls to out bridge to force certain > order of operations during init/exit sequences. This no longer works after > conversion of bridge chain to a double-linked list. To fix the regression > call brid

Re: [PATCH v14 0/7] drm/sun4i: Allwinner A64 MIPI-DSI support

On Thu, Dec 26, 2019 at 3:08 PM Maxime Ripard wrote: > > On Sun, Dec 22, 2019 at 06:52:22PM +0530, Jagan Teki wrote: > > This is v14 version for Allwinner A64 MIPI-DSI support > > and here is the previous version set[1] > > I applied the patches 1 to 6, and fixed checkpatch warnings in the > patch

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

On Fri, 27 Dec 2019 12:51:54 +0200 Laurent Pinchart wrote: > Hi Andrzej, > > On Fri, Dec 27, 2019 at 10:42:25AM +0100, Andrzej Hajda wrote: > > On 24.12.2019 10:44, Boris Brezillon wrote: > > > On Tue, 24 Dec 2019 10:16:49 +0100 Andrzej Hajda wrote: > > >> On 23.12.2019 10:55, Marek Szyprows

Re: [PATCH v4 04/11] drm/bridge: Make the bridge chain a double-linked list

On Tue, 24 Dec 2019 12:31:11 +0100 Sam Ravnborg wrote: > Hi Boris. > > > Just a reminder of my 2 proposals: > > > > 1/ implement the bridge_ops->pre_enable/post_disable() hooks so you can > >split your enable/disable logic in 2 parts and make sure things are > >ready when the panel/next

Re: [PATCH] drm/bridge: Fix Exynos DSI after making bridge chain a double-linked list

On Fri, 27 Dec 2019 13:00:04 +0100 Boris Brezillon wrote: > On Fri, 27 Dec 2019 12:01:35 +0100 > Marek Szyprowski wrote: > > > Exynos DSI DRM driver uses private calls to out bridge to force certain > > order of operations during init/exit sequences. This no longer works after > > conversion of

Re: [PATCH] drm/bridge: Fix Exynos DSI after making bridge chain a double-linked list

On Fri, 27 Dec 2019 14:23:13 +0100 Boris Brezillon wrote: > On Fri, 27 Dec 2019 13:00:04 +0100 > Boris Brezillon wrote: > > > On Fri, 27 Dec 2019 12:01:35 +0100 > > Marek Szyprowski wrote: > > > > > Exynos DSI DRM driver uses private calls to out bridge to force certain > > > order of opera

[PATCH 3/3] drm/exynos: dsi: Fix bridge chain handling

Commit 05193dc38197 ("drm/bridge: Make the bridge chain a double-linked list") patched the bridge chain logic to use a double-linked list instead of a single-linked list. This change induced changes to the Exynos driver which was manually resetting the encoder->bridge element to NULL to control the

[PATCH 2/3] drm/vc4: dsi: Fix bridge chain handling

Commit 05193dc38197 ("drm/bridge: Make the bridge chain a double-linked list") patched the bridge chain logic to use a double-linked list instead of a single-linked list. This change induced changes to the VC4 driver which was manually resetting the encoder->bridge element to NULL to control the en

[PATCH 1/3] drm/bridge: Fix drm_bridge_chain_pre_enable()

Stop iterating on the bridge chain when we reach the bridge element. That's what other helpers do and should allow bridge implementations to execute a pre_enable operation on a sub-chain. Fixes: 05193dc38197 ("drm/bridge: Make the bridge chain a double-linked list") Signed-off-by: Boris Brezillon

[PATCH AUTOSEL 5.4 068/187] bnxt_en: Return error if FW returns more data than dump length

From: Vasundhara Volam [ Upstream commit c74751f4c39232c31214ec6a3bc1c7e62f5c728b ] If any change happened in the configuration of VF in VM while collecting live dump, there could be a race and firmware can return more data than allocated dump length. Fix it by keeping track of the accumulated c

[PATCH AUTOSEL 4.19 32/84] bnxt_en: Return error if FW returns more data than dump length

From: Vasundhara Volam [ Upstream commit c74751f4c39232c31214ec6a3bc1c7e62f5c728b ] If any change happened in the configuration of VF in VM while collecting live dump, there could be a race and firmware can return more data than allocated dump length. Fix it by keeping track of the accumulated c

[PATCH AUTOSEL 4.19 74/84] drm/exynos: gsc: add missed component_del

From: Chuhong Yuan [ Upstream commit 84c92365b20a44c363b95390ea00dfbdd786f031 ] The driver forgets to call component_del in remove to match component_add in probe. Add the missed call to fix it. Signed-off-by: Chuhong Yuan Signed-off-by: Inki Dae Signed-off-by: Sasha Levin --- drivers/gpu/d

[git pull] drm fixes for 5.5-rc4

Hey Linus, Post-xmas food coma recovery fixes. Only 3 fixes for i915 since I expect most people are holidaying. Dave. drm-fixes-2019-12-28: drm fixes for 5.5-rc4 i915: - power management rc6 fix - framebuffer tracking fix - display power management ratelimit fix The following changes since comm

Re: [git pull] drm fixes for 5.5-rc4

The pull request you sent on Sat, 28 Dec 2019 06:08:45 +1000: > git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-12-28 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/48a8dd171993569cb77dee0882a47abad47d2837 Thank you! -- Deet-doot-dot, I am a bot. https://k

Re: [PATCH v11 00/25] mm/gup: track dma-pinned pages: FOLL_PIN

On 12/24/19 9:26 PM, Leon Romanovsky wrote: ... The branch is here (I just tested it and it seems healthy): g...@github.com:johnhubbard/linux.git pin_user_pages_tracking_v11_with_diags Hi, We tested the following branch and here comes results: Thanks for this testing run! [root@server co