Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>,
	 Lucas Stach <l.stach@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	 Sascha Hauer <s.hauer@pengutronix.de>,
	imx@lists.linux.dev
Subject: Re: [PATCH 18/83] drm/imx/dcss: Switch to drm_mode_config_create_initial_state
Date: Thu, 5 Nov 2026 16:59:23 +0200	[thread overview]
Message-ID: <auyZr5qupit_zzfY@vm> (raw)
In-Reply-To: <20261105-drm-no-more-config-reset-v1-18-763560c2cc3f@kernel.org>

On Thu, Nov 05, 2026 at 03:07:35PM +0100, Maxime Ripard wrote:
> drm_mode_config_reset() has a dual role: it creates the initial KMS
> state at probe time, and resets hardware and software state during
> suspend/resume cycles.
> 
> Since the two roles need different behaviors (notably for objects like
> drm_private_obj that must persist across suspend/resume),
> drm_mode_config_create_initial_state() was introduced to handle only
> the initial state creation at probe time.
> 
> Switch to drm_mode_config_create_initial_state().
> 
> Signed-off-by: Maxime Ripard <mripard@kernel.org>

Reviewed-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>

-- 
Thanks,
Laurentiu

  reply	other threads:[~2026-11-05 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 14:07 [PATCH 00/83] drm: Switch drivers to drm_mode_config_create_initial_state Maxime Ripard
2026-11-05 14:07 ` [PATCH 17/83] drm/imx/dc: Switch " Maxime Ripard
2026-11-05 14:07 ` [PATCH 18/83] drm/imx/dcss: " Maxime Ripard
2026-11-05 14:59   ` Laurentiu Palcu [this message]
2026-11-05 14:07 ` [PATCH 19/83] drm/imx/ipuv3: " Maxime Ripard
2026-11-05 14:07 ` [PATCH 29/83] drm/lcdif: " Maxime Ripard
2026-11-05 14:07 ` [PATCH 30/83] drm/mxsfb: " Maxime Ripard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=auyZr5qupit_zzfY@vm \
    --to=laurentiu.palcu@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=mripard@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox