From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 0/5] drm/i915: extract vblank/scanline code to a separate file
Date: Wed, 18 Jan 2023 11:27:01 +0200 [thread overview]
Message-ID: <871qnsdwgq.fsf@intel.com> (raw)
In-Reply-To: <Y8bcI7udqQu8SzvP@intel.com>
On Tue, 17 Jan 2023, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Mon, Jan 16, 2023 at 02:56:11PM +0200, Jani Nikula wrote:
>> Basically just https://patchwork.freedesktop.org/series/111854/ with the
>> two controversial patches dropped for now.
>>
>> BR,
>> Jani.
>>
>> Jani Nikula (5):
>> drm/i915/irq: split out vblank/scanline code to intel_vblank.[ch]
>> drm/i915/display: move more scanline functions to intel_vblank.[ch]
>> drm/i915/display: use common function for checking scanline is moving
>> drm/i915/vblank: use intel_de_read()
>> drm/i915/vblank: add and use intel_de_read64_2x32() to read vblank
>> counter
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks, pushed to din.
BR,
Jani.
>
>>
>> drivers/gpu/drm/i915/Makefile | 1 +
>> drivers/gpu/drm/i915/display/intel_crtc.c | 1 +
>> drivers/gpu/drm/i915/display/intel_de.h | 7 +
>> drivers/gpu/drm/i915/display/intel_display.c | 54 +--
>> .../drm/i915/display/intel_display_trace.h | 1 +
>> drivers/gpu/drm/i915/display/intel_vblank.c | 441 ++++++++++++++++++
>> drivers/gpu/drm/i915/display/intel_vblank.h | 23 +
>> drivers/gpu/drm/i915/i915_irq.c | 408 ----------------
>> drivers/gpu/drm/i915/i915_irq.h | 6 -
>> 9 files changed, 476 insertions(+), 466 deletions(-)
>> create mode 100644 drivers/gpu/drm/i915/display/intel_vblank.c
>> create mode 100644 drivers/gpu/drm/i915/display/intel_vblank.h
>>
>> --
>> 2.34.1
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-01-18 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 12:56 [Intel-gfx] [PATCH v2 0/5] drm/i915: extract vblank/scanline code to a separate file Jani Nikula
2023-01-16 12:56 ` [Intel-gfx] [PATCH v2 1/5] drm/i915/irq: split out vblank/scanline code to intel_vblank.[ch] Jani Nikula
2023-01-16 12:56 ` [Intel-gfx] [PATCH v2 2/5] drm/i915/display: move more scanline functions " Jani Nikula
2023-01-16 12:56 ` [Intel-gfx] [PATCH v2 3/5] drm/i915/display: use common function for checking scanline is moving Jani Nikula
2023-01-16 12:56 ` [Intel-gfx] [PATCH v2 4/5] drm/i915/vblank: use intel_de_read() Jani Nikula
2023-01-16 12:56 ` [Intel-gfx] [PATCH v2 5/5] drm/i915/vblank: add and use intel_de_read64_2x32() to read vblank counter Jani Nikula
2023-01-16 13:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: extract vblank/scanline code to a separate file (rev2) Patchwork
2023-01-16 14:17 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-16 16:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: extract vblank/scanline code to a separate file (rev3) Patchwork
2023-01-16 17:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-16 18:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-18 9:04 ` Jani Nikula
2023-01-17 17:34 ` [Intel-gfx] [PATCH v2 0/5] drm/i915: extract vblank/scanline code to a separate file Ville Syrjälä
2023-01-18 9:27 ` Jani Nikula [this message]
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=871qnsdwgq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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