From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: [PATCH v2 0/3] drm/i915/xe3lpd: Update bandwidth parameters
Date: Mon, 17 Feb 2025 12:35:22 -0300 [thread overview]
Message-ID: <20250217153550.43909-1-gustavo.sousa@intel.com> (raw)
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 to make it
use display-specific platform checkers, which is what patches #1 and #2
are about.
v2:
- Fix typo in patch #2.
Gustavo Sousa (3):
drm/i915/display: Use display variable in intel_bw.c
drm/i915/display: Use display-specific platform checks in intel_bw.c
drm/i915/xe3lpd: Update bandwidth parameters
drivers/gpu/drm/i915/display/intel_bw.c | 192 ++++++++++++++----------
1 file changed, 112 insertions(+), 80 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-17 15:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:35 Gustavo Sousa [this message]
2025-02-17 15:35 ` [PATCH v2 1/3] drm/i915/display: Use display variable in intel_bw.c Gustavo Sousa
2025-02-17 17:44 ` Ville Syrjälä
2025-02-17 20:05 ` Gustavo Sousa
2025-02-21 12:15 ` Vodapalli, Ravi Kumar
2025-02-17 15:35 ` [PATCH v2 2/3] drm/i915/display: Use display-specific platform checks " Gustavo Sousa
2025-02-17 17:49 ` Ville Syrjälä
2025-02-17 18:03 ` Ville Syrjälä
2025-02-17 15:35 ` [PATCH v2 3/3] drm/i915/xe3lpd: Update bandwidth parameters Gustavo Sousa
2025-02-26 22:33 ` Matt Roper
2025-02-17 16:21 ` ✓ CI.Patch_applied: success for drm/i915/xe3lpd: Update bandwidth parameters (rev2) Patchwork
2025-02-17 16:21 ` ✓ CI.checkpatch: " Patchwork
2025-02-17 16:22 ` ✓ CI.KUnit: " Patchwork
2025-02-17 16:39 ` ✓ CI.Build: " Patchwork
2025-02-17 16:41 ` ✓ CI.Hooks: " Patchwork
2025-02-17 16:42 ` ✓ CI.checksparse: " Patchwork
2025-02-18 7:16 ` ✓ Xe.CI.BAT: " 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=20250217153550.43909-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox