From: Maxime Ripard <maxime@cerno.tech>
To: Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>, Eric Anholt <eric@anholt.net>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <maxime@cerno.tech>
Cc: Tim Gover <tim.gover@raspberrypi.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
dri-devel@lists.freedesktop.org,
Hoegeun Kwon <hoegeun.kwon@samsung.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] drm/vc4: Rework the HVS muxing code
Date: Fri, 20 Nov 2020 15:42:43 +0100 [thread overview]
Message-ID: <20201120144245.398711-1-maxime@cerno.tech> (raw)
Hi,
Here's a second attempt at fixing the current issues we have with the
muxing code that results in a PV muxing its HVS muxing when only another
CRTC is modified by a state, or vblank timeouts when trying to wait for a
vblank on a single CRTC while another one is inactive but enabled.
Let me know what you think,
Maxime
Changes from v3:
- Pulled some patches from the atomic_helper_commit series that reorder /
cleanup some code added here
- s/needs_muxing/update_muxing/, and some cleanups suggested by Thomas
- Removed the patches already applied
Changes from v1:
- Dropped the code trying to access all the CRTCs (whether in the state
or not) state
- Added Hoegeun Kwon's tags
- Fixed a build bisection error
- Cleaned up the private state using drmm_add_action_or_reset
- Rebased on current linux next
Maxime Ripard (2):
drm/vc4: kms: Store the unassigned channel list in the state
drm/vc4: kms: Don't disable the muxing of an active CRTC
drivers/gpu/drm/vc4/vc4_drv.h | 4 +
drivers/gpu/drm/vc4/vc4_kms.c | 199 ++++++++++++++++++++++++----------
2 files changed, 146 insertions(+), 57 deletions(-)
--
2.28.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-20 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 14:42 Maxime Ripard [this message]
2020-11-20 14:42 ` [PATCH v4 1/2] drm/vc4: kms: Store the unassigned channel list in the state Maxime Ripard
2020-11-20 14:42 ` [PATCH v4 2/2] drm/vc4: kms: Don't disable the muxing of an active CRTC Maxime Ripard
2020-11-23 7:50 ` Thomas Zimmermann
2020-11-23 16:59 ` 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=20201120144245.398711-1-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.vetter@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=hoegeun.kwon@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=phil@raspberrypi.com \
--cc=tim.gover@raspberrypi.com \
--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