intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Thomas Zimmermann <tzimmermann@suse.de>
Subject: [Intel-gfx] [PATCH v3 0/7] drm: Try to fix encoder possible_clones/crtc
Date: Tue, 11 Feb 2020 18:22:01 +0200	[thread overview]
Message-ID: <20200211162208.16224-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Another respin of the possible_clones/crtcs fixing.

Changes based on v2 review:
- introduce drm_mode_config_validate()
- WARN for possible_clones!=0 when the encoder
  itself isn't in the mask
- update the documentation to match the code

Other changes:
- sligth refactoring of the code to make it
  more consistent
- add a patch to fixup possible_crtcs too (might not
  be needed but included it just in case).

Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Daniel Vetter <daniel@ffwll.ch>

Ville Syrjälä (7):
  drm: Include the encoder itself in possible_clones
  drm/gma500: Sanitize possible_clones
  drm/exynos: Use drm_encoder_mask()
  drm/imx: Remove the bogus possible_clones setup
  drm: Validate encoder->possible_clones
  drm: Validate encoder->possible_crtcs
  drm: Allow drivers to leave encoder->possible_crtcs==0

 drivers/gpu/drm/drm_crtc_internal.h     |  1 +
 drivers/gpu/drm/drm_drv.c               |  3 +
 drivers/gpu/drm/drm_mode_config.c       | 97 +++++++++++++++++++++++++
 drivers/gpu/drm/exynos/exynos_drm_drv.c |  5 +-
 drivers/gpu/drm/gma500/framebuffer.c    | 16 ++--
 drivers/gpu/drm/gma500/mdfld_dsi_dpi.c  |  4 +-
 drivers/gpu/drm/imx/imx-drm-core.c      |  4 +-
 include/drm/drm_encoder.h               | 12 ++-
 8 files changed, 125 insertions(+), 17 deletions(-)

-- 
2.24.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2020-02-11 16:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 16:22 Ville Syrjala [this message]
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 1/7] drm: Include the encoder itself in possible_clones Ville Syrjala
2020-02-11 16:58   ` Daniel Vetter
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 2/7] drm/gma500: Sanitize possible_clones Ville Syrjala
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 3/7] drm/exynos: Use drm_encoder_mask() Ville Syrjala
2020-02-17  2:27   ` Inki Dae
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 4/7] drm/imx: Remove the bogus possible_clones setup Ville Syrjala
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 5/7] drm: Validate encoder->possible_clones Ville Syrjala
2020-02-11 17:02   ` Daniel Vetter
2020-02-11 17:13     ` Ville Syrjälä
2020-02-12  8:56       ` Daniel Vetter
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 6/7] drm: Validate encoder->possible_crtcs Ville Syrjala
2020-02-11 17:04   ` Daniel Vetter
2020-09-06 11:19     ` Jan Kiszka
2020-09-07  7:14       ` Daniel Vetter
2020-09-10 18:18         ` Deucher, Alexander
2020-09-29  9:36           ` Jan Kiszka
2020-09-29 20:04             ` Alex Deucher
2020-12-03 21:30               ` Alex Deucher
2020-12-09 13:17                 ` Daniel Vetter
2020-12-14 20:26                 ` Jan Kiszka
2020-02-11 16:22 ` [Intel-gfx] [PATCH v3 7/7] drm: Allow drivers to leave encoder->possible_crtcs==0 Ville Syrjala
2020-02-11 17:05   ` Daniel Vetter
2020-02-11 17:14     ` Ville Syrjälä
2020-02-12  9:07       ` Daniel Vetter
2020-02-12  9:08         ` Daniel Vetter
2020-03-18 16:44           ` Ville Syrjälä
2020-12-03 22:16 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Try to fix encoder possible_clones/crtc (rev4) Patchwork

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=20200211162208.16224-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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;
as well as URLs for NNTP newsgroup(s).