From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
luciano.coelho@intel.com
Subject: Re: [Intel-gfx] [PATCH v6 0/3] drm/i915: implement internal workqueues
Date: Sat, 10 Jun 2023 09:58:34 +0300 [thread overview]
Message-ID: <87352zreg5.fsf@intel.com> (raw)
In-Reply-To: <cover.1686231190.git.jani.nikula@intel.com>
On Thu, 08 Jun 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> This is v6 of [1], creating i915->unordered_wq also for mock devices.
Pushed to drm-intel-next. Thanks for the patches and review.
This also superseeds [1], and finally removes the last user of
flush_scheduled_work().
Tetsuo, this will make its way to v6.5. Apologies about all the
procrastination and delay.
BR,
Jani.
[1] https://patchwork.freedesktop.org/patch/msgid/47c5fe59-faec-8eb6-7f3c-f76a4bb0f3cb@I-love.SAKURA.ne.jp
>
> BR,
> Jani.
>
> [1] https://patchwork.freedesktop.org/series/118947/
>
>
> Luca Coelho (3):
> drm/i915: use pointer to i915 instead of rpm in wakeref
> drm/i915: add a dedicated workqueue inside drm_i915_private
> drm/i915/selftests: add local workqueue for SW fence selftest
>
> drivers/gpu/drm/i915/display/intel_display.c | 5 ++--
> .../drm/i915/display/intel_display_driver.c | 2 +-
> drivers/gpu/drm/i915/display/intel_dmc.c | 2 +-
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> .../drm/i915/display/intel_dp_link_training.c | 3 ++-
> drivers/gpu/drm/i915/display/intel_drrs.c | 4 +++-
> drivers/gpu/drm/i915/display/intel_fbc.c | 2 +-
> drivers/gpu/drm/i915/display/intel_fbdev.c | 3 ++-
> drivers/gpu/drm/i915/display/intel_hdcp.c | 23 +++++++++++--------
> drivers/gpu/drm/i915/display/intel_hotplug.c | 18 ++++++++++-----
> drivers/gpu/drm/i915/display/intel_opregion.c | 3 ++-
> drivers/gpu/drm/i915/display/intel_pps.c | 4 +++-
> drivers/gpu/drm/i915/display/intel_psr.c | 8 ++++---
> drivers/gpu/drm/i915/gt/intel_engine_pm.c | 4 +---
> .../drm/i915/gt/intel_execlists_submission.c | 5 ++--
> .../gpu/drm/i915/gt/intel_gt_buffer_pool.c | 10 ++++----
> drivers/gpu/drm/i915/gt/intel_gt_irq.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_gt_pm.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_gt_requests.c | 10 ++++----
> drivers/gpu/drm/i915/gt/intel_reset.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_rps.c | 20 ++++++++--------
> drivers/gpu/drm/i915/gt/selftest_engine_cs.c | 2 +-
> drivers/gpu/drm/i915/i915_driver.c | 13 +++++++++++
> drivers/gpu/drm/i915/i915_drv.h | 10 ++++++++
> drivers/gpu/drm/i915/i915_request.c | 2 +-
> drivers/gpu/drm/i915/intel_runtime_pm.c | 2 +-
> drivers/gpu/drm/i915/intel_wakeref.c | 22 ++++++++++--------
> drivers/gpu/drm/i915/intel_wakeref.h | 12 +++++-----
> .../gpu/drm/i915/selftests/i915_sw_fence.c | 16 ++++++++++---
> .../gpu/drm/i915/selftests/mock_gem_device.c | 7 ++++++
> 30 files changed, 143 insertions(+), 77 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-06-10 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:35 [Intel-gfx] [PATCH v6 0/3] drm/i915: implement internal workqueues Jani Nikula
2023-06-08 13:35 ` [Intel-gfx] [PATCH v6 1/3] drm/i915: use pointer to i915 instead of rpm in wakeref Jani Nikula
2023-06-08 13:35 ` [Intel-gfx] [PATCH v6 2/3] drm/i915: add a dedicated workqueue inside drm_i915_private Jani Nikula
2023-06-08 14:17 ` Tvrtko Ursulin
2023-06-08 14:17 ` Tetsuo Handa
2023-06-08 13:35 ` [Intel-gfx] [PATCH v6 3/3] drm/i915/selftests: add local workqueue for SW fence selftest Jani Nikula
2023-06-08 13:54 ` Tetsuo Handa
2023-06-08 17:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: implement internal workqueues (rev4) Patchwork
2023-06-08 17:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-08 18:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-09 23:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-10 6:58 ` 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=87352zreg5.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luciano.coelho@intel.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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.