All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Navare, Manasi" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Nuke dg2_ddi_pre_enable_dp()
Date: Wed, 19 Jan 2022 21:47:33 +0200	[thread overview]
Message-ID: <Yehq1eK+R3kZhO6J@intel.com> (raw)
In-Reply-To: <20220119190942.GA20150@labuser-Z97X-UD5H>

On Wed, Jan 19, 2022 at 11:09:47AM -0800, Navare, Manasi wrote:
> On Wed, Jan 19, 2022 at 05:17:05PM +0200, Jani Nikula wrote:
> > On Wed, 19 Jan 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > dg2_ddi_pre_enable_dp() has outlived its usefulness so eliminate
> > > it.
> > >
> > > The one thing that tgl_ddi_pre_enable_dp() is missing that we
> > > need is intel_ddi_config_transcoder_dp2(). So we'll bring that
> > > over.
> > >
> > > tgl_ddi_pre_enable_dp() does also have a few things that
> > > dg2_ddi_pre_enable_dp() didn't have:
> > > - icl_program_mg_dp_mode() -> nop due to intel_phy_is_tc()==false on DG2
> > > - intel_ddi_power_up_lanes() -> nop due to intel_phy_is_combo()==false on DG2
> > > - intel_ddi_mso_configure() -> only matters for MSO panels
> > >
> > > Another slight difference is that dg2_ddi_pre_enable_dp() was
> > > missing a bigjoiner check around intel_dsc_enable(), which
> > > tgl_ddi_pre_enable_dp() does have.
> 
> Thanks Ville for this patch, I was just comparing differences between dg2_pre_enable_dp and tgl_pre_enable_dp
> in regards to a bug and there is totally no need for two functions with the checks you have here.
> 
> For the bigjoiner check aroind intel_dsc_enable(), I think the function intel_dsc_dp_pps_write(encoder, crtc_state);
> also needs to be moved into that check. 
> And then this functions needs to be called from icl_ddi_bigjoiner_pre_enable() where we call intel_dsc_enable

The video DIP lives in the transcoder so we don't want to write it
twice.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-01-19 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 12:21 [Intel-gfx] [PATCH] drm/i915: Nuke dg2_ddi_pre_enable_dp() Ville Syrjala
2022-01-19 13:08 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-01-19 13:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-19 15:17 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-01-19 19:09   ` Navare, Manasi
2022-01-19 19:47     ` Ville Syrjälä [this message]
2022-01-19 15:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " 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=Yehq1eK+R3kZhO6J@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=manasi.d.navare@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.