From: Maxime Ripard <mripard@kernel.org>
To: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
quic_abhinavk@quicinc.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dmitry.baryshkov@linaro.org,
robdclark@gmail.com
Subject: Re: [PATCH v3 0/2] drm: Allow encoder modeset when connectors are changed
Date: Mon, 16 Dec 2024 12:06:53 +0100 [thread overview]
Message-ID: <20241216-daring-opalescent-herring-bfdc8f@houat> (raw)
In-Reply-To: <20241211-abhinavk-modeset-fix-v3-0-0de4bf3e7c32@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
On Wed, Dec 11, 2024 at 01:18:41PM -0800, Jessica Zhang wrote:
> Call encoder mode_set() when connectors are changed. This avoids issues
> for cases where the connectors are changed but CRTC mode is not.
Looks great, thanks a lot for doing the tests :)
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2024-12-16 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 21:18 Jessica Zhang
2024-12-11 21:18 ` [PATCH v3 1/2] drm: allow encoder mode_set even when connectors change for crtc Jessica Zhang
2024-12-11 21:18 ` [PATCH v3 2/2] drm/tests: Add test for drm_atomic_helper_commit_modeset_disables() Jessica Zhang
2024-12-11 22:50 ` Dmitry Baryshkov
2025-02-04 11:23 ` Simona Vetter
2024-12-16 11:06 ` Maxime Ripard [this message]
2024-12-16 18:27 ` [PATCH v3 0/2] drm: Allow encoder modeset when connectors are changed Abhinav Kumar
2024-12-17 15:02 ` Maxime Ripard
2024-12-20 2:05 ` Dmitry Baryshkov
2025-01-07 21:43 ` Abhinav Kumar
2025-01-07 23:31 ` Dmitry Baryshkov
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=20241216-daring-opalescent-herring-bfdc8f@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=robdclark@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®