From: Jani Nikula <jani.nikula@intel.com>
To: Imre Deak <imre.deak@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 0/4] drm/i915/tgl+: Fix race conditions during DKL PHY accesses
Date: Fri, 21 Oct 2022 11:26:00 +0300 [thread overview]
Message-ID: <87y1t9fuqv.fsf@intel.com> (raw)
In-Reply-To: <20221020160022.1823365-1-imre.deak@intel.com>
On Thu, 20 Oct 2022, Imre Deak <imre.deak@intel.com> wrote:
> This is v2 of [1] addressing the review comments from Jani.
Did not do detailed review,
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> [1] https://lore.kernel.org/intel-gfx/Y1BaRfTAH%2Fl+XLqc@ideak-desk.fi.intel.com/T/#t
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Imre Deak (4):
> drm/i915/tgl+: Add locking around DKL PHY register accesses
> drm/i915: Rename intel_tc_phy_regs.h to intel_mg_phy_regs.h
> drm/i915/tgl+: Move DKL PHY register definitions to
> intel_dkl_phy_regs.h
> drm/i915/tgl+: Sanitize DKL PHY register definitions
>
> drivers/gpu/drm/i915/Makefile | 1 +
> drivers/gpu/drm/i915/display/intel_ddi.c | 71 +++---
> .../gpu/drm/i915/display/intel_display_core.h | 4 +
> .../i915/display/intel_display_power_well.c | 8 +-
> drivers/gpu/drm/i915/display/intel_dkl_phy.c | 101 +++++++++
> drivers/gpu/drm/i915/display/intel_dkl_phy.h | 20 ++
> .../gpu/drm/i915/display/intel_dkl_phy_regs.h | 202 ++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 62 +++---
> ...ntel_tc_phy_regs.h => intel_mg_phy_regs.h} | 6 +-
> drivers/gpu/drm/i915/display/intel_tc.c | 3 +-
> drivers/gpu/drm/i915/i915_driver.c | 1 +
> drivers/gpu/drm/i915/i915_reg.h | 176 ---------------
> 12 files changed, 397 insertions(+), 258 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/display/intel_dkl_phy.c
> create mode 100644 drivers/gpu/drm/i915/display/intel_dkl_phy.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_dkl_phy_regs.h
> rename drivers/gpu/drm/i915/display/{intel_tc_phy_regs.h => intel_mg_phy_regs.h} (99%)
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-10-21 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:00 [Intel-gfx] [PATCH v2 0/4] drm/i915/tgl+: Fix race conditions during DKL PHY accesses Imre Deak
2022-10-20 16:00 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/tgl+: Add locking around DKL PHY register accesses Imre Deak
2022-10-20 16:00 ` [Intel-gfx] [PATCH v2 2/4] drm/i915: Rename intel_tc_phy_regs.h to intel_mg_phy_regs.h Imre Deak
2022-10-20 16:00 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/tgl+: Move DKL PHY register definitions to intel_dkl_phy_regs.h Imre Deak
2022-10-20 16:00 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/tgl+: Sanitize DKL PHY register definitions Imre Deak
2022-10-20 17:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/tgl+: Fix race conditions during DKL PHY accesses Patchwork
2022-10-20 17:48 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-20 18:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-20 23:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-21 8:26 ` 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=87y1t9fuqv.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox