From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Anuar, Nuhairi" <nuhairi.anuar@intel.com>
Cc: "Mustaffa, Mustamin B" <mustamin.b.mustaffa@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fix the issue DP-1 not working in guest
Date: Thu, 15 Jun 2017 13:28:56 +0300 [thread overview]
Message-ID: <20170615102856.GV12629@intel.com> (raw)
In-Reply-To: <A4B70D240F2FDF479543112EA9A25CCC40699231@PGSMSX107.gar.corp.intel.com>
On Thu, Jun 15, 2017 at 03:53:18AM +0000, Anuar, Nuhairi wrote:
> To be clear, I believe right now, GVT-g architecture on upstream still only have one Virtualized DP monitor which will be on port B/D, but we have patches (not yet upstream) that have 3 virtualized DP monitors which will be attached to Port A/B/D. So we need to add this flexibility in the code so that it is not conflicted with eDP logic.
Please don't do that. Real hardware doesn't support non-eDP on port A,
so your virtualized thing shouldn't either. Why aren't you putting it on
port C instead?
>
>
>
> From: Anuar, Nuhairi
> Sent: Wednesday, June 14, 2017 10:55 PM
> To: Ville Syrjälä <ville.syrjala@linux.intel.com>; He, Min <min.he@intel.com>
> Cc: intel-gfx@lists.freedesktop.org; Mustaffa, Mustamin B <mustamin.b.mustaffa@intel.com>
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix the issue DP-1 not working in guest
>
> For a virtualized boot, it is possible for port A to be tied to DP.
>
> Min He any additional comment?
>
> On Jun 14, 2017 9:38 PM, Ville Syrjälä <ville.syrjala@linux.intel.com<mailto:ville.syrjala@linux.intel.com>> wrote:
> On Wed, Jun 14, 2017 at 01:47:30PM +0800, Mustamin B Mustaffa wrote:
> > From: "Anuar, Nuhairi" <nuhairi.anuar@intel.com<mailto: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<mailto:min.he@intel.com>>
> > Signed-off-by: Nuhairi Anuar <nuhairi.anuar@intel.com<mailto: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<mailto:Intel-gfx@lists.freedesktop.org>
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
>
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-15 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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ä [this message]
2017-06-15 20:54 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2017-06-14 5:47 Mustamin B Mustaffa
2017-06-14 13:38 ` Ville Syrjälä
2018-02-20 6:40 ` 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
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=20170615102856.GV12629@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 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.