From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Golani,
Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"Kandpal, Suraj" <suraj.kandpal@intel.com>
Subject: RE: [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal
Date: Thu, 02 Jul 2026 20:26:15 +0300 [thread overview]
Message-ID: <35eef66587306a256764b9d4a5e5316a73893099@intel.com> (raw)
In-Reply-To: <IA1PR11MB6348D8D9F53ECCFD47321C83B2F52@IA1PR11MB6348.namprd11.prod.outlook.com>
On Thu, 02 Jul 2026, "Golani, Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com> wrote:
> No. This change was made to align the driver with the updated VTOTAL
> programming requirements rather than to fix a regression introduced by
> a specific upstream commit.
>
> The regression we've recently observed during the GOP-to-driver
> handoff appears to be a separate issue introduced by this change and
> will need to be addressed with a follow-up fix.
Okay, thanks, sorry for the noise. :)
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-07-02 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 4:58 [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal Mitul Golani
2026-06-17 5:57 ` ✓ CI.KUnit: success for drm/i915/display: Program TRANS_VTOTAL from mode vtotal (rev4) Patchwork
2026-06-17 6:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-17 12:13 ` ✓ Xe.CI.FULL: " Patchwork
2026-07-02 15:41 ` [PATCH RESEND v2] drm/i915/display: Program TRANS_VTOTAL from mode vtotal Jani Nikula
2026-07-02 16:14 ` Golani, Mitulkumar Ajitkumar
2026-07-02 17:26 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-17 4:45 Mitul Golani
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=35eef66587306a256764b9d4a5e5316a73893099@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=suraj.kandpal@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