Probe deferral can cause the platform-data we access to be freed already
causing ugly splats on system shutdown.
Fix this via a small component-helper and adapting the rockchip-drm
shutdown handler.
Heiko Stuebner (2):
drivers: base: component: add function to query the bound status
drm/rockc
This patch removes mipi_dsi_dcs_set_tear_off and replaces it with a
multi version as after replacing it in sony-td4353-jdi, it doesn't
appear anywhere else. sony-td4353-jdi is converted to use multi style
functions, including mipi_dsi_dcs_set_tear_off_multi.
Tejas Vipin (2):
drm/mipi-dsi: Replac
On Thu, 23 Jan 2025, Simona Vetter wrote:
> On Wed, Jan 22, 2025 at 04:41:32PM +0200, Jani Nikula wrote:
>> Add CONFIG_DRM_HEADER_TEST to ensure drm headers are self-contained and
>> pass kernel-doc. And for starters, fix one header that this catches.
>>
>> Jani Nikula (2):
>> drm/client: inclu
On 02/11/2025, Alexander Stein wrote:
> Hi,
Hi Alexander,
>
> i.MX91/93 support a parallel display interface. There is a single register
> for configuring the output format. There is not much documentation, but
> apparently this does some internal conversion.
> Add a bridge driver (similar to fs
Hi,
i.MX91/93 support a parallel display interface. There is a single register
for configuring the output format. There is not much documentation, but
apparently this does some internal conversion.
Add a bridge driver (similar to fsl-ldb.c) for connecting a bridge/panel
to lcdif.
I'm a bit unsure
The mdp1-mem is not supported on the SM8550 & SM8650 SoCs, so only support a
single
mdp0-mem interconnect entry.
This fixes the following errors:
display-subsystem@ae0: interconnects: [[200, 3, 7, 32, 1, 7]] is too short
from schema $id:
http://devicetree.org/schemas/display/msm/qcom
Fix a mutex bug and convert most of the explicit mutex_(un)locks to
guards.
Bart Van Assche (1):
drm: zynqmp_dp: Fix a deadlock in zynqmp_dp_ignore_hpd_set()
Sean Anderson (1):
drm: zynqmp_dp: Use scope-based mutex helpers
drivers/gpu/drm/xlnx/zynqmp_dp.c | 151
A lot of DisplayPort bridges use HDMI Codec in order to provide audio
support. Present DRM HDMI Audio support has been written with the HDMI
and in particular DRM HDMI Connector framework support, however those
audio helpers can be easily reused for DisplayPort drivers too.
Patches by Hermes Wu th
From: Rafael Beims
This patch series adds HDMI audio support to the Lontium LT8912B bridge driver
using the I2S input. The audio output was tested using a Verdin iMX8MM + DSI to
HDMI adapter connected to different monitors.
Rafael Beims (2):
dt-bindings: display: bridge: lt8912b: Add I2S aud
This is a Generic MIPI-DSI / DPI(+SPI) dual stack panel driver.
Although the MIPI specifications define how to communicate with a panel
to display an image, some panels still require a panel-specific
initialization sequence to be sent.
While there are many dedicated drivers for such panels, they
On Wed, Jan 22, 2025 at 04:41:32PM +0200, Jani Nikula wrote:
> Add CONFIG_DRM_HEADER_TEST to ensure drm headers are self-contained and
> pass kernel-doc. And for starters, fix one header that this catches.
>
> Jani Nikula (2):
> drm/client: include types.h to make drm_client_event.h self-contain
Add CONFIG_DRM_HEADER_TEST to ensure drm headers are self-contained and
pass kernel-doc. And for starters, fix one header that this catches.
Jani Nikula (2):
drm/client: include types.h to make drm_client_event.h self-contained
drm: ensure drm headers are self-contained and pass kernel-doc
K
Two patches extracted from my deadline scheduler RFC. I think they are making
the entity selection logic a bit easier on the eyes but as opinions may vary
please have a look and see what you think.
Cc: Christian König
Cc: Danilo Krummrich
Cc: Matthew Brost
Cc: Philipp Stanner
Tvrtko Ursulin (
Retimers in H/w usually takes 30 to 40ms to wake up all the devices. To
get this we use the Extended Wake Time feature in which the sink device
tells us the minimum amount of time it requires to wake up and we need
to do a write to grant this request else we need to wake up within 1ms
of low power
vmwgfx had a number of cursor issues that related both to our handling
of dumb buffers and general detection when a cursor has actually changed.
Fix those issues and bump the kernel module version to allow userspace
to recognize fixed versions of the driver.
Zack Rusin (2):
drm/vmwgfx: Refactor
This series adds DT-bindings and panel-simple implementation for the
DataImage FG080016DNCWAG03 8" 640x480 TFT LCD panel.
The timings are sourced from the FG080016DNCWAGL1 datasheet but
available for testing was only the DataImage FG080016DNCWAG03, for which
I can confirm these values work.
Signe
Patch 1 reverts a previous fix for loss of HDMI sync when playing YUV420
@ 59.94 media. The patch does resolve a calculation issue. It also makes
all fractional rates invalid which is a bigger problem.
Patch 2 provides a proper fix after I figured out the actual root cause
of the original problem.
This series adds the following fixes related to the virtual planes code
changes:
1) Initialize the return value of dpu_assign_plane_resources() so that
the function doesn't return a garbage value if all planes are
disabled/otherwise not visible.
2) Remove extraneous return value for dpu_crtc
With this user can hint low latency during exec queue creation.
KMD will forward hint to guc.
Note : There is some issue going on with GUC, that setting hint is not
correctly fixing high frequency. The work to fix that in GUC is
being done parallely so sending RFC to get KMD reviews going.
Tejas
Hi,
this fixes two dtbs_check warnings by moving the video muxing node out of gpr
and adding a new imx7 specific DSI compatible to DT schema.
Best regards,
Alexander
Alexander Stein (2):
ARM: dts: imx7s: Move csi-mux to below root
dt-bindings: samsung,mipi-dsim: Add imx7d specific compatible
Hi,
On 31/12/2024 11:04, Devarsh Thakkar wrote:
This adds support for DSS subsystem present in TI's AM62L SoC
which supports single display pipeline with DPI output which
is also routed to DSI Tx controller within the SoC.
Devarsh Thakkar (2):
dt-bindings: display: ti,am65x-dss: Add support
On 12/20/2024 4:06 AM, Konrad Dybcio wrote:
> Might come in useful to try and track down otherwise inexplicable
> failures in e.g. old CI logs. A630 uses a different mechanism that is
> not implemented in this series.
>
> Tested on 8280 and X1
>
> Signed-off-by: Konrad Dybcio
For the whole seri
This adds support for DSS subsystem present in TI's AM62L SoC
which supports single display pipeline with DPI output which
is also routed to DSI Tx controller within the SoC.
Devarsh Thakkar (2):
dt-bindings: display: ti,am65x-dss: Add support for AM62L DSS
drm/tidss: Add support for AM62L dis
Might come in useful to try and track down otherwise inexplicable
failures in e.g. old CI logs. A630 uses a different mechanism that is
not implemented in this series.
Tested on 8280 and X1
Signed-off-by: Konrad Dybcio
---
Konrad Dybcio (2):
drm/msm: registers: Add GMU FW version register
TDA998x is the HDMI bridge driver, incorporating drm_connector and
optional drm_encoder (created via the component bind API by the TICLDC
and HDLCD drivers). TDA9950 is an I2C-CEC translator, being present
on-die on the TDA9989 and TDA19989 chips.
Move both drivers to live next to all DRM bridge d
The nouveau driver is the only user of the drm_encoder_slave interface.
Demote it from KMS helpers module to the nouveau driver itself, moving
corresponding I2C encoders to be handled by nouveau driver too.
Ideally those two drivers should be converted to the drm_bridge
interface, but it's unclear
Hi,
On Fri, 25 Oct 2024 15:34:06 +0800, Zhang Zekun wrote:
> drm_mode_duplicate() could return NULL due to lack of memory, which
> could cause NULL pointer dereference. Add a check to prevent it.
>
> Zhang Zekun (2):
> drm/i2c/ch7006: Add a check to prevent NULL pointer dereference
> drm/pane
Retimers in H/w usually takes 30 to 40ms to wake up all the devices. To
get this we use the Extended Wake Time feature in which the sink device
tells us the minimum amount of time it requires to wake up and we need
to do a write to grant this request else we need to wake up within 1ms
of low power
This patch series updates the compatible strings for the MediaTek OVL
in the MT8188 dts and the corresponding dt-binding.
The changes ensure that the MT8188 OVL device is correctly identified
and managed by the appropriate drivers.
The first patch is resending the reviewed and acked patch from:
-
This small series adds DT bindings and panel-simple implementation for the
Tianma TM070JDHG34-00 7" panel. Due to how the datasheet computes the
blanking time, a quirk is needed in the timing implementation. A comment
documents that in patch 2.
Signed-off-by: Luca Ceresoli
---
Luca Ceresoli (2):
From: Alexander Sverdlin
Add new DT compatible ti,lp8864 to support all four software-compatible
devices:
- LP8864
- LP8864S
- LP8866
- LP8866S
This is a new family with a functionality similar to LP8860 -- hence the
same (re-used) DT bindings. They had to be converted to YAML along the way.
Add
[Resending due to temporary mailing list server error on
gabe.freedesktop.org - trying again to reach dri-devel and amd-gfx]
Hi,
This is another attempt to approach page fault error faced by Cosmic
users of AMD display hw that exposes two overlay planes. It was first
reported as an interface fre
From: Ville Syrjälä
Fix a potential div-by-zero in drm_mode_vrefresh()
TODO: should probably make drm_mode_setcrtc() not even print the
(potentially partially) converted mode, and instead print
the original umode..
Test-with: 20241128190927.26033-1-ville.syrj...@linux.intel.com
Vil
reset control is included in platforms from Allwinner, specifically
A133, A733. Add reset control from devicetree and these changes are
tested with A133 based helper board, which will be upstremed after
Allwinner power domain controller.
Firmware is used from [1].
[1]: https://gitlab.freedesktop.
On Thu, Nov 21, 2024 at 09:25:11AM +0100, Thomas Zimmermann wrote:
> ping ping
> >drm/cirrus: Use virtual encoder and connector types
> >drm/cirrus: Rename to cirrus-qemu
Hmm, matter of taste. I would not have invested that effort, but I have
no objections either. So:
Acked-by: Gerd Ho
ping ping
Am 29.10.24 um 15:34 schrieb Thomas Zimmermann:
The cirrus driver is only for qemu's emulation of that hardware. The
two patches in this series update cirrus to reflect this.
(The driver is still obsolete. Use something else if possible.)
Thomas Zimmermann (2):
drm/cirrus: Use vi
Bhavin Sharma (2):
drm: amd: display: Remove redundant check
drm: amd: pm: Remove redundant check
.../display/dc/dml/dml1_display_rq_dlg_calc.c | 2 +-
drivers/gpu/drm/amd/display/dc/dsc/dc_dsc.c | 13 --
.../amd/pm/powerplay/smumgr/vega12_smumgr.c | 24 +--
3 fil
Hi,
Gentle ping.
The patch link is: [PATCH 0/2] drm/amd/display: Fix Null Pointer
Dereference Issues - Zicheng Qu (kernel.org)
<https://lore.kernel.org/linux-kernel/20241105140137.2465572-1-quzich...@huawei.com/>
Best regards,
Zicheng
On 2024/11/5 22:01, Zicheng Qu wrote:
Hi all,
Hi,
On Fri, Nov 8, 2024 at 12:31 AM Daniel Thompson
wrote:
>
> Going forward, I'll be using my kernel.org address for upstream work.
>
> Signed-off-by: Daniel Thompson
> ---
> Daniel Thompson (2):
> MAINTAINERS: Use Daniel Thompson's korg address for backlight work
> MAINTAINERS: Use
This is a small series that makes the deferred dphy no longer emit error
messages to the kernel log, which may even be repeated multiple times, to
avoid possible false impression of some issues.
This series also performs a few small, rather trivial code cleanups, to
make the code a bit easier to r
Going forward, I'll be using my kernel.org address for upstream work.
Signed-off-by: Daniel Thompson
---
Daniel Thompson (2):
MAINTAINERS: Use Daniel Thompson's korg address for backlight work
MAINTAINERS: Use Daniel Thompson's korg address for kgdb work
MAINTAINERS | 4 ++--
1 file
ping
Am 29.10.24 um 15:34 schrieb Thomas Zimmermann:
The cirrus driver is only for qemu's emulation of that hardware. The
two patches in this series update cirrus to reflect this.
(The driver is still obsolete. Use something else if possible.)
Thomas Zimmermann (2):
drm/cirrus: Use virtual
Hi all,
I am submitting two patches to fix null pointer dereference issues in
the AMD display driver.
1. Patch 1/2 (Fixes: 8e4ed3cf1642): Add null checks in
dcn20_program_pipe() to prevent potential crashes when accessing
plane_state.
2. Patch 2/2 (Fixes: 0baae6246307): Ensures pipe_ctx->plane_s
Hi all,
I am submitting two patches to correct power gating configurations in
the AMD display driver.
1. Patch 1/2 (Fixes: 46825fcfbe16): Corrects DOMAIN10_PG_CONFIG to use
DOMAIN10_POWER_FORCEON.
2. Patch 2/2 (Fixes: 46825fcfbe16): Corrects DOMAIN11_PG_CONFIG to use
DOMAIN11_POWER_FORCEON.
Than
On 11/5/24 7:02 AM, Zicheng Qu wrote:
Hi all,
I am submitting two patches to correct power gating configurations in
the AMD display driver.
1. Patch 1/2 (Fixes: 46825fcfbe16): Corrects DOMAIN10_PG_CONFIG to use
DOMAIN10_POWER_FORCEON.
2. Patch 2/2 (Fixes: 46825fcfbe16): Corrects DOMAIN11_PG_
This patch series aims to fix 2 bugs in ADV7535 driver
1) use-after-free bug in adv7533_attach_dsi()
2) out-of-bounds array in adv7511_dsi_config_timing_gen() for
clock_div_by_lanes[].
Biju Das (2):
drm: adv7511: Fix use-after-free in adv7533_attach_dsi()
drm: adv7511: Fix out-of-bounds arr
Hi, Javier:
Javier Carrasco 於 2024年10月12日 週六 上午3:22寫道：
>
> This series fixes a wrong handling of the child node within the
> for_each_child_of_node() by adding the missing call to of_node_put() to
> make it compatible with stable kernels that don't provide the scoped
> variant of the macro, which
The cirrus driver is only for qemu's emulation of that hardware. The
two patches in this series update cirrus to reflect this.
(The driver is still obsolete. Use something else if possible.)
Thomas Zimmermann (2):
drm/cirrus: Use virtual encoder and connector types
drm/cirrus: Rename to cirru
On Fri, 25 Oct 2024, Ville Syrjälä wrote:
> On Wed, Oct 02, 2024 at 09:21:58PM +0300, Ville Syrjala wrote:
>> From: Ville Syrjälä
>>
>> An attempt to hide the drm_plane/crtc legacy state better.
>>
>> This also highlights the fact that a lot of supposedly
>> atomic drivers are poking around in
On Fri, 25 Oct 2024 at 10:46, Ville Syrjälä
wrote:
>
> On Wed, Oct 02, 2024 at 09:21:58PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > An attempt to hide the drm_plane/crtc legacy state better.
> >
> > This also highlights the fact that a lot of supposedly
> > atomic drivers are po
drm_mode_duplicate() could return NULL due to lack of memory, which
could cause NULL pointer dereference. Add a check to prevent it.
Zhang Zekun (2):
drm/i2c/ch7006: Add a check to prevent NULL pointer dereference
drm/panel: himax-hx83102: Add a check to prevent NULL pointer
dereference
On Wed, Oct 02, 2024 at 09:21:58PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> An attempt to hide the drm_plane/crtc legacy state better.
>
> This also highlights the fact that a lot of supposedly
> atomic drivers are poking around in the legacy crtc state,
> which is rather questionab
Hi,
Usually the TI SN65DSI83 recovers from error by itself but during ESD
tests, we have some cases where the TI SN65DSI83 didn't recover.
In order to handle those cases, this series adds support for a recovery
mechanism.
Best regards,
Hervé Codina
Herve Codina (2):
dt-bindings: display: brid
This series brings two small improvements to the DRM documentation and
logging.
Signed-off-by: Luca Ceresoli
---
Luca Ceresoli (2):
drm/drm_mode_object: fix typo in kerneldoc
drm/atomic-helper: improve CRTC enabled/connectors mismatch logging
message
drivers/gpu/drm/drm_atomic_help
Hi,
On Mon, 14 Oct 2024 00:24:00 +0300, Danila Tikhonov wrote:
> This patch series adds support for the Samsung AMS581VF01 panel, used in
> the Google Pixel 4a (sm7150-google-sunfish). Unlike many other devices,
> which may use different panels in various revisions, the Pixel 4a has only
> one pos
After unplugging a display from the connector, the driver has to clear
the connector's EDID property. Recent code for BMC support forget to do
this for VGA- and SIL164-based transmitters. Fix it.
Thomas Zimmermann (2):
drm/ast: sil164: Clear EDID if no display is connected
drm/ast: vga: Clear
This patch series adds support for the Samsung AMS581VF01 panel, used in
the Google Pixel 4a (sm7150-google-sunfish). Unlike many other devices,
which may use different panels in various revisions, the Pixel 4a has only
one possible panel option. Also this panel is not used in other devices.
Testin
While reviewing the interrupt related code and register dump, we found couple
of issues related to interrupt related register programming. Firstly, the
function enabling/disabling the interrupts was trying to clear the
interrupts which were not enabled in first place and secondly there is a
potenti
This series fixes a wrong handling of the child node within the
for_each_child_of_node() by adding the missing call to of_node_put() to
make it compatible with stable kernels that don't provide the scoped
variant of the macro, which is more secure and was introduced early this
year.
Signed-off-by:
Applied to drm-misc-next
On 10/4/2024 6:25 PM, Maciej Falkowski wrote:
> This patchset adds initial support for 5th generation Intel NPU
> that is going to be present in the upcoming Panther Lake CPUs.
>
> Maciej Falkowski (1):
> accel/ivpu: Add initial Panther Lake support
>
> Wachowski, Karo
Hi,
On Wed, 26 Jun 2024 16:40:37 +0200, Philipp Zabel wrote:
> The Ilitek IL9881C controller can rotate the image by 180°. This
> might be desirable on devices with their display mounted upside down,
> that don't have rotation capability in the SoC display controller.
>
>
Thanks, Applied to htt
On 26/06/2024 16:40, Philipp Zabel wrote:
The Ilitek IL9881C controller can rotate the image by 180°. This
might be desirable on devices with their display mounted upside down,
that don't have rotation capability in the SoC display controller.
Signed-off-by: Philipp Zabel
---
Philipp Zabel (2):
If DSC is enabled, the only case is with 2 DSC engines so far. And
DSC in all pipes are configured by default.
More usage case will be added, such as 4 DSC in 4:4:2 topoplogy.
Pipe number is extended in future to support quad-pipe. But only
some of 4 pipes are used in non quad-pipe. So number of D
This patchset adds initial support for 5th generation Intel NPU
that is going to be present in the upcoming Panther Lake CPUs.
Maciej Falkowski (1):
accel/ivpu: Add initial Panther Lake support
Wachowski, Karol (1):
accel/ivpu: Update power island delays
drivers/accel/ivpu/ivpu_drv.c
On Wed, Oct 02, 2024 at 03:10:14PM GMT, Jani Nikula wrote:
> On Wed, 25 Sep 2024, Maxime Ripard wrote:
> > On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
> >> I think for at least drm the consensus is clear, we won't have kunit tests
> >> that splat.
> >
> > Where was that ever discu
Hi Marek
On Thu, 3 Oct 2024 at 10:29, Marek Szyprowski wrote:
>
> Dear All,
>
> Yesterday the "drm: Provide client setup helper and convert drivers"
> patchset [1] landed in linux-next. In my tests I found that it causes kernel
> NULL pointer dereference on ARM/ARM64 based Raspberry Pi4B boards.
Dear All,
Yesterday the "drm: Provide client setup helper and convert drivers"
patchset [1] landed in linux-next. In my tests I found that it causes kernel
NULL pointer dereference on ARM/ARM64 based Raspberry Pi4B boards. It
turned out that the conversion of the VC4 DRM driver is a bit incomplete
This patch series lets DRM fdinfo stats functions display an additional tag
that will reflect the amount of memory internal BOs of a DRM driver take
up.
The rationale for this is that some drivers, like Panthor, need quite a bit
of memory for things like queue ring buffers or tiler heap chunks, an
From: Ville Syrjälä
An attempt to hide the drm_plane/crtc legacy state better.
This also highlights the fact that a lot of supposedly
atomic drivers are poking around in the legacy crtc state,
which is rather questionable. For planes we did force the
legacy state to NULL already to force drivers
I was trying dri-misc-next on Pi4 and getting a NULL deref as vc4
started. The cause was having missed adding DRM_FBDEV_DMA_DRIVER_OPS
to the 2711 struct drm_driver, but also showed up that the handling
in drm_fb_helper_single_fb_probe could fail to call any fbdev_probe
function, and hence the NULL
On Wed, 25 Sep 2024, Maxime Ripard wrote:
> On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
>> I think for at least drm the consensus is clear, we won't have kunit tests
>> that splat.
>
> Where was that ever discussed?
Well, where was it ever agreed that it's okay for drm kunit test
On Thu, 12 Sep 2024 22:43:57 +0800, Pin-yen Lin wrote:
> This series fixes two binding schema errors in mediatek,dpi binding.
> The first patch adds the power-domain property to the binding, and the
> second patch adds the port node as it's required by the binding.
>
>
> Pin-yen Lin (2):
> dt-b
On 2024-09-27 18:02, Dmitry Baryshkov wrote:
On Fri, 27 Sept 2024 at 17:39, wrote:
On 2024-08-01 21:25, Dmitry Baryshkov wrote:
> On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
>> This patch series add dpu support for MSM8996/MSM8953 devices.
>>
>> Note, by default these platfo
On Fri, 27 Sept 2024 at 17:39, wrote:
>
> On 2024-08-01 21:25, Dmitry Baryshkov wrote:
> > On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
> >> This patch series add dpu support for MSM8996/MSM8953 devices.
> >>
> >> Note, by default these platforms are still handled by the MDP5 dri
On 2024-08-01 21:25, Dmitry Baryshkov wrote:
On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
This patch series add dpu support for MSM8996/MSM8953 devices.
Note, by default these platforms are still handled by the MDP5 driver
unless the `msm.prefer_mdp5=false' parameter is provid
On Wed, Sep 25, 2024 at 09:04:39AM GMT, Guenter Roeck wrote:
> On 9/25/24 06:05, Maxime Ripard wrote:
> [ ... ]
>
> > > We've had similar discussions in the past around unit tests that wasted
> > > too much cpu time with randomized combinatorial testing, and we've thrown
> > > those out too from d
On Wed, 25 Sept 2024 at 23:28, wrote:
>
> On 2024-08-01 21:25, Dmitry Baryshkov wrote:
> > On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
> >> This patch series add dpu support for MSM8996/MSM8953 devices.
> >>
> >> Note, by default these platforms are still handled by the MDP5 dri
On 2024-08-01 21:25, Dmitry Baryshkov wrote:
On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
This patch series add dpu support for MSM8996/MSM8953 devices.
Note, by default these platforms are still handled by the MDP5 driver
unless the `msm.prefer_mdp5=false' parameter is provid
On 9/25/24 06:05, Maxime Ripard wrote:
[ ... ]
We've had similar discussions in the past around unit tests that wasted
too much cpu time with randomized combinatorial testing, and we've thrown
those out too from drm. Test hygiene matters.
We had that discussion because those tests could run fo
On 9/25/24 05:59, Maxime Ripard wrote:
...
All I'm saying it generates an extra burden for current real world CI
systems that run tests on a massive scale and even have paid
maintainers. It's not trivial to sort out expected and unexpected
warnings, and keep the filters updated every time the wa
Hi!
AFAIU, the driver is defining two different max number of surfaces:
MAX_SURFACES (dc.h) and MAX_SURFACE_NUM (dc_types.h) Many years ago,
MAX_SURFACES was set 3 just to prevent a stack size warning as in
091a97e542cf ("drm/amd/display: Fix warning. Set MAX_SURFACES to 3")[1].
But according to c
On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
> On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote:
> > On 9/24/24 06:56, Maxime Ripard wrote:
> > > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> > > > On 9/24/24 04:54, Maxime Ripard wrote:
> > > > > +Guent
On Wed, Sep 25, 2024 at 12:41:40PM GMT, Jani Nikula wrote:
> On Tue, 24 Sep 2024, Maxime Ripard wrote:
> > On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
> >> On Tue, 24 Sep 2024, Guenter Roeck wrote:
> >> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> >> > Ye
On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote:
> On 9/24/24 06:56, Maxime Ripard wrote:
> > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> > > On 9/24/24 04:54, Maxime Ripard wrote:
> > > > +Guenter
> > > >
> > > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vett
On Tue, 24 Sep 2024, Maxime Ripard wrote:
> On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
>> On Tue, 24 Sep 2024, Guenter Roeck wrote:
>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
>> > Yeah I think long-term we might want a kunit framework so that we can
>
On 9/24/24 09:57, Maxime Ripard wrote:
On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
Yeah I think long-term we might want a kunit framework so that we can
catch dmesg warnings w
On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
> On Tue, 24 Sep 2024, Guenter Roeck wrote:
> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> > Yeah I think long-term we might want a kunit framework so that we can
> > catch dmesg warnings we expect and test f
On 9/24/24 08:56, Jani Nikula wrote:
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
Yeah I think long-term we might want a kunit framework so that we can
catch dmesg warnings we expect and test for those, without those warnings
actually g
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> Yeah I think long-term we might want a kunit framework so that we can
> catch dmesg warnings we expect and test for those, without those warnings
> actually going to dmesg. Sim
On 9/24/24 06:56, Maxime Ripard wrote:
On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
On 9/24/24 04:54, Maxime Ripard wrote:
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
The tests consistently
On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> On 9/24/24 04:54, Maxime Ripard wrote:
> > +Guenter
> >
> > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> > > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> > > > The tests consistently trigger WARNs in
On 9/24/24 04:54, Maxime Ripard wrote:
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
The tests consistently trigger WARNs in drm_framebuffer code. I'm not
sure what the point is with type of belts and suspende
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> > The tests consistently trigger WARNs in drm_framebuffer code. I'm not
> > sure what the point is with type of belts and suspenders tests. The
> > warnings *are*
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> The tests consistently trigger WARNs in drm_framebuffer code. I'm not
> sure what the point is with type of belts and suspenders tests. The
> warnings *are* the way to flag erroneous API usage.
>
> Warnings in turn trigger failures in
This mainly fixes the use case when the user changes the external monitor
when the system is suspended. Without this series, both of the bridges
will skip the EDID read and returned the cached one after resume.
Apart from that, we also observed a DP-to-HDMI bridge expects an EDID read
after it's p
Il 17/09/24 19:34, Markus Elfring ha scritto:
From: Markus Elfring
Date: Tue, 17 Sep 2024 19:16:45 +0200
A few update suggestions were taken into account
from static source code analysis.
Hello Markus,
In my opinion, the suggested changes aren't bringing any improvement, not
in readability n
This patch series adds a new debugfs file named "sched_groups" allowing
a user to query information about all userspace clients scheduler groups.
This patch series assumes that [1] and [2] are applied.
[1]https://lore.kernel.org/all/20240903144955.144278-2-mary.guillem...@collabora.com/
[2]https:
The tests consistently trigger WARNs in drm_framebuffer code. I'm not
sure what the point is with type of belts and suspenders tests. The
warnings *are* the way to flag erroneous API usage.
Warnings in turn trigger failures in CI. Filtering the warnings are
error prone, and, crucially, would also
From: Markus Elfring
Date: Tue, 17 Sep 2024 19:16:45 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Avoid duplicate sg_free_table(sgt) call
Use common error handling code
drivers/gpu/drm/mediatek/mtk_gem.c | 14 --
1
This series fixes two binding schema errors in mediatek,dpi binding.
The first patch adds the power-domain property to the binding, and the
second patch adds the port node as it's required by the binding.
Pin-yen Lin (2):
dt-bindings: display: mediatek: dpi: Add power-domains to the bindings
1 - 100 of 1287 matches
Mail list logo
