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: David Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, Michal Simek <michal.simek@amd.com>,
linux-arm-kernel@lists.infradead.org,
Daniel Vetter <daniel@ffwll.ch>,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH 0/6] drm: zynqmp_dp: Misc. patches and debugfs support
Date: Fri, 15 Mar 2024 19:09:10 -0400 [thread overview]
Message-ID: <20240315230916.1759060-1-sean.anderson@linux.dev> (raw)
This series adds debugfs support for the zynqmp_dp driver. The intent is
to enable compliance testing or to help debug signal-integrity issues.
The first three patches are general improvements (and could be applied
independently), while the last three add debugfs support.
Sean Anderson (6):
drm: zynqmp_dp: Downgrade log level for aux retries message
drm: zynqmp_dp: Adjust training values per-lane
drm: zynqmp_dp: Add locking
drm: zynqmp_dp: Split off several helper functions
drm: zynqmp_dp: Optionally ignore DPCD errors
drm: zynqmp_dp: Add debugfs interface for compliance testing
drivers/gpu/drm/xlnx/zynqmp_dp.c | 749 ++++++++++++++++++++++++++++---
1 file changed, 691 insertions(+), 58 deletions(-)
--
2.35.1.1320.gc452695387.dirty
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-15 23:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 23:09 Sean Anderson [this message]
2024-03-15 23:09 ` [PATCH 1/6] drm: zynqmp_dp: Downgrade log level for aux retries message Sean Anderson
2024-03-18 16:39 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 2/6] drm: zynqmp_dp: Adjust training values per-lane Sean Anderson
2024-03-18 17:06 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 3/6] drm: zynqmp_dp: Add locking Sean Anderson
2024-03-16 9:52 ` kernel test robot
2024-03-18 15:09 ` Sean Anderson
2024-03-18 17:16 ` Laurent Pinchart
2024-03-18 17:29 ` Sean Anderson
2024-03-18 17:59 ` Laurent Pinchart
2024-03-18 18:01 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 4/6] drm: zynqmp_dp: Split off several helper functions Sean Anderson
2024-03-18 17:41 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 5/6] drm: zynqmp_dp: Optionally ignore DPCD errors Sean Anderson
2024-03-18 17:47 ` Laurent Pinchart
2024-03-18 18:12 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing Sean Anderson
2024-03-16 10:14 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson
2024-03-18 17:50 ` Laurent Pinchart
2024-03-18 19:05 ` Sean Anderson
2024-03-20 6:03 ` Yujie Liu
2024-03-16 10:55 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson
2024-03-16 17:56 ` Dmitry Baryshkov
2024-03-18 15:22 ` Sean Anderson
2024-03-18 17:52 ` Laurent Pinchart
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=20240315230916.1759060-1-sean.anderson@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=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).