From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/7] drm/i915/pcode: Init pcode on different gt's
Date: Wed, 18 May 2022 17:03:53 +0100 [thread overview]
Message-ID: <acf55efc-a4f4-47b8-fd5a-84dd563df7c2@linux.intel.com> (raw)
In-Reply-To: <99f86f6e0c520a571f4dd4ab8a7b6dfdbb50bad3.1652405421.git.ashutosh.dixit@intel.com>
On 13/05/2022 02:36, Ashutosh Dixit wrote:
> Extend pcode initialization to pcode on different gt's.
>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> drivers/gpu/drm/i915/i915_driver.c | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index 0e9763868d68..e137bcf021ee 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -520,6 +520,22 @@ static int i915_set_dma_info(struct drm_i915_private *i915)
> return ret;
> }
>
> +static int i915_pcode_init(struct drm_i915_private *i915)
> +{
> + struct intel_gt *gt;
> + int id, ret;
> +
> + for_each_gt(gt, i915, id) {
> + ret = intel_pcode_init(gt->uncore);
> + if (ret) {
> + drm_err(>->i915->drm, "gt%d: intel_pcode_init failed %d\n", id, ret);
> + return ret;
> + }
> + }
> +
> + return 0;
> +}
> +
> /**
> * i915_driver_hw_probe - setup state requiring device access
> * @dev_priv: device private
> @@ -629,7 +645,7 @@ static int i915_driver_hw_probe(struct drm_i915_private *dev_priv)
>
> intel_opregion_setup(dev_priv);
>
> - ret = intel_pcode_init(&dev_priv->uncore);
> + ret = i915_pcode_init(dev_priv);
> if (ret)
> goto err_msi;
>
> @@ -1251,7 +1267,7 @@ static int i915_drm_resume(struct drm_device *dev)
>
> disable_rpm_wakeref_asserts(&dev_priv->runtime_pm);
>
> - ret = intel_pcode_init(&dev_priv->uncore);
> + ret = i915_pcode_init(dev_priv);
> if (ret)
> return ret;
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
next prev parent reply other threads:[~2022-05-18 16:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 1:36 [Intel-gfx] [PATCH v6 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 1/7] drm/i915: Introduce has_media_ratio_mode Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 2/7] drm/i915/gt: Add media freq factor to per-gt sysfs Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 3/7] drm/i915/pcode: Extend pcode functions for multiple gt's Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 4/7] drm/i915/pcode: Init pcode on different gt's Ashutosh Dixit
2022-05-18 16:03 ` Tvrtko Ursulin [this message]
2022-05-13 1:36 ` [Intel-gfx] [PATCH 5/7] drm/i915/pcode: Add a couple of pcode helpers Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 6/7] drm/i915/gt: Add media RP0/RPn to per-gt sysfs Ashutosh Dixit
2022-05-13 1:36 ` [Intel-gfx] [PATCH 7/7] drm/i915/gt: Fix memory leaks in " Ashutosh Dixit
2022-05-13 4:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Media freq factor and per-gt enhancements/fixes (rev6) Patchwork
2022-05-13 4:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-13 6:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-13 7:18 ` Dixit, Ashutosh
2022-05-13 17:14 ` Vudum, Lakshminarayana
2022-05-13 16:06 ` Patchwork
2022-05-13 16:59 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-05-23 8:57 ` [Intel-gfx] [PATCH v6 0/7] drm/i915: Media freq factor and per-gt enhancements/fixes Tvrtko Ursulin
2022-05-25 8:21 ` Dixit, Ashutosh
2022-05-26 8:12 ` Dixit, Ashutosh
2022-05-26 8:39 ` Tvrtko Ursulin
-- strict thread matches above, loose matches on Subject: below --
2022-05-12 2:32 [Intel-gfx] [PATCH v5 " Ashutosh Dixit
2022-05-12 2:32 ` [Intel-gfx] [PATCH 4/7] drm/i915/pcode: Init pcode on different gt's Ashutosh Dixit
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=acf55efc-a4f4-47b8-fd5a-84dd563df7c2@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=ashutosh.dixit@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