From: Thierry Reding <thierry.reding@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 03/21] drm/dp: Add drm_dp_link_reset() implementation
Date: Mon, 5 Aug 2019 14:23:32 +0200 [thread overview]
Message-ID: <20190805122350.8838-3-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190805122350.8838-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Subsequent patches will add non-volatile fields to struct drm_dp_link,
so introduce a function to zero out only the volatile fields.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/gpu/drm/drm_dp_helper.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
index ffc68d305afe..f5af71ec1b7d 100644
--- a/drivers/gpu/drm/drm_dp_helper.c
+++ b/drivers/gpu/drm/drm_dp_helper.c
@@ -336,6 +336,17 @@ int drm_dp_dpcd_read_link_status(struct drm_dp_aux *aux,
}
EXPORT_SYMBOL(drm_dp_dpcd_read_link_status);
+static void drm_dp_link_reset(struct drm_dp_link *link)
+{
+ if (!link)
+ return;
+
+ link->revision = 0;
+ link->rate = 0;
+ link->num_lanes = 0;
+ link->capabilities = 0;
+}
+
/**
* drm_dp_link_probe() - probe a DisplayPort link for capabilities
* @aux: DisplayPort AUX channel
@@ -352,7 +363,7 @@ int drm_dp_link_probe(struct drm_dp_aux *aux, struct drm_dp_link *link)
u8 values[3];
int err;
- memset(link, 0, sizeof(*link));
+ drm_dp_link_reset(link);
err = drm_dp_dpcd_read(aux, DP_DPCD_REV, values, sizeof(values));
if (err < 0)
--
2.22.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-05 12:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:23 [PATCH 01/21] drm/dp: Sort includes alphabetically Thierry Reding
2019-08-05 12:23 ` [PATCH 02/21] drm/dp: Add missing kerneldoc for struct drm_dp_link Thierry Reding
2019-08-05 12:23 ` Thierry Reding [this message]
2019-08-05 12:23 ` [PATCH 04/21] drm/dp: Track link capabilities alongside settings Thierry Reding
2019-08-08 11:39 ` Andrzej Hajda
2019-08-05 12:23 ` [PATCH 05/21] drm/dp: Turn link capabilities into booleans Thierry Reding
2019-08-08 11:52 ` Andrzej Hajda
2019-08-05 12:23 ` [PATCH 06/21] drm/dp: Probe link using existing parsing helpers Thierry Reding
2019-08-08 13:22 ` Philipp Zabel
2019-08-05 12:23 ` [PATCH 07/21] drm/dp: Read fast training capability from link Thierry Reding
2019-08-08 13:26 ` Philipp Zabel
2019-08-05 12:23 ` [PATCH 08/21] drm/dp: Read TPS3 capability from sink Thierry Reding
2019-08-05 12:23 ` [PATCH 09/21] drm/dp: Read channel coding " Thierry Reding
2019-08-05 12:23 ` [PATCH 10/21] drm/dp: Read alternate scrambler reset " Thierry Reding
2019-08-05 12:23 ` [PATCH 11/21] drm/dp: Read eDP version from DPCD Thierry Reding
2019-08-05 12:23 ` [PATCH 12/21] drm/dp: Read AUX read interval " Thierry Reding
2019-08-05 12:23 ` [PATCH 13/21] drm/dp: Do not busy-loop during link training Thierry Reding
2019-08-08 13:33 ` Philipp Zabel
2019-09-02 10:57 ` Thierry Reding
2019-08-05 12:23 ` [PATCH 14/21] drm/dp: Use drm_dp_aux_rd_interval() Thierry Reding
2019-08-08 13:17 ` Philipp Zabel
2019-09-02 11:06 ` Thierry Reding
2019-08-05 12:23 ` [PATCH 15/21] drm/dp: Add helper to get post-cursor adjustments Thierry Reding
2019-08-08 13:36 ` Philipp Zabel
2019-08-05 12:23 ` [PATCH 16/21] drm/dp: Set channel coding on link configuration Thierry Reding
2019-08-05 12:23 ` [PATCH 17/21] drm/dp: Enable alternate scrambler reset when supported Thierry Reding
2019-08-05 12:23 ` [PATCH 18/21] drm/dp: Add drm_dp_link_choose() helper Thierry Reding
2019-08-05 12:23 ` [PATCH 19/21] drm/dp: Add support for eDP link rates Thierry Reding
2019-08-05 12:23 ` [PATCH 20/21] drm/dp: Fix a couple of whitespace issues Thierry Reding
2019-08-08 13:18 ` Philipp Zabel
2019-09-02 11:10 ` Thierry Reding
2019-08-05 12:23 ` [PATCH 21/21] drm/bridge: tc358767: Use DP nomenclature Thierry Reding
2019-08-08 11:54 ` Andrzej Hajda
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=20190805122350.8838-3-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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