From: Sean Anderson <sean.anderson@linux.dev>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
David Airlie <airlied@gmail.com>,
Michal Simek <michal.simek@amd.com>,
Daniel Vetter <daniel@ffwll.ch>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH v6 0/8] drm: zynqmp_dp: IRQ cleanups and debugfs support
Date: Tue, 1 Oct 2024 14:31:28 -0400 [thread overview]
Message-ID: <5e9769dd-459a-4ff3-aebb-bb7057192733@linux.dev> (raw)
In-Reply-To: <20240809193600.3360015-1-sean.anderson@linux.dev>
On 8/9/24 15:35, Sean Anderson wrote:
> This series cleans up the zyqnmp_dp IRQ and locking situation. Once
> that's done, it adds debugfs support. The intent is to enable compliance
> testing or to help debug signal-integrity issues.
>
> Previously, I discussed converting the HPD work(s) to a threaded IRQ. I
> did not end up doing that for this series since the steps would be
>
> - Add locking
> - Move link retraining to a work function
> - Harden the IRQ
> - Merge the works into a threaded IRQ (omitted)
>
> Which with the exception of the final step is the same as leaving those
> works as-is. Conversion to a threaded IRQ can be done as a follow-up.
>
> Changes in v6:
> - Unplug DRM device before removal
> - Fix hang upon driver removal
> - Rebase onto drm-misc/drm-misc-next
>
> Changes in v5:
> - Rebase onto drm-misc/drm-misc-next
>
> Changes in v4:
> - Rebase onto drm/drm-next
>
> Changes in v3:
> - Convert to a hard IRQ
> - Use AUX IRQs instead of polling
> - Take dp->lock in zynqmp_dp_hpd_work_func
>
> Changes in v2:
> - Split off the HPD IRQ work into another commit
> - Expand the commit message
> - Document hpd_irq_work
> - Document debugfs files
> - Add ignore_aux_errors and ignore_hpd debugfs files to replace earlier
> implicit functionality
> - Attempt to fix unreproducable, spurious build warning
> - Drop "Optionally ignore DPCD errors" in favor of a debugfs file
> directly affecting zynqmp_dp_aux_transfer.
>
> Sean Anderson (8):
> drm: zynqmp_kms: Unplug DRM device before removal
> drm: zynqmp_dp: Add locking
> drm: zynqmp_dp: Don't retrain the link in our IRQ
> drm: zynqmp_dp: Convert to a hard IRQ
> drm: zynqmp_dp: Use AUX IRQs instead of polling
> drm: zynqmp_dp: Split off several helper functions
> drm: zynqmp_dp: Take dp->lock in zynqmp_dp_hpd_work_func
> drm: zynqmp_dp: Add debugfs interface for compliance testing
>
> Documentation/gpu/drivers.rst | 1 +
> Documentation/gpu/zynqmp.rst | 149 ++++++
> MAINTAINERS | 1 +
> drivers/gpu/drm/xlnx/zynqmp_dp.c | 846 ++++++++++++++++++++++++++++--
> drivers/gpu/drm/xlnx/zynqmp_kms.c | 2 +-
> 5 files changed, 951 insertions(+), 48 deletions(-)
> create mode 100644 Documentation/gpu/zynqmp.rst
>
ping
--Sean
next prev parent reply other threads:[~2024-10-01 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 19:35 [PATCH v6 0/8] drm: zynqmp_dp: IRQ cleanups and debugfs support Sean Anderson
2024-08-09 19:35 ` [PATCH v6 1/8] drm: zynqmp_kms: Unplug DRM device before removal Sean Anderson
2024-08-09 19:35 ` [PATCH v6 2/8] drm: zynqmp_dp: Add locking Sean Anderson
2024-08-09 19:35 ` [PATCH v6 3/8] drm: zynqmp_dp: Don't retrain the link in our IRQ Sean Anderson
2024-08-09 19:35 ` [PATCH v6 4/8] drm: zynqmp_dp: Convert to a hard IRQ Sean Anderson
2024-10-02 13:52 ` Tomi Valkeinen
2024-08-09 19:35 ` [PATCH v6 5/8] drm: zynqmp_dp: Use AUX IRQs instead of polling Sean Anderson
2024-08-09 19:35 ` [PATCH v6 6/8] drm: zynqmp_dp: Split off several helper functions Sean Anderson
2024-08-09 19:35 ` [PATCH v6 7/8] drm: zynqmp_dp: Take dp->lock in zynqmp_dp_hpd_work_func Sean Anderson
2024-08-09 19:36 ` [PATCH v6 8/8] drm: zynqmp_dp: Add debugfs interface for compliance testing Sean Anderson
2024-10-01 18:31 ` Sean Anderson [this message]
2024-10-02 14:50 ` [PATCH v6 0/8] drm: zynqmp_dp: IRQ cleanups and debugfs support Tomi Valkeinen
2024-10-03 14:53 ` Sean Anderson
2024-10-25 14:58 ` Sean Anderson
2024-10-28 15:04 ` Tomi Valkeinen
2024-10-30 12:30 ` Tomi Valkeinen
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=5e9769dd-459a-4ff3-aebb-bb7057192733@linux.dev \
--to=sean.anderson@linux.dev \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.