From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 2/3] drm/i915/display: debugfs entry to control ignore long hpd flag
Date: Tue, 14 Feb 2023 13:44:19 +0200 [thread overview]
Message-ID: <87o7pwsc8c.fsf@intel.com> (raw)
In-Reply-To: <20230207160311.930772-3-vinod.govindapillai@intel.com>
On Tue, 07 Feb 2023, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> Knob to control ignoring the long hpds. Set this to true will
> start ignoring the long HPDs generated by the displays. Useful
> for use cases like CI systems where we dont expect to disconnect
> the panels.
>
> v2: Address patch styling comments (Jani Nikula)
>
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hotplug.c | 25 ++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hotplug.c b/drivers/gpu/drm/i915/display/intel_hotplug.c
> index f0a2aa648bb8..41372a10288c 100644
> --- a/drivers/gpu/drm/i915/display/intel_hotplug.c
> +++ b/drivers/gpu/drm/i915/display/intel_hotplug.c
> @@ -939,6 +939,29 @@ static const struct file_operations i915_hpd_short_storm_ctl_fops = {
> .write = i915_hpd_short_storm_ctl_write,
> };
>
> +static int i915_ignore_long_hpd_set(void *data, u64 val)
> +{
> + struct drm_i915_private *i915 = data;
> +
> + drm_dbg_kms(&i915->drm, "Ignoring long HPDs: %s\n", str_yes_no(val));
> +
> + i915->display.hotplug.ignore_long_hpd = val;
> +
> + return 0;
> +}
> +
> +static int i915_ignore_long_hpd_get(void *data, u64 *val)
> +{
> + struct drm_i915_private *i915 = data;
> +
> + *val = i915->display.hotplug.ignore_long_hpd;
> +
> + return 0;
> +}
> +
> +DEFINE_SIMPLE_ATTRIBUTE(i915_ignore_long_hpd_fops, i915_ignore_long_hpd_get,
> + i915_ignore_long_hpd_set, "%llu\n");
> +
> void intel_hpd_debugfs_register(struct drm_i915_private *i915)
> {
> struct drm_minor *minor = i915->drm.primary;
> @@ -947,4 +970,6 @@ void intel_hpd_debugfs_register(struct drm_i915_private *i915)
> i915, &i915_hpd_storm_ctl_fops);
> debugfs_create_file("i915_hpd_short_storm_ctl", 0644, minor->debugfs_root,
> i915, &i915_hpd_short_storm_ctl_fops);
> + debugfs_create_file("i915_ignore_long_hpd", 0644, minor->debugfs_root,
> + i915, &i915_ignore_long_hpd_fops);
See debugfs_create_bool(). This whole patch becomes so simple that
should be part of the previous patch, really.
> }
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-02-14 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 16:03 [Intel-gfx] [PATCH v3 0/3] Provision to ignore long HPDs in CI systems Vinod Govindapillai
2023-02-07 16:03 ` [Intel-gfx] [PATCH v3 1/3] drm/i915/display: ignore long HPDs based on a flag Vinod Govindapillai
2023-02-07 16:03 ` [Intel-gfx] [PATCH v3 2/3] drm/i915/display: debugfs entry to control ignore long hpd flag Vinod Govindapillai
2023-02-14 11:44 ` Jani Nikula [this message]
2023-02-07 16:03 ` [Intel-gfx] [PATCH v3 3/3] drm/i915/display: ignore link training failures in CI Vinod Govindapillai
2023-02-07 16:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Provision to ignore long HPDs in CI systems (rev4) Patchwork
2023-02-07 19:06 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=87o7pwsc8c.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinod.govindapillai@intel.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).