Re: [PATCH 4/8] drm/client: Make copies of modes

2024-10-10 Thread Ville Syrjälä
On Tue, Oct 08, 2024 at 10:33:44PM +0300, Ville Syrjälä wrote: > On Mon, Oct 07, 2024 at 09:36:13AM +0200, Thomas Zimmermann wrote: > > Hi > > > > Am 03.10.24 um 13:33 schrieb Ville Syrjala: > > > From: Ville Syrjälä > > > > > > drm_client_firmware_config() is currently picking up the current > >

Re: [PATCH 4/8] drm/client: Make copies of modes

2024-10-09 Thread kernel test robot
dress#:#[##]PREEMPT_SMP_KASAN_PTI" on: commit: 2cc919cccbb5d887534545618d696db4ec5fb691 ("[PATCH 4/8] drm/client: Make copies of modes") url: https://github.com/intel-lab-lkp/linux/commits/Ville-Syrjala/drm-client-Constify-modes/20241004-061843 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-nex

Re: [PATCH 4/8] drm/client: Make copies of modes

2024-10-08 Thread Ville Syrjälä
On Mon, Oct 07, 2024 at 09:36:13AM +0200, Thomas Zimmermann wrote: > Hi > > Am 03.10.24 um 13:33 schrieb Ville Syrjala: > > From: Ville Syrjälä > > > > drm_client_firmware_config() is currently picking up the current > > mode of the crtc via the legacy crtc->mode, which is not supposed > > to be

Re: [PATCH 4/8] drm/client: Make copies of modes

2024-10-07 Thread Thomas Zimmermann
Hi Am 03.10.24 um 13:33 schrieb Ville Syrjala: From: Ville Syrjälä drm_client_firmware_config() is currently picking up the current mode of the crtc via the legacy crtc->mode, which is not supposed to be used by atomic drivers at all. We can't simply switch over to the proper crtc->state->mode

Re: [PATCH 4/8] drm/client: Make copies of modes

2024-10-03 Thread Ville Syrjälä
On Thu, Oct 03, 2024 at 02:33:00PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > drm_client_firmware_config() is currently picking up the current > mode of the crtc via the legacy crtc->mode, which is not supposed > to be used by atomic drivers at all. We can't simply switch over > to the

[PATCH 4/8] drm/client: Make copies of modes

2024-10-03 Thread Ville Syrjala
From: Ville Syrjälä drm_client_firmware_config() is currently picking up the current mode of the crtc via the legacy crtc->mode, which is not supposed to be used by atomic drivers at all. We can't simply switch over to the proper crtc->state->mode because we drop the crtc->mutex (which protects c