From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Cory Tusar <cory.tusar@zii.aero>, Chris Healy <cphealy@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] tc358767 test mode
Date: Wed, 11 Sep 2019 18:37:38 -0700 [thread overview]
Message-ID: <20190912013740.5638-1-andrew.smirnov@gmail.com> (raw)
Everyone:
This series is a couple of patches exposing TestCtl register of
tc358767, which can be pretty handy when troubleshooting link problems.
Changes since [v1]:
- Debugfs moved into a standalone directory and is now created as
a part of probe()
- Added tstctl_lock to ensure mutual exclusion of tstctl code and
bridge's enable/disable methods
- tc_tstctl_set() changed to function only if bridge was previosly
enabled
- Added comment explaining data format expected by "tstctl"
- Debugfs permission changed to reflect write-only nature of this
feature
- Original commit split into two
- Minor formatting changes
Thanks,
Andrey Smirnov
[v1] lore.kernel.org/r/20190826182524.5064-1-andrew.smirnov@gmail.com
Andrey Smirnov (2):
drm/bridge: tc358767: Introduce __tc_bridge_enable/disable()
drm/bridge: tc358767: Expose test mode functionality via debugfs
drivers/gpu/drm/bridge/tc358767.c | 184 ++++++++++++++++++++++++------
1 file changed, 148 insertions(+), 36 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-12 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 1:37 Andrey Smirnov [this message]
2019-09-12 1:37 ` [PATCH v2 1/2] drm/bridge: tc358767: Introduce __tc_bridge_enable/disable() Andrey Smirnov
2019-09-12 1:37 ` [PATCH v2 2/2] drm/bridge: tc358767: Expose test mode functionality via debugfs Andrey Smirnov
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=20190912013740.5638-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=cory.tusar@zii.aero \
--cc=cphealy@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).