From: Jani Nikula <jani.nikula@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 0/7] drm/i915: extract vblank/scanline code to a separate file
Date: Wed, 14 Dec 2022 11:18:58 +0200 [thread overview]
Message-ID: <87h6xywdfh.fsf@intel.com> (raw)
In-Reply-To: <BL0PR11MB3170BFC8724349A4AD8776CCBAE09@BL0PR11MB3170.namprd11.prod.outlook.com>
On Wed, 14 Dec 2022, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Monday, December 12, 2022 7:59 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [Intel-gfx] [PATCH 0/7] drm/i915: extract vblank/scanline code to a
>> separate file
>>
>> Add new intel_vblank.[ch] and dump a bunch of the vblank/scanline code
>> there.
>>
>> Jani Nikula (7):
>> drm/i915/irq: split out vblank/scanline code to intel_vblank.[ch]
> Can the function naming convention such as i915_get_vblank_counter be
> changed to intel_get_vblank_counter in the same series?
In this case i915_ is a platform prefix, contrast with
g4x_get_vblank_counter().
There's more naming to be sorted out, and I wanted to see what the
response was to this split with the scanline functions being included
here before embarking on doing a bunch of tedious renames.
BR,
Jani.
>
> Thanks and Regards,
> Arun R Murthy
> --------------------
>
>> drm/i915/display: move more scanline functions to intel_vblank.[ch]
>> drm/i915/display: use common function for checking scanline is moving
>> drm/i915/hdmi: abstract scanline range wait into intel_vblank.[ch]
>> drm/i915/vblank: use intel_de_read()
>> drm/i915/vblank: add and use intel_de_read64_2x32() to read vblank
>> counter
>> drm/i915/reg: split out vblank/scanline regs
>>
>> drivers/gpu/drm/i915/Makefile | 1 +
>> drivers/gpu/drm/i915/display/intel_crt.c | 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_hdmi.c | 9 +-
>> drivers/gpu/drm/i915/display/intel_vblank.c | 456 ++++++++++++++++++
>> drivers/gpu/drm/i915/display/intel_vblank.h | 24 +
>> .../gpu/drm/i915/display/intel_vblank_regs.h | 42 ++
>> drivers/gpu/drm/i915/gvt/cmd_parser.c | 1 +
>> drivers/gpu/drm/i915/gvt/display.c | 1 +
>> drivers/gpu/drm/i915/gvt/handlers.c | 1 +
>> drivers/gpu/drm/i915/i915_irq.c | 408 ----------------
>> drivers/gpu/drm/i915/i915_irq.h | 6 -
>> drivers/gpu/drm/i915/i915_reg.h | 35 --
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 1 +
>> 17 files changed, 541 insertions(+), 508 deletions(-) create mode 100644
>> drivers/gpu/drm/i915/display/intel_vblank.c
>> create mode 100644 drivers/gpu/drm/i915/display/intel_vblank.h
>> create mode 100644 drivers/gpu/drm/i915/display/intel_vblank_regs.h
>>
>> --
>> 2.34.1
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-12-14 9:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 14:29 [Intel-gfx] [PATCH 0/7] drm/i915: extract vblank/scanline code to a separate file Jani Nikula
2022-12-12 14:29 ` [Intel-gfx] [PATCH 1/7] drm/i915/irq: split out vblank/scanline code to intel_vblank.[ch] Jani Nikula
2022-12-12 14:29 ` [Intel-gfx] [PATCH 2/7] drm/i915/display: move more scanline functions " Jani Nikula
2022-12-14 4:15 ` Murthy, Arun R
2022-12-14 9:15 ` Jani Nikula
2022-12-15 2:11 ` Murthy, Arun R
2022-12-15 9:12 ` Jani Nikula
2022-12-15 9:59 ` Murthy, Arun R
2022-12-15 10:20 ` Jani Nikula
2022-12-15 10:39 ` Murthy, Arun R
2022-12-15 11:03 ` Jani Nikula
2022-12-12 14:29 ` [Intel-gfx] [PATCH 3/7] drm/i915/display: use common function for checking scanline is moving Jani Nikula
2022-12-14 4:01 ` Murthy, Arun R
2022-12-12 14:29 ` [Intel-gfx] [PATCH 4/7] drm/i915/hdmi: abstract scanline range wait into intel_vblank.[ch] Jani Nikula
2022-12-14 4:17 ` Murthy, Arun R
2022-12-14 14:16 ` Ville Syrjälä
2022-12-12 14:29 ` [Intel-gfx] [PATCH 5/7] drm/i915/vblank: use intel_de_read() Jani Nikula
2022-12-14 4:05 ` Murthy, Arun R
2022-12-12 14:29 ` [Intel-gfx] [PATCH 6/7] drm/i915/vblank: add and use intel_de_read64_2x32() to read vblank counter Jani Nikula
2022-12-12 14:29 ` [Intel-gfx] [PATCH 7/7] drm/i915/reg: split out vblank/scanline regs Jani Nikula
2022-12-14 4:24 ` Murthy, Arun R
2022-12-14 13:42 ` Ville Syrjälä
2022-12-12 14:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: extract vblank/scanline code to a separate file Patchwork
2022-12-12 14:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-12-12 15:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-14 4:12 ` [Intel-gfx] [PATCH 0/7] " Murthy, Arun R
2022-12-14 9:18 ` Jani Nikula [this message]
2022-12-15 2:05 ` Murthy, Arun R
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=87h6xywdfh.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@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 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.