With the introduction of the HDMI Connector framework the driver might
end up creating the max_bpc property with min = max = 8. IGT insists
that such properties carry the 'immutable' flag. Automatically set the
flag if the driver asks for the max_bpc property with min == max.
Fixes: aadb3e16b8f3 (
drm_bridge_connector is a "leaf" driver, belonging to the display
helper, rather than the "CRTC" drm_kms_helper module. Move the driver
to the drm/display and add necessary Kconfig selection clauses.
Suggested-by: Maxime Ripard
Signed-off-by: Dmitry Baryshkov
---
MAINTAINERS
On HDMI connectors which use drm_bridge_connector and DRM_BRIDGE_OP_HDMI
IGT chokes on the max_bpc property in several kms_properties tests due
to the drm_bridge_connector failing to reset HDMI-related
properties.
Call __drm_atomic_helper_connector_hdmi_reset() if the
drm_bridge_connector has brid
Document that DRM_MODE_PROP_IMMUTABLE must be set for the properties
that are immutable by definition - e.g. ranges with min == max or enums
with a single value. This matches the behaviour of the IGT tests, see
kms_properties.c / validate_range_prop(), validate_enum_prop(),
validate_bitmask_prop().
Kconfig symbols should not declare dependency on DRM_DISPLAY_HELPER.
Move all parts of DRM_DISPLAY_HELPER to an if DRM_DISPLAY_HELPER block.
It is not possible to make those symbols select DRM_DISPLAY_HELPER
because of the link issues when a part of the helper is selected to be
built-in, while oth
Running IGT tests on Qualcomm Dragonboard820c uncovered two issues with
the HDMI Connector implementation and with its integration into the
drm_bridge_connector. Fix those issues.
Note, I'm not fully satisfied with the drm_bridge_connector move. Maybe
it's better to add drm_bridge_funcs::connector
Thanks Maíra, both patches are:
Reviewed-by: Iago Toral Quiroga
El dom, 14-07-2024 a las 11:49 -0300, Maíra Canal escribió:
> `args->cfg[4]` is configured in Indirect Dispatch using the number of
> batches. Currently, for all V3D tech versions, `args->cfg[4]` equals
> the
> number of batches subt
On 15-07-2024 04:42, Stephen Rothwell wrote:
Hi all,
On Wed, 12 Jun 2024 14:11:10 +1000 Stephen Rothwell
wrote:
After merging the drm-intel tree, today's linux-next build (htmldocs)
produced this warning:
include/drm/display/drm_dp_helper.h:127: warning: Function parameter or struct
membe
On Fri, 12 Jul 2024 at 14:46, Dave Airlie wrote:
>
> Hi Linus,
>
> Back to work, thanks to Sima for last week, not too many fixes as
> expected getting close to release, amdgpu and xe have a couple each,
> and then some other misc ones.
Oh I screwed up last week's fixes pull, and forgot to send t
The current driver can only obtain the porch parameters
of boe-th101mb31ig002. Modify it to obtain the porch
parameters of the panel currently being used.
Fixes: 24179ff9a2e4524 ("drm/panel: boe-th101mb31ig002 : Make it compatible
with other panel.")
Signed-off-by: Zhaoxiong Lv
---
drivers/gpu
The current driver can only obtain the porch parameters
of boe-th101mb31ig002. Modify it to obtain the porch
parameters of the panel currently being used.
Zhaoxiong Lv (1):
drm/panel: boe-th101mb31ig002 : Fix the way to get porch parameters
drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c
Hi all,
On Wed, 12 Jun 2024 14:11:10 +1000 Stephen Rothwell
wrote:
>
> After merging the drm-intel tree, today's linux-next build (htmldocs)
> produced this warning:
>
> include/drm/display/drm_dp_helper.h:127: warning: Function parameter or
> struct member 'target_rr_divider' not described i
Hi all,
On Fri, 31 May 2024 15:26:36 +1000 Stephen Rothwell
wrote:
>
> After merging the amdgpu tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:586: warning: Function
> parameter or struct member 'bb_from_dmub' not descri
Hi all,
On Tue, 14 May 2024 17:11:53 +1000 Stephen Rothwell
wrote:
>
> After merging the amdgpu tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:580: warning: Function parameter
> or struct member 'program_3dlut_size' not descr
Hi all,
On Wed, 1 May 2024 15:19:29 +1000 Stephen Rothwell
wrote:
>
> After merging the amdgpu tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:581: warning: Function
> parameter or struct member 'idle_workqueue' not descr
Hi all,
On Mon, 22 Apr 2024 09:56:42 +1000 Stephen Rothwell
wrote:
>
> On Tue, 30 Jan 2024 13:56:26 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the amdgpu tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > drivers/gpu/drm/amd/display/dc/link/hwss/link_hwss
Hi all,
On Mon, 22 Apr 2024 09:54:48 +1000 Stephen Rothwell
wrote:
>
> On Tue, 30 Jan 2024 13:54:21 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the amdgpu tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > drivers/gpu/drm/amd/display/dc/inc/hw/opp.h:1: warn
Define DRM native context capset in the VirtIO-GPU protocol header.
Signed-off-by: Dmitry Osipenko
---
include/uapi/linux/virtio_gpu.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/virtio_gpu.h b/include/uapi/linux/virtio_gpu.h
index 0e21f3998108..bf2c9cabd207 100644
---
Type of DMA fence context is u64. Fence-waiting code uses u32 for the
context variable, fix it.
Fixes: e4812ab8e6b1 ("drm/virtio: Refactor and optimize job submission code
path")
Cc: # v6.4+
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/virtio/virtgpu_submit.c | 2 +-
1 file changed, 1 in
Hi
Am 12.07.24 um 18:16 schrieb José Expósito:
Building with Sparse enabled prints this warning for cpu_to_le16()
calls:
warning: incorrect type in assignment (different base types)
expected unsigned short [usertype]
got restricted __le16 [usertype]
And this warning for
On 7/14/24 3:37 AM, Dan Carpenter wrote:
[...]
+err_irq_nfb4eof:
+ ipu_idmac_put(priv->vdi_out_ch);
+err_out:
+ ipu_idmac_put(priv->vdi_in_ch_n);
+err_next:
+ ipu_idmac_put(priv->vdi_in_ch);
+err_curr:
+ ipu_idmac_put(priv->vdi_in_ch_p);
+err_prev:
+ ipu_ic_put(pri
Cristian,
I'm hacking with adding cec support for rk3588 hdmi on 6.10-rc7 mainline.
Cec kernel module is my backport from bsp.
Module loads. Cec line (observed on osciloscope) has pulses when i'm issuing
i.e. cec-ctl -d /dev/cec0 --phys-addr=1.0.0.0 —playback
My issue is that timings are 2,9
On Wed, Jul 10, 2024 at 2:23 PM Helen Koike wrote:
>
>
>
> On 02/07/2024 18:57, Jim Cromie wrote:
> > Several tests are dependent upon config choices. Lets avoid failing
> > where that is noise.
> >
...
> >
> > test_mod_submod() recaps the bug found in DRM-CI where drivers werent
>
> If this fixes
The V3D tech revision can be a useful information when configuring
jobs. Therefore, expose it in the `struct v3d_dev` with the V3D tech
version.
Signed-off-by: Maíra Canal
---
drivers/gpu/drm/v3d/v3d_drv.c | 5 -
drivers/gpu/drm/v3d/v3d_drv.h | 8 +---
2 files changed, 9 insertions(+), 4
`args->cfg[4]` is configured in Indirect Dispatch using the number of
batches. Currently, for all V3D tech versions, `args->cfg[4]` equals the
number of batches subtracted by 1. But, for V3D 7.1.6 and later, we must not
subtract 1 from the number of batches.
Implement the fix by checking the V3D t
On 04.07.2024 11:48, Manikandan Muralidharan wrote:
> Add the Microchip's DSI controller wrapper driver that uses
> the Synopsys DesignWare MIPI DSI host controller bridge.
>
> Signed-off-by: Manikandan Muralidharan
> ---
> drivers/gpu/drm/bridge/Kconfig| 8 +
> drivers/gpu/drm/
On 7/12/24 16:08, Jason Gunthorpe wrote:
> [You don't often get email from j...@ziepe.ca. Learn why this is important at
> https://aka.ms/LearnAboutSenderIdentification ]
>
> On Fri, Jun 28, 2024 at 10:24:32AM +, Omer Shpigelman wrote:
>
>> We need the core driver to access the IB driver (an
'struct exynos_drm_ipp_funcs' are not modified in these drivers.
Constifying this structure moves some data to a read-only section, so
increase overall security.
On a x86_64, with allmodconfig, as an example:
Before:
==
textdata bss dec hex filename
204461746 16
28 matches
Mail list logo
