From: Harry Wentland <harry.wentland@amd.com>
To: YueHaibing <yuehaibing@huawei.com>,
sunpeng.li@amd.com, alexander.deucher@amd.com,
christian.koenig@amd.com, airlied@linux.ie, daniel@ffwll.ch,
mikita.lipski@amd.com, eryk.brol@amd.com
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] drm/amd/display: Create trigger_hotplug entry
Date: Thu, 10 Sep 2020 11:35:15 -0400 [thread overview]
Message-ID: <dcdc327c-c0d1-85cb-28fa-5b7cb5d4e555@amd.com> (raw)
In-Reply-To: <20200910031352.39992-1-yuehaibing@huawei.com>
On 2020-09-09 11:13 p.m., YueHaibing wrote:
> Add trigger_hotplug debugfs entry.
>
> Fixes: 6f77b2ac6280 ("drm/amd/display: Add connector HPD trigger debugfs entry")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> ---
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c
> index 94fcb086154c..83da24aced45 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c
> @@ -2098,6 +2098,7 @@ static const struct {
> const struct file_operations *fops;
> } dp_debugfs_entries[] = {
> {"link_settings", &dp_link_settings_debugfs_fops},
> + {"trigger_hotplug", &dp_trigger_hotplug_debugfs_fops},
> {"phy_settings", &dp_phy_settings_debugfs_fop},
> {"test_pattern", &dp_phy_test_pattern_fops},
> #ifdef CONFIG_DRM_AMD_DC_HDCP
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-09-10 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 3:13 [PATCH -next] drm/amd/display: Create trigger_hotplug entry YueHaibing
2020-09-10 15:35 ` Harry Wentland [this message]
2020-09-15 19:46 ` Alex Deucher
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=dcdc327c-c0d1-85cb-28fa-5b7cb5d4e555@amd.com \
--to=harry.wentland@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eryk.brol@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikita.lipski@amd.com \
--cc=sunpeng.li@amd.com \
--cc=yuehaibing@huawei.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