Re: [PATCH v6 3/8] drm/bridge: mhdp8546: Add minimal format negotiation

2023-05-28 Thread Aradhya Bhatia
Hi Tomi, Thank you for taking a look at this. On 26/05/23 14:59, Tomi Valkeinen wrote: > On 16/05/2023 17:25, Aradhya Bhatia wrote: >> Hi Neil, >> >> Thank you for reviewing the patch. >> >> On 16-May-23 12:51, Neil Armstrong wrote: >>> On 15/05/2023 17:59, Aradhya Bhatia wrote: Hi Tomi, >>>

RE: [PATCH v2 3/7] drm/i915: Fix CHV CGM CSC coefficient sign handling

2023-05-28 Thread Shankar, Uma
> -Original Message- > From: Ville Syrjälä > Sent: Friday, May 26, 2023 7:18 PM > To: Shankar, Uma > Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org > Subject: Re: [PATCH v2 3/7] drm/i915: Fix CHV CGM CSC coefficient sign > handling > > On Thu, May 25, 2023 at 08:

Re: [PATCH] arm64: dts: mediatek: mt8173-elm: remove panel model number in DT

2023-05-28 Thread Hsin-Yi Wang
On Mon, May 29, 2023 at 12:14 PM Icenowy Zheng wrote: > > 在 2023-05-26星期五的 07:24 -0700,Doug Anderson写道: > > Hi, > > > > On Fri, May 26, 2023 at 3:09 AM Icenowy Zheng wrote: > > > > > > Currently a specific panel number is used in the Elm DTSI, which is > > > corresponded to a 12" panel. However,

Re: [PATCH 0/5] MDSS reg bus interconnect

2023-05-28 Thread Dmitry Baryshkov
On Mon, 17 Apr 2023 at 18:30, Konrad Dybcio wrote: > > Apart from the already handled data bus (MAS_MDP_Pn<->DDR), there's > another path that needs to be handled to ensure MDSS functions properly, > namely the "reg bus", a.k.a the CPU-MDSS interconnect. > > Gating that path may have a variety of

Re: [PATCH V2] dt-bindings: bridge: samsung-dsim: Make some flags optional

2023-05-28 Thread Fabio Estevam
On Sun, May 28, 2023 at 10:27 AM Adam Ford wrote: > > In the event a device is connected to the samsung-dsim > controller that doesn't support the burst-clock, the > driver is able to get the requested pixel clock from the > attached device or bridge. In these instances, the > samsung,burst-clock

Re: [PATCH RFC 01/10] drm/panel: Clean up SOFEF00 config dependencies

2023-05-28 Thread Caleb Connolly
On 21/05/2023 22:23, Marijn Suijten wrote: > As per the config name this Display IC features a DSI command-mode > interface (or the command to switch to video mode is not > known/documented) and does not use any of the video-mode helper > utilities, hence should not select VIDEOMODE_HELPERS. In

[PATCH][next] drm/amdgpu/discovery: Replace fake flex-arrays with flexible-array members

2023-05-28 Thread Gustavo A. R. Silva
Zero-length and one-element arrays are deprecated, and we are moving towards adopting C99 flexible-array members, instead. Use the DECLARE_FLEX_ARRAY() helper macro to transform zero-length arrays in a union into flexible-array members. And replace a one-element array with a C99 flexible-array mem

[PATCH 6.1 065/119] drm: fix drmm_mutex_init()

2023-05-28 Thread Greg Kroah-Hartman
From: Matthew Auld commit c21f11d182c2180d8b90eaff84f574cfa845b250 upstream. In mutex_init() lockdep identifies a lock by defining a special static key for each lock class. However if we wrap the macro in a function, like in drmm_mutex_init(), we end up generating: int drmm_mutex_init(struct dr

[PATCH 6.3 069/127] drm: fix drmm_mutex_init()

2023-05-28 Thread Greg Kroah-Hartman
From: Matthew Auld commit c21f11d182c2180d8b90eaff84f574cfa845b250 upstream. In mutex_init() lockdep identifies a lock by defining a special static key for each lock class. However if we wrap the macro in a function, like in drmm_mutex_init(), we end up generating: int drmm_mutex_init(struct dr

Re: [PATCH V2] dt-bindings: bridge: samsung-dsim: Make some flags optional

2023-05-28 Thread Adam Ford
On Sun, May 28, 2023 at 8:34 AM Jagan Teki wrote: > > On Sun, May 28, 2023 at 6:57 PM Adam Ford wrote: > > > > In the event a device is connected to the samsung-dsim > > controller that doesn't support the burst-clock, the > > driver is able to get the requested pixel clock from the > > attached

Re: [PATCH v2 2/3] arm64: dts: qcom: sc8280xp: Add GPU related nodes

2023-05-28 Thread Manivannan Sadhasivam
On Tue, May 23, 2023 at 09:59:53AM +0200, Konrad Dybcio wrote: > > > On 23.05.2023 03:15, Bjorn Andersson wrote: > > From: Bjorn Andersson > > > > Add Adreno SMMU, GPU clock controller, GMU and GPU nodes for the > > SC8280XP. > > > > Signed-off-by: Bjorn Andersson > > Signed-off-by: Bjorn And

Patch "drm: fix drmm_mutex_init()" has been added to the 6.3-stable tree

2023-05-28 Thread gregkh
This is a note to let you know that I've just added the patch titled drm: fix drmm_mutex_init() to the 6.3-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: drm-fix-drmm_mutex_init.patc

Patch "drm: fix drmm_mutex_init()" has been added to the 6.1-stable tree

2023-05-28 Thread gregkh
This is a note to let you know that I've just added the patch titled drm: fix drmm_mutex_init() to the 6.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: drm-fix-drmm_mutex_init.patc

[Bug 217499] NVIDIA drivers fail to install on 6.4.0-rc3-1-mainline kernel

2023-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217499 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED Reso

Re: [PATCH] drm: Remove unnecessary (void*) conversions

2023-05-28 Thread Su Hui
On 2023/5/26 15:27, Christian König wrote: Am 26.05.23 um 05:32 schrieb Su Hui: Pointer variables of (void*) type do not require type cast. Please split that up by subsystem/driver. Taking it through the misc tree might just cause merge conflicts. Sorry for that, I will split it and send a

Re: [Nouveau] [PATCH v2] drm/nouveau: bring back blit subchannel for pre nv50 GPUs

2023-05-28 Thread Ilia Mirkin
On Fri, May 26, 2023 at 5:11 AM Karol Herbst wrote: > > 1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128 > was important as otherwise the GPU spams us with `CACHE_ERROR` messages. > > We use the blit subchannel inside our vblank handling, so we should keep > at least this par

Re: [PATCH] arm64: dts: mediatek: mt8173-elm: remove panel model number in DT

2023-05-28 Thread Icenowy Zheng
在 2023-05-26星期五的 07:24 -0700,Doug Anderson写道: > Hi, > > On Fri, May 26, 2023 at 3:09 AM Icenowy Zheng wrote: > > > > Currently a specific panel number is used in the Elm DTSI, which is > > corresponded to a 12" panel. However, according to the official > > Chrome > > OS devices document, Elm ref

[PATCH] arm64: dts: mediatek: mt8173-elm: remove panel model number in DT

2023-05-28 Thread Icenowy Zheng
Currently a specific panel number is used in the Elm DTSI, which is corresponded to a 12" panel. However, according to the official Chrome OS devices document, Elm refers to Acer Chromebook R13, which, as the name specifies, uses a 13.3" panel, which comes with EDID information. As the kernel curr

[PATCH] drm/radeon: fix race condition UAF in radeon_gem_set_domain_ioctl

2023-05-28 Thread Min Li
Userspace can race to free the gobj(robj converted from), robj should not be accessed again after drm_gem_object_put, otherwith it will result in use-after-free. Signed-off-by: Min Li --- drivers/gpu/drm/radeon/radeon_gem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driv

[PATCH] drm/exynos: fix race condition UAF in exynos_g2d_exec_ioctl

2023-05-28 Thread Min Li
If it is async, runqueue_node is freed in g2d_runqueue_worker on another worker thread. So in extreme cases, if g2d_runqueue_worker runs first, and then executes the following if statement, there will be use-after-free. Signed-off-by: Min Li --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 2 +- 1

[Bug 217499] NVIDIA drivers fail to install on 6.4.0-rc3-1-mainline kernel

2023-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217499 Wessel (wessel.working+ker...@gmail.com) changed: What|Removed |Added Kernel Version||6.4.0-rc3-1-mai

[Bug 217499] NVIDIA drivers fail to install on 6.4.0-rc3-1-mainline kernel

2023-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217499 Wessel (wessel.working+ker...@gmail.com) changed: What|Removed |Added URL||https://forum.g

[Bug 217499] New: NVIDIA drivers fail to install on 6.4.0-rc3-1-mainline kernel

2023-05-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=217499 Bug ID: 217499 Summary: NVIDIA drivers fail to install on 6.4.0-rc3-1-mainline kernel Product: Drivers Version: 2.5 Hardware: Intel OS: Linux St

[PATCH 2/3] dw-hdmi: truly enforce 420-only formats when drm mode demands it

2023-05-28 Thread Adrián Larumbe
The current output bus format selection logic is enforcing YUV420 even when the drm mode allows for other bus formats as well. Fix it by adding check for 420-only drm modes. Signed-off-by: Adrián Larumbe --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 7 --- 1 file changed, 4 insertions(+),

[PATCH 3/3] dw-hdmi: remove dead code and fix indentation

2023-05-28 Thread Adrián Larumbe
Signed-off-by: Adrián Larumbe --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 22 -- 1 file changed, 4 insertions(+), 18 deletions(-) diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c index 1afb8f2603a0..0accfb51509c 100644 --

[PATCH 1/3] drm/meson: dw-hdmi: change YUV420 selection logic at clock setup

2023-05-28 Thread Adrián Larumbe
Right now clocking value selection code is prioritising RGB, YUV444 modes over YUV420 for HDMI2 sinks. However, because of the bus format selection procedure in dw-hdmi, for HDMI2 sinks YUV420 is the format that will always be picked during the drm bridge chain check stage. Later on dw_hdmi_setup

[PATCH 0/3] Add additional YUV420 bus format check for dw-meson's bridge enable

2023-05-28 Thread Adrián Larumbe
This is a belated follow-up on https://lore.kernel.org/dri-devel/20220515204412.2733803-1-adrian.laru...@collabora.com/ Commit e67f6037ae1be34b2b68 ("drm/meson: split out encoder from meson_dw_hdmi") broke 4K display modes for me, and I discovered it was because the right pixel clock wasn't being

Re: [PATCH V2] dt-bindings: bridge: samsung-dsim: Make some flags optional

2023-05-28 Thread Jagan Teki
On Sun, May 28, 2023 at 6:57 PM Adam Ford wrote: > > In the event a device is connected to the samsung-dsim > controller that doesn't support the burst-clock, the > driver is able to get the requested pixel clock from the > attached device or bridge. In these instances, the > samsung,burst-clock-

[PATCH V2] dt-bindings: bridge: samsung-dsim: Make some flags optional

2023-05-28 Thread Adam Ford
In the event a device is connected to the samsung-dsim controller that doesn't support the burst-clock, the driver is able to get the requested pixel clock from the attached device or bridge. In these instances, the samsung,burst-clock-frequency isn't needed, so remove it from the required list.

[PATCH 2/3] accel/habanalabs: add event queue extra validation

2023-05-28 Thread Oded Gabbay
From: Ofir Bitton In order to increase reliability of the event queue interface, we apply to Gaudi2 the same mechanism we have in Gaudi1. The extra validation is basically checking that the received event index matches the expected index. Signed-off-by: Ofir Bitton Reviewed-by: Oded Gabbay Sig

[PATCH 3/3] accel/habanalabs: refactor error info reset

2023-05-28 Thread Oded Gabbay
From: Dani Liberman Moved error info reset code to single function for future use from other places in the driver. Signed-off-by: Dani Liberman Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/accel/habanalabs/common/device.c | 8 drivers/accel/habanalabs/comm

[PATCH 1/3] accel/habanalabs: unsecure TSB_CFG_MTRR regs

2023-05-28 Thread Oded Gabbay
From: Ofir Bitton In order to utilize Engine Barrier padding, user must have access to this register set. Signed-off-by: Ofir Bitton Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay --- drivers/accel/habanalabs/gaudi2/gaudi2_security.c | 4 1 file changed, 4 insertions(+) diff --git