Re: [PATCH 19/25] drm/msm/dpu: don't use unsupported blend stages

On 2/9/2022 9:25 AM, Dmitry Baryshkov wrote: The atomic_check compares blending stage with DPU_STAGE_MAX (maximum amount of blending stages supported by the driver), however we should compare it against .max_mixer_blendstages, the maximum blend stage supported by the mixer. Signed-off-by:

Re: [git pull] drm fixes for 5.18-rc7 (follow up)

The pull request you sent on Sat, 14 May 2022 08:56:01 +1000: > git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-05-14 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/ec7f49619d8ee13e108740c82f942cd401b989e9 Thank you! -- Deet-doot-dot, I am a bot.

Re: [PATCH] drm/msm/dpu: limit writeback modes according to max_linewidth

On 5/13/2022 3:59 PM, Abhinav Kumar wrote: Writeback modes were being added according to mode_config.max_width but this is assigned to double of max_mixer_width. For compositors/clients using a single SSPP, this will fail the dpu_plane's atomic check as it checks for max_linewidth. Limit

[PATCH] drm/msm/dpu: limit writeback modes according to max_linewidth

Writeback modes were being added according to mode_config.max_width but this is assigned to double of max_mixer_width. For compositors/clients using a single SSPP, this will fail the dpu_plane's atomic check as it checks for max_linewidth. Limit writeback modes according to max_linewidth to

[git pull] drm fixes for 5.18-rc7 (follow up)

Hey Linus, Turns out I was right, some fixes hadn't made it to me yet. The vmwgfx ones also popped up later, but all seem like bad enough things to fix. The dma-buf, vc4 and nouveau ones are all pretty small. The fbdev fixes are a bit more complicated, a fix to cleanup fbdev devices properly,

Re: [PATCH v2 1/3] dt-bindings: display: rockchip: make reg-names mandatory for VOP2

Hi Rob, Krzysztof, Am Mittwoch, 11. Mai 2022, 10:21:07 CEST schrieb Sascha Hauer: > The VOP2 driver relies on reg-names properties, but these are not > documented. Add the missing documentation, make reg-names mandatory > and increase minItems to 2 as always both register spaces are needed. > >

Re: [PATCH v3] uapi/drm/i915: Document memory residency and Flat-CCS capability of obj

On 2022-05-13 05:31:00, Lionel Landwerlin wrote: > On 02/05/2022 17:15, Ramalingam C wrote: > > Capture the impact of memory region preference list of the objects, on > > their memory residency and Flat-CCS capability. > > > > v2: > >Fix the Flat-CCS capability of an obj with {lmem, smem}

Re: [PATCH v2 3/3] drm/panel: introduce ebbg,ft8719 panel

On Wed, May 11, 2022 at 7:28 AM Joel Selvaraj wrote: > Add DRM panel driver for EBBG FT8719 6.18" 2246x1080 DSI video mode > panel, which can be found on some Xiaomi Poco F1 phones. The panel's > backlight is managed through QCOM WLED driver. > > Signed-off-by: Joel Selvaraj I see my review

Re: [PATCH v2 2/3] dt-bindings: display: Add bindings for EBBG FT8719

On Wed, May 11, 2022 at 7:28 AM Joel Selvaraj wrote: > Add bindings for the EBBG FT8719 6.18" 2246x1080 DSI video mode panel, > which can be found on some Xiaomi Poco F1 phones. The backlight is > managed through the QCOM WLED driver. > > Signed-off-by: Joel Selvaraj > --- > Changes in v2:

[PATCH v5] drm/msm/dsi: don't powerup at modeset time for parade-ps8640

Commit 7d8e9a90509f ("drm/msm/dsi: move DSI host powerup to modeset time") caused sc7180 Chromebooks that use the parade-ps8640 bridge chip to fail to turn the display back on after it turns off. Unfortunately, it doesn't look easy to fix the parade-ps8640 driver to handle the new power sequence.

Re: [PATCH v2] drm/probe-helper: Default to 640x480 if no EDID

Hi, On Wed, May 11, 2022 at 2:32 PM Doug Anderson wrote: > > Hi, > > On Wed, May 11, 2022 at 12:14 AM Thomas Zimmermann > wrote: > > > > Hi > > > > Am 10.05.22 um 22:51 schrieb Douglas Anderson: > > > If we're unable to read the EDID for a display because it's corrupt / > > > bogus / invalid

[PATCH v3] drm/probe-helper: Make 640x480 first if no EDID

If we're unable to read the EDID for a display because it's corrupt / bogus / invalid then we'll add a set of standard modes for the display. Since we have no true information about the connected display, these modes are essentially guesses but better than nothing. None of the modes returned is

Re: [PATCH 16/25] drm/msm/dpu: drop EAGAIN check from dpu_format_populate_layout

On 2/9/2022 9:25 AM, Dmitry Baryshkov wrote: Since layout is not cached anymore, drop comparison against previous layout and corresponding EAGAIN handling. Signed-off-by: Dmitry Baryshkov Isnt this preventing the usermode from programming the same address again? I thought that this check

Re: [PATCH 15/25] drm/msm/dpu: remove dpu_hw_fmt_layout from struct dpu_hw_pipe_cfg

On 2/9/2022 9:25 AM, Dmitry Baryshkov wrote: Remove dpu_hw_fmt_layout instance from struct dpu_hw_fmt_layout, leaving only src_rect and dst_rect. I believe you meant "remove dpu_hw_fmt_layout instance from struct dpu_hw_pipe_cfg" ?. Otherwise nothing wrong with the change as such, but

Re: [PATCH 14/25] drm/msm/dpu: move stride programming to dpu_hw_sspp_setup_sourceaddress

On 2/9/2022 9:25 AM, Dmitry Baryshkov wrote: Move stride programming to dpu_hw_sspp_setup_sourceaddress(), so that dpu_hw_sspp_setup_rects() programs only source and destination rectangles. Signed-off-by: Dmitry Baryshkov This separation is logically correct, but there is another codepath

Re: [git pull] drm fixes for 5.18-rc7

The pull request you sent on Fri, 13 May 2022 15:07:55 +1000: > git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-05-13 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/10b4b67ab58248636723af181734b9574be05ade Thank you! -- Deet-doot-dot, I am a bot.

Re: [Intel-gfx] [PATCH] drm/i915/guc/rc: Use i915_probe_error instead of drm_error

Nit: not sure why we use ERR_PTR for int when calling func was also returning an int. Anyway, that was how the original code was, so: Reviewed-by: Alan Previn On Thu, 2022-05-05 at 22:41 -0700, Vinay Belgaumkar wrote: > To avoid false positives in error injection cases. > > Signed-off-by:

Re: [PATCH] drm/amd/display: clean up some inconsistent indenting

Applied. Thanks! Alex On Thu, May 12, 2022 at 3:19 AM Jiapeng Chong wrote: > > Eliminate the follow smatch warning: > > drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:9687 > amdgpu_dm_atomic_commit_tail() warn: inconsistent indenting. > > Reported-by: Abaci Robot > Signed-off-by:

Re: [PATCH] drm/amd/display: Remove macro DC_DEFAULT_LOG_MASK

On Fri, May 13, 2022 at 3:20 AM pengfuyuan wrote: > > [Why] > The DC_DEFAULT_LOG_MASK macro has not been used for a long time, so remove it. I'm sure there are lots of macros in the driver that are not used at the moment. Any particular reason to remove it? DC_MIN_LOG_MASK doesn't appear to be

[GIT PULL] etnaviv-next for 5.19

Hi Dave, hi Daniel, please pull the following etnaviv changes for the next merge window, which fix address space collisions in some edge cases when userspace is using softpin and cleans up the MMU reference handling a bit. Regards, Lucas The following changes since commit

Re: [PATCH v7 0/6] Proposal for a GPU cgroup controller

Hello, On Thu, May 12, 2022 at 08:43:52PM -0700, T.J. Mercier wrote: > > I'm actually happy I've asked this question, wasn't silly after all. I > > think the > > problem here is a naming issue. What you really are monitor is "video > > memory", > > which consist of a memory segment allocated to

Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct

On Fri, 2022-05-13 at 16:18 +0200, Hans de Goede wrote: > Hi, > > On 5/13/22 15:25, Zack Rusin wrote: > > > > > > > On May 13, 2022, at 3:43 AM, Thorsten Leemhuis > > > mailto:regressi...@leemhuis.info>> wrote: > > > > > > CCing airlied > > > > > > On 09.05.22 14:02, Javier Martinez Canillas

[pull] vmwgfx- drm-fixes-5.18

Hi Dave, Daniel. Sorry for the late email, I missed some important fixes for vmwgfx. The following changes since commit 5005e9814698f47c5a3698fcc56c9f5e6f1d4644: Merge tag 'amd-drm-fixes-5.18-2022-05-11' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes (2022-05-13 10:40:56

[PATCH 5.10 04/10] drm/amd/display/dc/gpio/gpio_service: Pass around correct dce_{version, environment} types

From: Lee Jones commit 353f7f3a9dd5fd2833b6462bac89ec1654c9c3aa upstream. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c: In function ‘dal_gpio_service_create’: drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:71:4:

[PATCH 5.4 03/18] drm/amd/display/dc/gpio/gpio_service: Pass around correct dce_{version, environment} types

From: Lee Jones commit 353f7f3a9dd5fd2833b6462bac89ec1654c9c3aa upstream. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c: In function ‘dal_gpio_service_create’: drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:71:4:

[PATCH 4.19 03/15] drm/amd/display/dc/gpio/gpio_service: Pass around correct dce_{version, environment} types

From: Lee Jones commit 353f7f3a9dd5fd2833b6462bac89ec1654c9c3aa upstream. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c: In function ‘dal_gpio_service_create’: drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:71:4:

Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct

Hi, On 5/13/22 15:25, Zack Rusin wrote: > > >> On May 13, 2022, at 3:43 AM, Thorsten Leemhuis > > wrote: >> >> CCing airlied >> >> On 09.05.22 14:02, Javier Martinez Canillas wrote: >>> On 5/9/22 13:55, Hans de Goede wrote: >>> [snip] >> >> Fixes:

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

On Wed, May 11, 2022 at 9:17 PM Marek Vasut wrote: > > On 5/11/22 16:58, Marek Szyprowski wrote: > > Hi Dave, > > > > On 05.04.2022 13:43, Dave Stevenson wrote: > >> On Fri, 18 Mar 2022 at 12:25, Dave Stevenson > >> wrote: > >>> On Fri, 4 Mar 2022 at 15:18, Dave Stevenson > >>> wrote: >

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

On Wed, May 11, 2022 at 8:28 PM Marek Szyprowski wrote: > > Hi Dave, > > On 05.04.2022 13:43, Dave Stevenson wrote: > > On Fri, 18 Mar 2022 at 12:25, Dave Stevenson > > wrote: > >> On Fri, 4 Mar 2022 at 15:18, Dave Stevenson > >> wrote: > >>> Hi All > >> A gentle ping on this series. Any

[PATCH][next] drm/rockchip: Fix spelling mistake "aligened" -> "aligned"

There is a spelling mistake in a drm_err message. Fix it. Signed-off-by: Colin Ian King --- drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c

Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct

On 13.05.22 15:25, Zack Rusin wrote: >> On May 13, 2022, at 3:43 AM, Thorsten Leemhuis >> mailto:regressi...@leemhuis.info>> wrote: >> >> CCing airlied >> >> On 09.05.22 14:02, Javier Martinez Canillas wrote: >>> On 5/9/22 13:55, Hans de Goede wrote: >>> [snip] >> >> Fixes: dabdcdc9822a

Re: [LINUX PATCH 2/2] drm: xlnx: dsi: driver for Xilinx DSI Tx subsystem

Hi GVRao, Thank you for the patch. On Thu, May 12, 2022 at 07:23:13PM +0530, Venkateshwar Rao Gannavarapu wrote: > The Xilinx MIPI DSI Tx Subsystem soft IP is used to display video > data from AXI-4 stream interface. > > It supports upto 4 lanes, optional register interface for the DPHY > and

Re: [LINUX PATCH 1/2] dt-bindings: display: xlnx: Add DSI 2.0 Tx subsystem documentation

Hi GVRao, Thank you for the patch. On Thu, May 12, 2022 at 07:23:12PM +0530, Venkateshwar Rao Gannavarapu wrote: > This patch adds dt binding for Xilinx DSI TX subsystem. > > The Xilinx MIPI DSI (Display serial interface) Transmitter Subsystem > implements the Mobile Industry Processor

Re: Improve TTMs empty object handling

On Fri, 13 May 2022 at 14:03, Christian König wrote: > > Am 13.05.22 um 11:21 schrieb Matthew Auld: > > On Mon, 9 May 2022 at 14:09, Christian König > > wrote: > >> Hi everyone, > >> > >> re-sending this because Daniel was requesting a background why this is > >> useful. > >> > >> When TTM

Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct

On May 13, 2022, at 3:43 AM, Thorsten Leemhuis mailto:regressi...@leemhuis.info>> wrote: CCing airlied On 09.05.22 14:02, Javier Martinez Canillas wrote: On 5/9/22 13:55, Hans de Goede wrote: [snip] Fixes: dabdcdc9822a ("drm/vmwgfx: Switch to mode_cmd2") BugLink:

Re: Improve TTMs empty object handling

Am 13.05.22 um 11:21 schrieb Matthew Auld: On Mon, 9 May 2022 at 14:09, Christian König wrote: Hi everyone, re-sending this because Daniel was requesting a background why this is useful. When TTM creates a buffer this object initially should not have any backing store and there no resource

Re: [PATCH v3 1/3] dt-bindings: mediatek: add vdosys1 RDMA definition for mt8195

On Thu, 12 May 2022 16:05:21 +0800, Rex-BC Chen wrote: > From: "Nancy.Lin" > > Add vdosys1 RDMA definition. > > Signed-off-by: Nancy.Lin > Reviewed-by: AngeloGioacchino Del Regno > > --- > .../display/mediatek/mediatek,mdp-rdma.yaml | 88 +++ > 1 file changed, 88

Re: [PATCH v3 3/3] dt-bindings: mediatek: add ethdr definition for mt8195

On Thu, 12 May 2022 16:05:23 +0800, Rex-BC Chen wrote: > From: "Nancy.Lin" > > Add vdosys1 ETHDR definition. > > Signed-off-by: Nancy.Lin > Reviewed-by: Chun-Kuang Hu > Reviewed-by: AngeloGioacchino Del Regno > > --- > .../display/mediatek/mediatek,ethdr.yaml | 188 ++

Re: [PATCH v3] uapi/drm/i915: Document memory residency and Flat-CCS capability of obj

On 02/05/2022 17:15, Ramalingam C wrote: Capture the impact of memory region preference list of the objects, on their memory residency and Flat-CCS capability. v2: Fix the Flat-CCS capability of an obj with {lmem, smem} preference list [Thomas] v3: Reworded the doc [Matt]

Re: [PATCH] fbdev: vesafb: Allow to be built if COMPILE_TEST is enabled

On 5/5/22 14:04, Javier Martinez Canillas wrote: > The driver has runtime but no build time dependency with X86, so it can > be built for testing purposes if the COMPILE_TEST option is enabled. > > This is useful to have more build coverage and make sure that the driver > is not affected by

Re: [PATCH v5 3/7] fbdev: Restart conflicting fb removal loop when unregistering devices

On 5/11/22 13:30, Javier Martinez Canillas wrote: > Drivers that want to remove registered conflicting framebuffers prior to > register their own framebuffer, calls remove_conflicting_framebuffers(). > > This function takes the registration_lock mutex, to prevent a races when > drivers register

Re: [PATCH 1/2] drm/msm: don't free the IRQ if it was not requested

On 12/05/2022 04:41, Stephen Boyd wrote: Quoting Dmitry Baryshkov (2022-05-11 18:30:55) On 12/05/2022 04:29, Stephen Boyd wrote: Quoting Dmitry Baryshkov (2022-05-11 18:01:31) On Thu, 12 May 2022 at 03:54, Stephen Boyd wrote: Quoting Dmitry Baryshkov (2022-05-06 18:00:20) Does this

Re: [PATCH v1 13/15] mm: handling Non-LRU pages returned by vm_normal_pages

On Thu, May 12, 2022 at 05:33:44PM -0500, Sierra Guiza, Alejandro (Alex) wrote: > > On 5/11/2022 1:50 PM, Jason Gunthorpe wrote: > > On Thu, May 05, 2022 at 04:34:36PM -0500, Alex Sierra wrote: > > > > > diff --git a/mm/memory.c b/mm/memory.c > > > index 76e3af9639d9..892c4cc54dc2 100644 > > >

Re: [PATCH 2/2] drm/msm: push IRQ setup into individual drivers

On 13/05/2022 01:54, Abhinav Kumar wrote: On 5/6/2022 6:00 PM, Dmitry Baryshkov wrote: Afther the commit f026e431cf86 ("drm/msm: Convert to Linux IRQ interfaces") converted MSM DRM driver to handle IRQs on it's own (rather than using the DRM IRQ mid-layer), there is little point in keeping

Re: [PATCH v5 0/7] Fix some races between sysfb device registration and drivers probe

Hi Javier Am 13.05.22 um 13:10 schrieb Javier Martinez Canillas: ... We already track the memory ranges in drm aperture helpers. We'd need to move the code to a more prominent location (e.g., ) and change fbdev to use it. Sysfb and DT code needs to insert platform devices upon creation. We can

[PATCH V3 RESEND] dma-buf: ensure unique directory name for dmabuf stats

The dmabuf file uses get_next_ino()(through dma_buf_getfile() -> alloc_anon_inode()) to get an inode number and uses the same as a directory name under /sys/kernel/dmabuf/buffers/. This directory is used to collect the dmabuf stats and it is created through dma_buf_stats_setup(). At current,

Re: [PATCH v5 0/7] Fix some races between sysfb device registration and drivers probe

Hello Thomas, Thanks for your feedback and comments. On 5/13/22 12:48, Thomas Zimmermann wrote: > Hi Javier, > > thanks again for providing the examples. I think I now better get what > you're trying to solve. > You are welcome. > First of all let's merge patch 3, as it seems unrelated. >

Re: [LINUX PATCH 2/2] drm: xlnx: dsi: driver for Xilinx DSI Tx subsystem

Hi Venkateshwar, On Thu, May 12, 2022 at 07:23:13PM +0530, Venkateshwar Rao Gannavarapu wrote: > The Xilinx MIPI DSI Tx Subsystem soft IP is used to display video > data from AXI-4 stream interface. > > It supports upto 4 lanes, optional register interface for the DPHY > and multiple RGB color

Re: [PATCH 1/3] usb: gadget: add Aspeed ast2600 udc driver

Hi Neal, I love your patch! Perhaps something to improve: [auto build test WARNING on usb/usb-testing] [also build test WARNING on robh/for-next v5.18-rc6 next-20220513] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base

Re: [PATCH v5 0/7] Fix some races between sysfb device registration and drivers probe

Hi Javier, thanks again for providing the examples. I think I now better get what you're trying to solve. First of all let's merge patch 3, as it seems unrelated. For the other patches, I'd like to take a step back and try to solve the broader problem. IIRC we talked about this briefly

Re: [PATCH v2 11/11] dt-bindings: display: convert Arm Komeda to DT schema

That seems sensible to me. It matches the kind of DT content I know works. It's certainly more detailed now. On 5/6/22 15:05, Andre Przywara wrote: The Arm Komeda (aka Mali-D71) is a display controller that scans out a framebuffer and hands a signal to a digital encoder to generate a DVI or

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

Am 13.05.22 um 12:38 schrieb Charan Teja Kalla: On 5/13/2022 3:59 PM, Christian König wrote: Am 13.05.22 um 12:18 schrieb Charan Teja Kalla: On 5/13/2022 3:41 PM, Greg KH wrote: Reported-by: kernel test robot The trest robot did not say that the dmabuf stat name was being duplicated, did

RE: [PATCH v4] drm/ast: Create the driver for ASPEED proprietory Display-Port

Hi Thomas, -Original Message- From: Thomas Zimmermann [mailto:tzimmerm...@suse.de] Sent: Friday, May 13, 2022 6:21 PM To: Kuo-Hsiang Chou ; dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org Subject: Re: [PATCH v4] drm/ast: Create the driver for ASPEED proprietory

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

On 5/13/2022 3:59 PM, Christian König wrote: > Am 13.05.22 um 12:18 schrieb Charan Teja Kalla: >> On 5/13/2022 3:41 PM, Greg KH wrote: Reported-by: kernel test robot >>> The trest robot did not say that the dmabuf stat name was being >>> duplicated, did it? >>> >> It reported a printk

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

Am 13.05.22 um 12:18 schrieb Charan Teja Kalla: On 5/13/2022 3:41 PM, Greg KH wrote: Reported-by: kernel test robot The trest robot did not say that the dmabuf stat name was being duplicated, did it? It reported a printk warning on V2[1]. Should we remove this on V3? We only add the

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

On Fri, May 13, 2022 at 03:48:23PM +0530, Charan Teja Kalla wrote: > > On 5/13/2022 3:41 PM, Greg KH wrote: > >> Reported-by: kernel test robot > > The trest robot did not say that the dmabuf stat name was being > > duplicated, did it? > > > > It reported a printk warning on V2[1]. Should we

Re: [PATCH v4] drm/ast: Create the driver for ASPEED proprietory Display-Port

Hi Am 13.05.22 um 11:07 schrieb Kuo-Hsiang Chou: -Original Message- From: Thomas Zimmermann [mailto:tzimmerm...@suse.de] Sent: Tuesday, May 10, 2022 6:56 PM To: Kuo-Hsiang Chou ; dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org Subject: Re: [PATCH v4] drm/ast: Create the

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

On 5/13/2022 3:41 PM, Greg KH wrote: >> Reported-by: kernel test robot > The trest robot did not say that the dmabuf stat name was being > duplicated, did it? > It reported a printk warning on V2[1]. Should we remove this on V3? @Christian: Could you please drop this tag while merging? [1]

Re: DSI Bridge switching

Hi Maxime, On Thu, Mar 10, 2022 at 4:05 PM Maxime Ripard wrote: > > On Wed, Mar 09, 2022 at 06:45:10PM -0600, Adam Ford wrote: > > On Wed, Mar 9, 2022 at 1:11 PM Jagan Teki > > wrote: > > > > > > or a Hi All, > > > > > > On Thu, Oct 14, 2021 at 6:45 PM Jagan Teki > > > wrote: > > > > > > >

Re: [PATCH v2] drm: rcar-du: Fix Alpha blending issue on Gen3

Quoting Biju Das (2022-04-26 09:41:57) > From: LUU HOAI > > As per R-Car-Gen3_Common_OPC_Customer_Notifications_V30.1.pdf, > unexpected image output(such as incorrect colors or planes being > invisible) can happen on the below conditions, as PnALPHAR register > is not initialized by reset. > >

Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

On Fri, May 13, 2022 at 03:08:09PM +0530, Charan Teja Kalla wrote: > The dmabuf file uses get_next_ino()(through dma_buf_getfile() -> > alloc_anon_inode()) to get an inode number and uses the same as a > directory name under /sys/kernel/dmabuf/buffers/. This directory is > used to collect the

Re: [PATCH] drm/i915: Fix CFI violation with show_dynamic_id()

On 12/05/2022 22:17, Nathan Chancellor wrote: When an attribute group is created with sysfs_create_group(), the ->sysfs_ops() callback is set to kobj_sysfs_ops, which sets the ->show() callback to kobj_attr_show(). kobj_attr_show() uses container_of() to get the ->show() callback from the

[PATCH V3] dma-buf: ensure unique directory name for dmabuf stats

The dmabuf file uses get_next_ino()(through dma_buf_getfile() -> alloc_anon_inode()) to get an inode number and uses the same as a directory name under /sys/kernel/dmabuf/buffers/. This directory is used to collect the dmabuf stats and it is created through dma_buf_stats_setup(). At current,

Re: Improve TTMs empty object handling

On Mon, 9 May 2022 at 14:09, Christian König wrote: > > Hi everyone, > > re-sending this because Daniel was requesting a background why this is > useful. > > When TTM creates a buffer this object initially should not have any > backing store and there no resource object associated with it. The

RE: [PATCH v4] drm/ast: Create the driver for ASPEED proprietory Display-Port

-Original Message- From: Thomas Zimmermann [mailto:tzimmerm...@suse.de] Sent: Tuesday, May 10, 2022 6:56 PM To: Kuo-Hsiang Chou ; dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org Subject: Re: [PATCH v4] drm/ast: Create the driver for ASPEED proprietory Display-Port Hi

Re: [PATCH 3/3] dt-bindings: usb: add documentation for aspeed udc

On 13/05/2022 08:57, Neal Liu wrote: > Add device tree binding documentation for the Aspeed USB2.0 Device > Controller. > > Signed-off-by: Neal Liu > --- > .../devicetree/bindings/usb/aspeed,udc.yaml | 52 +++ > 1 file changed, 52 insertions(+) > create mode 100644

[PATCH v3] drm/mgag200: Enable atomic gamma lut update

Add support for atomic update of gamma lut. With this patch the "Night light" feature of gnome3 is working properly on mgag200. v2: - Add a default linear gamma function - renamed functions with mgag200 prefix - use format's 4cc code instead of bit depth - use better interpolation for 16bits

[PATCH] drm/exynos: mic: Rework initialization

Commit dd8b6803bc49 ("exynos: drm: dsi: Attach in_bridge in MIC driver") moved Exynos MIC attaching from DSI to MIC driver. However the method proposed there is incomplete and cannot really work. To properly attach it to the bridge chain, access to the respective encoder is needed. The Exynos MIC

Re: [PATCH v3 3/3] dt-bindings: mediatek: add ethdr definition for mt8195

On 12/05/2022 10:05, Rex-BC Chen wrote: > From: "Nancy.Lin" > > Add vdosys1 ETHDR definition. > > Signed-off-by: Nancy.Lin > Reviewed-by: Chun-Kuang Hu > Reviewed-by: AngeloGioacchino Del Regno > Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof

Re: [PATCH v3 2/3] dt-bindings: reset: mt8195: add vdosys1 reset control bit

On 12/05/2022 10:05, Rex-BC Chen wrote: > From: "Nancy.Lin" > > Add vdosys1 reset control bit for MT8195 platform. > > Signed-off-by: Nancy.Lin > Reviewed-by: Chun-Kuang Hu > Reviewed-by: AngeloGioacchino Del Regno > > Reviewed-by: Rex-BC Chen Acked-by: Krzysztof Kozlowski Best

Re: [PATCH v3 1/3] dt-bindings: mediatek: add vdosys1 RDMA definition for mt8195

On 12/05/2022 10:05, Rex-BC Chen wrote: > From: "Nancy.Lin" > > Add vdosys1 RDMA definition. > > Signed-off-by: Nancy.Lin > Reviewed-by: AngeloGioacchino Del Regno > Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof

Re: [5.18 regression] drm/i915 BYT rendering broken due to "Remove short-term pins from execbuf, v6" #forregzbot

TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. On 09.05.22 09:01, Thorsten Leemhuis wrote: > [TLDR: I'm adding this regression

Re: [PATCH] drm/amd/display: Remove macro DC_DEFAULT_LOG_MASK

/0day-ci/archive/20220513/202205131519.0pphvmxz-...@intel.com/config) compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 9519dacab7b8afd537811fc2abaceb4d14f4e16a) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross

Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct

CCing airlied On 09.05.22 14:02, Javier Martinez Canillas wrote: > On 5/9/22 13:55, Hans de Goede wrote: > [snip] Fixes: dabdcdc9822a ("drm/vmwgfx: Switch to mode_cmd2") BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2072556 Signed-off-by: Hans de Goede --- >>> >>>

Re: [PATCH v20 8/8] soc: mediatek: remove DDP_DOMPONENT_DITHER from enum

Hi Chun-Kuang, On 02/05/2022 00:54, Chun-Kuang Hu wrote: Hi, Matthias: Matthias Brugger 於 2022年4月22日 週五 下午8:42寫道： On 19/04/2022 11:41, jason-jh.lin wrote: After mmsys and drm change DITHER enum to DDP_COMPONENT_DITHER0, mmsys header can remove the useless DDP_COMPONENT_DITHER enum.

[PULL] drm-misc-fixes

Hi Dave, Daniel, Here's this week drm-misc-fixes. drm-misc-next-fixes is empty at the moment, so there won't be a PR for it this week. Thanks! Maxime drm-misc-fixes-2022-05-13: Multiple fixes to fbdev to address a regression at unregistration, an iommu detection improvement for nouveau, a

[PATCH] drm/amd/display: Remove macro DC_DEFAULT_LOG_MASK

[Why] The DC_DEFAULT_LOG_MASK macro has not been used for a long time, so remove it. Signed-off-by: pengfuyuan --- .../drm/amd/display/include/logger_types.h| 33 --- 1 file changed, 33 deletions(-) diff --git a/drivers/gpu/drm/amd/display/include/logger_types.h