All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Gustavo Sousa <gustavo.sousa@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH v3 0/3] drm/i915/xe3lpd: Update bandwidth parameters
Date: Mon, 10 Mar 2025 18:37:15 +0200	[thread overview]
Message-ID: <Z88VOxMunnhE_koL@intel.com> (raw)
In-Reply-To: <87ldtdghbo.fsf@intel.com>

On Mon, Mar 10, 2025 at 03:12:43PM +0200, Jani Nikula wrote:
> On Fri, 07 Mar 2025, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> > Bandwidth parameters for Xe3_LPD have been updated with respect to
> > previous display releases. Encode them into xe3lpd_sa_info and use that
> > new struct.
> >
> > Since we are touching intel_bw.c, also take the opportunity convert it
> > to intel_display.
> 
> In case you didn't notice already, this series and [1] from Ville will
> conflict badly with each other. Please collaborate to sort out which
> series to merge first.

I can rebase my stuff, so no worries.

> 
> Thanks,
> Jani.
> 
> 
> [1] https://lore.kernel.org/r/20250307180139.15744-1-ville.syrjala@linux.intel.com
> 
> 
> >
> > Changes in v2:
> >   - Fix typo in patch #2.
> >
> > Changes in v3:
> > - Squash patches #1 and #2 into a single one and modify it to convert
> >   intel_bw.c internally to intel_display (new patch subject is
> >   "drm/i915/display: Convert intel_bw.c internally to intel_display").
> > - Add a new patch #2 to convert intel_bw.c externally to intel_display.
> > - Link to v2: https://lore.kernel.org/r/20250217153550.43909-1-gustavo.sousa@intel.com
> >
> > ---
> > Gustavo Sousa (3):
> >       drm/i915/display: Convert intel_bw.c internally to intel_display
> >       drm/i915/display: Convert intel_bw.c externally to intel_display
> >       drm/i915/xe3lpd: Update bandwidth parameters
> >
> >  drivers/gpu/drm/i915/display/intel_bw.c            | 440 +++++++++++----------
> >  drivers/gpu/drm/i915/display/intel_bw.h            |   9 +-
> >  drivers/gpu/drm/i915/display/intel_cdclk.c         |   3 +-
> >  .../gpu/drm/i915/display/intel_display_driver.c    |   2 +-
> >  drivers/gpu/drm/i915/display/skl_watermark.c       |  10 +-
> >  drivers/gpu/drm/i915/i915_driver.c                 |   2 +-
> >  drivers/gpu/drm/xe/display/xe_display.c            |   2 +-
> >  7 files changed, 245 insertions(+), 223 deletions(-)
> > ---
> > base-commit: f811577f424491a57b1e8669bde62998227d6907
> > change-id: 20250228-xe3lpd-bandwidth-update-f011599c0c3e
> >
> > Best regards,
> 
> -- 
> Jani Nikula, Intel

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-03-10 16:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 19:25 [PATCH v3 0/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
2025-03-07 19:25 ` [PATCH v3 1/3] drm/i915/display: Convert intel_bw.c internally to intel_display Gustavo Sousa
2025-03-10 16:47   ` Ville Syrjälä
2025-03-10 19:00     ` Gustavo Sousa
2025-03-11  9:26       ` Jani Nikula
2025-03-11 11:43         ` Gustavo Sousa
2025-03-07 19:25 ` [PATCH v3 2/3] drm/i915/display: Convert intel_bw.c externally " Gustavo Sousa
2025-03-10 16:49   ` Ville Syrjälä
2025-03-07 19:25 ` [PATCH v3 3/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
2025-03-07 20:29 ` ✗ Fi.CI.SPARSE: warning for drm/i915/xe3lpd: Update bandwidth parameters (rev3) Patchwork
2025-03-07 20:57 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-07 23:42 ` ✓ CI.Patch_applied: success " Patchwork
2025-03-07 23:42 ` ✓ CI.checkpatch: " Patchwork
2025-03-07 23:44 ` ✓ CI.KUnit: " Patchwork
2025-03-08  0:00 ` ✓ CI.Build: " Patchwork
2025-03-08  0:03 ` ✓ CI.Hooks: " Patchwork
2025-03-08  0:04 ` ✗ CI.checksparse: warning " Patchwork
2025-03-08  0:24 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-09 12:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-10 13:12 ` [PATCH v3 0/3] drm/i915/xe3lpd: Update bandwidth parameters Jani Nikula
2025-03-10 16:37   ` Ville Syrjälä [this message]
2025-03-10 19:01     ` Gustavo Sousa

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=Z88VOxMunnhE_koL@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=matthew.d.roper@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.