All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Kamati Srinivas <srinivasx.k@intel.com>
Cc: hariom.pandey@intel.com, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/jsl: Remove require_force_probe protection
Date: Mon, 19 Oct 2020 14:30:05 -0400	[thread overview]
Message-ID: <20201019183005.GB3149316@intel.com> (raw)
In-Reply-To: <20201015085308.3492-1-srinivasx.k@intel.com>

On Thu, Oct 15, 2020 at 08:53:08AM +0000, Kamati Srinivas wrote:
> Removing force probe protection from JSL platform. Did
> not observe warnings, errors, flickering or any visual
> defects while doing ordinary tasks like browsing and
> editing documents in a two monitor setup.

I'm afraid we first need to get a JSL on CI. Or what am I missing?

> 
> Signed-off-by: Kamati Srinivas <srinivasx.k@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 16d4e72bed09..a61195a1883a 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -849,7 +849,6 @@ static const struct intel_device_info ehl_info = {
>  static const struct intel_device_info jsl_info = {
>  	GEN11_FEATURES,
>  	PLATFORM(INTEL_JASPERLAKE),
> -	.require_force_probe = 1,
>  	.platform_engine_mask = BIT(RCS0) | BIT(BCS0) | BIT(VCS0) | BIT(VECS0),
>  	.ppgtt_size = 36,
>  };
> -- 
> 2.25.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Kamati Srinivas <srinivasx.k@intel.com>
Cc: hariom.pandey@intel.com, james.ausmus@intel.com,
	intel-gfx@lists.freedesktop.org, jose.souza@intel.com,
	dri-devel@lists.freedesktop.org,
	tejaskumarx.surendrakumar.upadhyay@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/jsl: Remove require_force_probe protection
Date: Mon, 19 Oct 2020 14:30:05 -0400	[thread overview]
Message-ID: <20201019183005.GB3149316@intel.com> (raw)
In-Reply-To: <20201015085308.3492-1-srinivasx.k@intel.com>

On Thu, Oct 15, 2020 at 08:53:08AM +0000, Kamati Srinivas wrote:
> Removing force probe protection from JSL platform. Did
> not observe warnings, errors, flickering or any visual
> defects while doing ordinary tasks like browsing and
> editing documents in a two monitor setup.

I'm afraid we first need to get a JSL on CI. Or what am I missing?

> 
> Signed-off-by: Kamati Srinivas <srinivasx.k@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 16d4e72bed09..a61195a1883a 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -849,7 +849,6 @@ static const struct intel_device_info ehl_info = {
>  static const struct intel_device_info jsl_info = {
>  	GEN11_FEATURES,
>  	PLATFORM(INTEL_JASPERLAKE),
> -	.require_force_probe = 1,
>  	.platform_engine_mask = BIT(RCS0) | BIT(BCS0) | BIT(VCS0) | BIT(VECS0),
>  	.ppgtt_size = 36,
>  };
> -- 
> 2.25.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-10-19 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  8:53 [Intel-gfx] [PATCH] drm/i915/jsl: Remove require_force_probe protection Kamati Srinivas
2020-10-15  8:53 ` Kamati Srinivas
2020-10-15  9:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-15 11:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-19 18:30 ` Rodrigo Vivi [this message]
2020-10-19 18:30   ` [Intel-gfx] [PATCH] " Rodrigo Vivi
  -- strict thread matches above, loose matches on Subject: below --
2021-06-29 10:53 Tejas Upadhyay
2021-06-29 15:17 ` Rodrigo Vivi
2021-06-29 15:20   ` Rodrigo Vivi

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=20201019183005.GB3149316@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hariom.pandey@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=srinivasx.k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.