From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Souza\, Jose" <jose.souza@intel.com>,
"ville.syrjala\@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "Pandey, Hariom" <hariom.pandey@intel.com>,
"Ausmus, James" <james.ausmus@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
Subject: Re: [PATCH v2] drm/i915/edp/jsl: Update vswing table for HBR and HBR2
Date: Wed, 30 Sep 2020 15:31:57 +0300 [thread overview]
Message-ID: <87362zo37m.fsf@intel.com> (raw)
In-Reply-To: <a4a075597c7d3e65b25598ab696a59eccbd2a069.camel@intel.com>
On Tue, 29 Sep 2020, "Souza, Jose" <jose.souza@intel.com> wrote:
> On Tue, 2020-09-29 at 23:02 +0300, Ville Syrjälä wrote:
>> If the thing has nothing to do PCH then it should not use the PCH type
>> for the the check. Instead we should just do the EHL/JSL split.
>
> In the first version Matt Roper suggested to use PCH to differentiate
> between EHL and JSL, Jani also agreed with this solution.This 2 PCHs
> can only be associate with EHL and JSL respectively, so no downsides
> here.
FWIW I said, "If the difference is in the PCH", without pondering
further.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-09-30 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 12:11 [PATCH v2] drm/i915/edp/jsl: Update vswing table for HBR and HBR2 Tejas Upadhyay
2020-09-29 12:52 ` Ville Syrjälä
2020-09-29 13:17 ` Surendrakumar Upadhyay, TejaskumarX
2020-09-29 19:33 ` Souza, Jose
2020-09-29 20:02 ` Ville Syrjälä
2020-09-29 20:20 ` Souza, Jose
2020-09-29 20:30 ` Ville Syrjälä
2020-09-29 20:34 ` Souza, Jose
2020-09-29 21:01 ` Matt Roper
2020-09-29 21:11 ` Ville Syrjälä
2020-09-29 21:59 ` Ville Syrjälä
2020-09-29 23:38 ` Matt Roper
2020-09-30 10:38 ` Ville Syrjälä
2020-09-30 12:57 ` Jani Nikula
2020-09-30 18:20 ` Matt Roper
2020-09-30 12:31 ` Jani Nikula [this message]
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=87362zo37m.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hariom.pandey@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=tejaskumarx.surendrakumar.upadhyay@intel.com \
--cc=ville.syrjala@linux.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