From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C79B0346A0B for ; Thu, 16 Jul 2026 08:19:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784189943; cv=none; b=CTdaXYvU3QGxEGLc+qD3Xz021o1oANbg4wniHxKSLghAsFj/JzJVdfNuKkWes9uje40s3jAcTuioRlNCH9HYVyuWoIseqkRJ68B5IYoV0MkNQn5+PfjPy3JJZBdzW9sRJxHjYHmOu3E/Jcr3GVT/Ta8MQBb7H9/KJsHiGwtEGZA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784189943; c=relaxed/simple; bh=CQcSJu7ir1ZxyU06FWPT4r5MnZcOUIDMyXGHVCWBTk0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=S7JOW9knXZ6lmHD7drv260WMh1yFvOuFbVNRX94Ink6sKb9tx8SDzf9z1Cevg8953+awIfF0sX4PHVe9fJwUc/fmUDM2ahATW2IX3qrwDDaZ/INlhJUzwITN150P5w0866ljHDX94nBBrtWrmuPyZwYmNlybTB8gFwSQuPBrqLc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=OfZ4ymHA; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="OfZ4ymHA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F10CA1F000E9; Thu, 16 Jul 2026 08:19:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784189942; bh=CQcSJu7ir1ZxyU06FWPT4r5MnZcOUIDMyXGHVCWBTk0=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=OfZ4ymHAWUb0RMyBLZH/IBDPQl0rkzOG8Fe1FsYTDnOoflWlpEF9Wt3igBepiqVcP qg1d66d4FFxj1YLKpP2ySujFBL+Xs42E1ctWY7nnpAf6AHblDFmL9r4gArj/PGt/C7 MPs+cjhYP/xTsw1fbX+c4Be8FhfKe9kWvRQAFR3dR8J7j0U8Ke81f+UfK+BR4Qvf2L u3NI2aWNsom+kdy+WhdzYwebYkO5whtECElmpKk52AcBrXmWSOXkjPzpHW82dtptsK WVS9zZxOPDSSuD8kV2q3lPgRA1eW0N2G3kj+UphnHtCuqqYalBXHL2uWGDhJqpu9hw 5J8O+sj33b1mw== Date: Thu, 16 Jul 2026 10:18:59 +0200 From: Maxime Ripard To: Xaver Hugl Cc: Maarten Lankhorst , Thomas Zimmermann , David Airlie , Simona Vetter , Daniel Stone , Harry Wentland , Jonas =?utf-8?B?w4VkYWhs?= , Michel =?utf-8?Q?D=C3=A4nzer?= , Pekka Paalanen , Sebastian Wick , Simon Ser , Victoria Brekenfeld , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC 0/8] drm: Add DRM_MODE_ATOMIC_RESET flag Message-ID: <20260716-expert-crouching-bonobo-ffd0b6@houat> References: <20260708-drm-reset-state-flag-v1-0-c37dc985485d@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha384; protocol="application/pgp-signature"; boundary="synlwefppugk5zgo" Content-Disposition: inline In-Reply-To: --synlwefppugk5zgo Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH RFC 0/8] drm: Add DRM_MODE_ATOMIC_RESET flag MIME-Version: 1.0 Hi Xaver, On Wed, Jul 08, 2026 at 08:25:36PM +0200, Xaver Hugl wrote: > Hi, >=20 > Thanks for working on this, it'll be great to finally have this solved pr= operly. >=20 > > Open question: should DRM_MODE_ATOMIC_RESET require > > DRM_MODE_ATOMIC_ALLOW_MODESET? A full state reset will change CRTC > > active states, which is effectively a modeset. Without requiring it, > > a reset could pass flag validation but fail later at atomic_check in > > a confusing way. > > The compositor may use the same CRTC states, modes etc; whether or not > the commit actually ends up requiring a modeset depends entirely on > the exact contents of the commit. So I definitely wouldn't require > ALLOW_MODESET. Just to make sure we're on the same page, you're saying that when using the reset flag, the compositor is expected to fill the state with enough that a modeset is unlikely to happen anyway? Maxime --synlwefppugk5zgo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iJUEABMJAB0WIQTkHFbLp4ejekA/qfgnX84Zoj2+dgUCaliT8wAKCRAnX84Zoj2+ dtj5AYDBzhLK638oLf5/0o6aTZv6zoEZ5aJivXx7/5FW/eanaFacq+6rnM810xbP VNDA50EBgLW2bz5DIlh7gyE5yibQif6lGrNqW9lEiXoI7WO9GRg/DXDsDylo5gZy lp8k8LZ8xg== =xvJ5 -----END PGP SIGNATURE----- --synlwefppugk5zgo--