On Fri, Jul 18, 2025 at 01:17:25PM -0300, Luiz Otavio Mello wrote:
> i915 is the only remaining user of struct_mutex lock.
>
> Move it from drm_device to drm_i915_private so it is only used within
> the i915 driver.
>
> Signed-off-by: Luiz Otavio Mello
> ---
> drivers/gpu/drm/i915/gt/uc/intel_g
While LT9611UXC is a DSI-to-HDMI bridge, it implements all HDMI-related
functions internally, in the firmware, thus it doesn't make sense to
implement DRM_BRIDGE_OP_HDMI. However it is possible to implement
DRM_BRIDGE_OP_HDMI_AUDIO, streamlining HDMI audio plumbing (which
includes plugged notificat
Use DRM HDMI audio helpers in order to implement HDMI audio support for
Lontium LT9611UXC bridge.
Signed-off-by: Dmitry Baryshkov
---
Dmitry Baryshkov (2):
drm/bridge: add connector argument to .hpd_notify callback
drm/bridge: lontium-lt9611uxc: switch to HDMI audio helpers
drivers/
Drivers might need to update DRM connector in the
drm_bridge_funcs.hpd_notify callback (e.g. it might be necessary to
update EDID before setting ELD). Add corresponding argument to the
callback.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/display/drm_bridge_connector.c | 2 +-
drivers/gp
On Fri, Jul 18, 2025 at 05:25:25PM +0200, Javier Martinez Canillas wrote:
> The kernel test robot reported that sparse gives the following warnings:
>
> make C=2 M=drivers/gpu/drm/sitronix/
> CC [M] st7571-i2c.o
> CHECK st7571-i2c.c
> st7571-i2c.c:1027:26: warning: symbol 'st7567_config' wa
On Sun, Jul 20, 2025 at 05:31:54PM +0530, Kaustabh Chakraborty wrote:
> Document the Synaptics TDDI (Touch/Display Integration) panel hardware.
> Along with the MIPI-DSI panel, these devices also have an in-built LED
> backlight device and a touchscreen, all packed together in a single chip.
>
> A
On Sun, Jul 20, 2025 at 05:31:55PM +0530, Kaustabh Chakraborty wrote:
> Synaptics TDDI (Touch/Display Integration) panels utilize a single chip
> for display and touch controllers. Implement a simple device driver for
> such panels, along with its built-in LED backlight controller, and add
> suppor
On Friday, August 1st, 2025 at 00:12, Nícolas "F. R. A. Prado"
wrote:
> This function implies it only cleans up the colorops in the color
> pipeline of a specific plane, but it actually cleans up all colorops in
> the drm_mode_config of a device.
Good catch! Would make more sense to take a drm_
Here what I have from bisecting, please let me know if it makes things
clearer or not.
git bisect log
git bisect start
# status: waiting for both good and bad commits
# good: [6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1] Linux 6.7.11
git bisect good 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1
# status:
Hi Brigham,
thanks for the fixes. Will pick them up. Hope you don't mind if I
change the subject of the first patch to something a bit more
specific, such as:
accel/rocket: Adapt to changes in drm/sched API
Regards,
Tomeu
On Sat, Aug 2, 2025 at 9:25 PM Brigham Campbell
wrote:
>
> Fix two bui
On Sun Aug 3, 2025 at 9:33 AM MDT, Tomeu Vizoso wrote:
> thanks for the fixes. Will pick them up. Hope you don't mind if I
> change the subject of the first patch to something a bit more
> specific, such as:
>
> accel/rocket: Adapt to changes in drm/sched API
No, I don't mind at all. Go ahead and
On Thu, 31 Jul 2025 17:51:14 +0200, Otto Pflüger wrote:
> Add new compatible strings for the DPU and DSI controller found in the
> UMS9230 SoC.
>
> Signed-off-by: Otto Pflüger
> ---
> .../devicetree/bindings/display/sprd/sprd,sharkl3-dpu.yaml | 7
> ++-
> .../devicetree/bindings/d
On Sat, Aug 02, 2025 at 06:13:05PM +0200, Sukrut Heroorkar wrote:
> drm: drm_bridge: fix missing parameter documentation
>
> The function documentation was missing description for the
> parameter 'connector'.
>
> Add missing function parameter documentation for drm_bridge_detect()
> to fix kernel
On Thu, 31 Jul 2025 17:51:15 +0200, Otto Pflüger wrote:
> Introduce new clock names that actually describe what the clock input is
> used for instead of referring to a specific clock source.
>
> The new clock input names are based on information from clock drivers
> such as drivers/clk/sprd/ums5
On 8/1/25 05:36, Mario Limonciello wrote:
On 7/31/2025 10:05 PM, Lizhi Hou wrote:
The suspend and resume callbacks for pm and runtime pm should be same.
During suspending, it needs to stop all hardware contexts first. And
the hardware contexts will be restarted after the device is resumed.
Si
On 8/1/25 07:48, Falkowski, Maciej wrote:
On 7/31/2025 6:35 PM, Lizhi Hou wrote:
The suspend and resume callbacks for pm and runtime pm should be same.
During suspending, it needs to stop all hardware contexts first. And
the hardware contexts will be restarted after the device is resumed.
Si
The suspend and resume callbacks for pm and runtime pm should be same.
During suspending, it needs to stop all hardware contexts first. And
the hardware contexts will be restarted after the device is resumed.
Signed-off-by: Lizhi Hou
---
drivers/accel/amdxdna/aie2_ctx.c| 59 ++---
On Thu, Jul 03, 2025 at 05:28:19PM +0800, Haoxiang Li wrote:
> Add check for the return value of kstrdup_const() in drm_managed.c
> to prevent potential null pointer dereference.
>
> Fixes: c6603c740e0e ("drm: add managed resources tied to drm_device")
> Cc: sta...@vger.kernel.org
> Signed-off-by:
On Fri, Aug 01, 2025 at 01:57:49PM -0300, Jason Gunthorpe wrote:
> On Fri, Aug 01, 2025 at 06:50:18PM +0200, David Hildenbrand wrote:
> > On 01.08.25 18:40, Jason Gunthorpe wrote:
> > > On Fri, Jul 25, 2025 at 10:31:25AM +1000, Alistair Popple wrote:
> > >
> > > > The only issue would be if there
Add dt-binding documentation for waveshare DPI panel
Signed-off-by: Joseph Guo
Reviewed-by: Rob Herring (Arm)
---
Documentation/devicetree/bindings/display/panel/panel-simple.yaml | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/panel/panel-simpl
Waveshare touchscreen consists of a DPI panel and a driver board.
The waveshare driver board consists of ICN6211 and a MCU to
convert DSI to DPI and control the backlight.
This driver treats the MCU and ICN6211 board as a whole unit.
It can support all resolution waveshare DSI2DPI based panel,
the
This patchset add support for waveshare DSI2DPI unit.
Signed-off-by: Joseph Guo
---
Changes in v2:
- /s/i2c0/i2c/ in patch 1
- Add Review tags
- Link to v1:
https://lore.kernel.org/r/20250716-waveshare-v1-0-81cb03fb2...@nxp.com
---
Joseph Guo (3):
dt-bindings: display: bridge: Add wavesha
Add dt-binding documentation for waveshare DSI2DPI unit
Signed-off-by: Joseph Guo
Reviewed-by: Rob Herring (Arm)
---
Change from v1 to v2
- /s/i2c0/i2c/
---
.../bindings/display/bridge/waveshare,dsi2dpi.yaml | 103 +
1 file changed, 103 insertions(+)
diff --git
a/Documenta
Add check for the return value of kstrdup_const() in drm_managed.c
to prevent potential null pointer dereference.
Fixes: c6603c740e0e ("drm: add managed resources tied to drm_device")
Cc: sta...@vger.kernel.org
Signed-off-by: Haoxiang Li
---
Changes in v2:
- Modify a fix error. Thanks, Dmitry!
--
Hello Liu,
thanks for having reviewed this series.
On Mon, 4 Aug 2025 12:02:48 +0800
Liu Ying wrote:
> Hi Luca,
>
> On 08/01/2025, Luca Ceresoli wrote:
> > Note: the cover in v1 was mentioning by mistake
> > drm_bridge_get_last_bridge() instead of drm_bridge_get_next_bridge().
> >
On 08/01/2025, Luca Ceresoli wrote:
> Use drm_bridge_chain_get_last_bridge() instead of open coding a loop with
> two invocations of drm_bridge_get_next_bridge() per iteration.
>
> Besides being cleaner and more efficient, this change is necessary in
> preparation for drm_bridge_get_next_bridge()
Hello John,
On 8/2/2025 12:51 AM, John Stultz wrote:
> The __clear_task_blocked_on() helper added a number of sanity
> checks ensuring we hold the mutex wait lock and that the task
> we are clearing blocked_on pointer (if set) matches the mutex.
>
> However, there is an edge case in the _ww_mutex
On 2025/8/4 12:49, Dmitry Baryshkov wrote:
WARNING: This email originated from outside of Qualcomm. Please be wary of any
links or attachments, and do not enable macros.
On Mon, Aug 04, 2025 at 12:00:39PM +0800, Yongxing Mou wrote:
On 2025/7/31 4:31, Rob Herring (Arm) wrote:
WARNING: Thi
On Fri, Aug 01, 2025 at 12:31:00PM +0200, Michal Wilczynski wrote:
>
> v10:
> - Squashed the two dt-binding patches back into a single commit.
> - Simplified the B-series GPU rule by removing the not clause.
> - Reverted the removal of the items definition from the top-level
>power-domain-n
On 2025/8/4 12:52, Dmitry Baryshkov wrote:
On Mon, Aug 04, 2025 at 12:31:31PM +0800, Yongxing Mou wrote:
On 2025/8/2 17:56, Dmitry Baryshkov wrote:
On Wed, Jul 30, 2025 at 05:42:28PM +0800, Yongxing Mou wrote:
Document the MDSS hardware found on the Qualcomm QCS8300 platform.
Signed-off-
On 2025/7/31 4:31, Rob Herring (Arm) wrote:
WARNING: This email originated from outside of Qualcomm. Please be wary of any
links or attachments, and do not enable macros.
On Wed, 30 Jul 2025 17:42:28 +0800, Yongxing Mou wrote:
Document the MDSS hardware found on the Qualcomm QCS8300 platfor
Hi Luca,
On 08/01/2025, Luca Ceresoli wrote:
> Note: the cover in v1 was mentioning by mistake
> drm_bridge_get_last_bridge() instead of drm_bridge_get_next_bridge().
>
>
> This series adds drm_bridge_get/put() calls for DRM bridges returned by
> drm_bridge_get_next_bridge().
On Mon, Aug 04, 2025 at 12:00:39PM +0800, Yongxing Mou wrote:
>
>
> On 2025/7/31 4:31, Rob Herring (Arm) wrote:
> > WARNING: This email originated from outside of Qualcomm. Please be wary of
> > any links or attachments, and do not enable macros.
> >
> > On Wed, 30 Jul 2025 17:42:28 +0800, Yong
On Mon, Aug 04, 2025 at 12:31:31PM +0800, Yongxing Mou wrote:
>
>
> On 2025/8/2 17:56, Dmitry Baryshkov wrote:
> > On Wed, Jul 30, 2025 at 05:42:28PM +0800, Yongxing Mou wrote:
> > > Document the MDSS hardware found on the Qualcomm QCS8300 platform.
> > >
> > > Signed-off-by: Yongxing Mou
> > >
On 2025/8/2 17:56, Dmitry Baryshkov wrote:
On Wed, Jul 30, 2025 at 05:42:28PM +0800, Yongxing Mou wrote:
Document the MDSS hardware found on the Qualcomm QCS8300 platform.
Signed-off-by: Yongxing Mou
---
.../bindings/display/msm/qcom,qcs8300-mdss.yaml| 284 +
1 fi
On Mon, Aug 04, 2025 at 10:20:21AM +0800, Haoxiang Li wrote:
> Add check for the return value of kstrdup_const() in drm_managed.c
> to prevent potential null pointer dereference.
>
> Fixes: c6603c740e0e ("drm: add managed resources tied to drm_device")
> Cc: sta...@vger.kernel.org
> Signed-off-by:
37 matches
Mail list logo
