intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mustamin B Mustaffa <mustamin.b.mustaffa@intel.com>
Cc: intel-gfx@lists.freedesktop.org, "Anuar,
	Nuhairi" <nuhairi.anuar@intel.com>
Subject: Re: [PATCH] drm/i915: fix the issue DP-1 not working in guest
Date: Wed, 14 Jun 2017 16:38:42 +0300	[thread overview]
Message-ID: <20170614133842.GM12629@intel.com> (raw)
In-Reply-To: <1497419250-147816-1-git-send-email-mustamin.b.mustaffa@intel.com>

On Wed, Jun 14, 2017 at 01:47:30PM +0800, Mustamin B Mustaffa wrote:
> From: "Anuar, Nuhairi" <nuhairi.anuar@intel.com>
> 
> In GVT guest, when port A is DP, i915 will force it as an EDP panel,
> which
> will cause DP-1 not working in GVT guest.
> This patch fixed this issue by check intel_vgpu_active() in
> intel_ddi_compute_config().
> 
> Signed-off-by: Min He <min.he@intel.com>
> Signed-off-by: Nuhairi Anuar <nuhairi.anuar@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_ddi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> index 66b367d..1110cbc 100644
> --- a/drivers/gpu/drm/i915/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> @@ -2069,7 +2069,7 @@ static bool intel_ddi_compute_config(struct intel_encoder *encoder,
>  
>  	WARN(type == INTEL_OUTPUT_UNKNOWN, "compute_config() on unknown output!\n");
>  
> -	if (port == PORT_A)
> +	if (port == PORT_A && !intel_vgpu_active(dev_priv))
>  		pipe_config->cpu_transcoder = TRANSCODER_EDP;

And why exactly are you trying to register DP on port A?

>  
>  	if (type == INTEL_OUTPUT_HDMI)
> -- 
> 1.9.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-06-14 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  5:47 [PATCH] drm/i915: fix the issue DP-1 not working in guest Mustamin B Mustaffa
2017-06-14  6:11 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-06-14 13:38 ` Ville Syrjälä [this message]
2018-02-20  6:40 ` [PATCH] " Mustamin B Mustaffa
2018-02-20 11:35   ` Jani Nikula
2018-02-21  0:01     ` Mustaffa, Mustamin B
2018-02-21  8:03       ` Jani Nikula
2018-02-21  8:21         ` Mustaffa, Mustamin B
2018-02-20  7:13 ` ✓ Fi.CI.BAT: success for drm/i915: fix the issue DP-1 not working in guest (rev2) Patchwork
2018-02-20  7:57 ` ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2017-06-14 14:55 [PATCH] drm/i915: fix the issue DP-1 not working in guest Anuar, Nuhairi
2017-06-15  3:53 ` Anuar, Nuhairi
2017-06-15 10:28   ` Ville Syrjälä
2017-06-15 20:54     ` Jani Nikula

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=20170614133842.GM12629@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mustamin.b.mustaffa@intel.com \
    --cc=nuhairi.anuar@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).