All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsi: fix DSS CTL register offsets for TGL+
Date: Wed, 1 Mar 2023 18:00:51 +0200	[thread overview]
Message-ID: <Y/92swZjW47GuN2c@intel.com> (raw)
In-Reply-To: <Y/9xf6SkV1fG4JSA@intel.com>

On Wed, Mar 01, 2023 at 05:38:39PM +0200, Ville Syrjälä wrote:
> On Wed, Mar 01, 2023 at 05:14:09PM +0200, Jani Nikula wrote:
> > On TGL+ the DSS control registers are at different offsets, and there's
> > one per pipe. Fix the offsets to fix dual link DSI for TGL+.
> > 
> > There would be helpers for this in the DSC code, but just do the quick
> > fix now for DSI. Long term, we should probably move all the DSS handling
> > into intel_vdsc.c, so exporting the helpers seems counter-productive.
> 
> I'm not entirely happy with intel_vdsc.c since it handles
> both the hardware VDSC block (which includes DSS, and so
> also uncompressed joiner and MSO), and also some actual
> DSC calculations/etc. Might be nice to have a cleaner
> split of some sort.
> 
> That also reminds me that MSO+dsc/joiner is probably going
> to fail miserably given that neither side knows about the
> other and both poke the DSS registers.

I suppose MSO+joiner should just be rejected outright since 
the splitter seems to sit before the joiner in the path.
We'd need them to be the other way around.

But MSO+DSC does look plausible.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2023-03-01 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 15:14 [Intel-gfx] [PATCH] drm/i915/dsi: fix DSS CTL register offsets for TGL+ Jani Nikula
2023-03-01 15:14 ` Jani Nikula
2023-03-01 15:38 ` [Intel-gfx] " Ville Syrjälä
2023-03-01 15:38   ` Ville Syrjälä
2023-03-01 16:00   ` Ville Syrjälä [this message]
2023-03-06 16:25   ` [Intel-gfx] " Jani Nikula
2023-03-06 16:25     ` Jani Nikula
2023-03-01 21:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-03 14:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: fix DSS CTL register offsets for TGL+ (rev2) Patchwork
2023-03-04 13:13 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsi: fix DSS CTL register offsets for TGL+ Patchwork
2023-03-06 20:31 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsi: fix DSS CTL register offsets for TGL+ (rev2) 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=Y/92swZjW47GuN2c@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=stable@vger.kernel.org \
    /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.