AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Trigger Huang <Trigger.Huang-5C7GfCeVMHo@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: Trigger.Huang-5C7GfCeVMHo@public.gmane.org
Subject: [PATCH 1/2] drm/amdgpu: Skip IH reroute in Vega10 SR-IOV VF
Date: Tue, 7 May 2019 12:08:34 +0800	[thread overview]
Message-ID: <1557202115-24444-2-git-send-email-Trigger.Huang@amd.com> (raw)
In-Reply-To: <1557202115-24444-1-git-send-email-Trigger.Huang-5C7GfCeVMHo@public.gmane.org>

IH reroute commands are not supported on Vega10 VF

Signed-off-by: Trigger Huang <Trigger.Huang@amd.com>
---
 drivers/gpu/drm/amd/amdgpu/psp_v3_1.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/gpu/drm/amd/amdgpu/psp_v3_1.c b/drivers/gpu/drm/amd/amdgpu/psp_v3_1.c
index 143f0fa..9d6e603 100644
--- a/drivers/gpu/drm/amd/amdgpu/psp_v3_1.c
+++ b/drivers/gpu/drm/amd/amdgpu/psp_v3_1.c
@@ -260,6 +260,10 @@ static void psp_v3_1_reroute_ih(struct psp_context *psp)
 	struct amdgpu_device *adev = psp->adev;
 	uint32_t tmp;
 
+	/* reroute_ih is not supported on SR_IOV VF */
+	if (amdgpu_sriov_vf(adev))
+		return;
+
 	/* Change IH ring for VMC */
 	tmp = REG_SET_FIELD(0, IH_CLIENT_CFG_DATA, CREDIT_RETURN_ADDR, 0x1244b);
 	tmp = REG_SET_FIELD(tmp, IH_CLIENT_CFG_DATA, CLIENT_TYPE, 1);
-- 
2.7.4

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2019-05-07  4:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  4:08 [PATCH 0/2] Skip IH re-route on Vega SR-IOV Trigger Huang
     [not found] ` <1557202115-24444-1-git-send-email-Trigger.Huang-5C7GfCeVMHo@public.gmane.org>
2019-05-07  4:08   ` Trigger Huang [this message]
2019-05-07  4:08   ` [PATCH 2/2] drm/amdgpu: Skip IH reroute in Vega20 SR-IOV VF Trigger Huang
2019-05-07  7:36   ` [PATCH 0/2] Skip IH re-route on Vega SR-IOV Christian König
     [not found]     ` <1b5b40b0-0d3c-8374-f423-5c50617fca9a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-07  8:54       ` Huang, Trigger
     [not found]         ` <MN2PR12MB34084FE909CDC9AF45A6D624FE310-rweVpJHSKTo4ZTiO+qW6TgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-05-07  9:04           ` Christian König
     [not found]             ` <3bc56691-9d61-8709-31a4-6ee98b79b397-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-07  9:16               ` Huang, Trigger

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=1557202115-24444-2-git-send-email-Trigger.Huang@amd.com \
    --to=trigger.huang-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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