From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: Manasi Navare <manasi.d.navare@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/atomic: don't reset link-status to GOOD without ALLOW_MODESET
Date: Wed, 3 Jun 2020 14:13:43 +0300 [thread overview]
Message-ID: <20200603111343.GO6112@intel.com> (raw)
In-Reply-To: <6Q-O7vKObfRu8cOyvcAxR_uRWgjQdlYgVursTGN2AaHtdaUZICSC6szFjkkDGXhyKF22Grj-aGCTC74OGhtuJ9JChitqvqtCVi1wr_Lnh6Y=@emersion.fr>
On Wed, Jun 03, 2020 at 10:45:23AM +0000, Simon Ser wrote:
> In update_output_state, the link-status property was reset to GOOD to
> ensure legacy drmModeSetCrtc re-trains the link. However this auto-reset
> is also performed on an atomic commit without ALLLOW_MODESET. If a
I didn't think udate_output_state() was getting called for
non-legacy paths. Where is that coming from?
> driver reads link-status to figure out whether to re-train the link,
> this could cause an atomic commit failure. User-space doesn't expect
> such a failure, because commits without ALLOW_MODESET aren't supposed to
> fail because of link training issues.
>
> Change update_output_state to implicitly reset link-status to GOOD only
> if ALLOW_MODESET is set. This is the case for legacy drmModeSetCrtc
> because drm_atomic_state_init sets it (and is used in
> drm_atomic_helper_set_config, called from drm_mode_setcrtc).
>
> Drivers don't seem to read link-status at the moment -- they seem to
> rely on user-space performing a modeset instead. So this shouldn't
> result in any change in behaviour, this should only prevent future
> failures if drivers start reading link-status.
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Suggested-by: Pekka Paalanen <ppaalanen@gmail.com>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/drm_atomic.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 965173fd0ac2..3d9d9e6f7397 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1426,7 +1426,8 @@ static int update_output_state(struct drm_atomic_state *state,
> return ret;
>
> /* Make sure legacy setCrtc always re-trains */
> - new_conn_state->link_status = DRM_LINK_STATUS_GOOD;
> + if (state->allow_modeset)
> + new_conn_state->link_status = DRM_LINK_STATUS_GOOD;
> }
> }
>
> --
> 2.26.2
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-03 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 10:45 [PATCH] drm/atomic: don't reset link-status to GOOD without ALLOW_MODESET Simon Ser
2020-06-03 11:06 ` Daniel Vetter
2020-06-03 11:13 ` Ville Syrjälä [this message]
2020-06-03 11:36 ` Daniel Vetter
2020-06-03 13:17 ` Simon Ser
2020-06-03 13:45 ` Daniel Vetter
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=20200603111343.GO6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=manasi.d.navare@intel.com \
/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