All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: Huang Rui <ray.huang-5C7GfCeVMHo@public.gmane.org>
Cc: "Deucher,
	Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
	"Huan, Alvin" <Alvin.Huan-5C7GfCeVMHo@public.gmane.org>,
	"Wang, Ken" <Ken.Wang-5C7GfCeVMHo@public.gmane.org>,
	"Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 1/2] drm/amdgpu: fix re-program vm invalidate eng address range for gfxhub on resume
Date: Wed, 17 May 2017 16:11:33 +0800	[thread overview]
Message-ID: <591C05B5.4090902@amd.com> (raw)
In-Reply-To: <20170517075557.GA31947@hr-amur2>



On 2017年05月17日 15:55, Huang Rui wrote:
> On Wed, May 17, 2017 at 03:43:47PM +0800, Zhou, David(ChunMing) wrote:
>> By this change, I suggest to remove mmhub/gfxhub_v1_0_ip_funcs and their
>> IP block, unify them to gmc ip block, this way we cannot lost setting
>> when resume back.
>>
>  From hw side, wo won't have real gmc since this chip, mmhub and gfxhub(gc)
> instead of it. Maybe we would better to align with hw desgin.
I don't see any advance, as you said, we still have gmc block in soc15, 
why not unify mmhub/gfxhub calls to gmc block?
We can keep mmhub/gfxhub_xxx.c file, but ip_funciton isn't necessary.

Regards,
David Zhou
>
> Thanks,
> Rui
>
>> Regards,
>> David Zhou
>>
>> On 2017年05月17日 15:38, Huang Rui wrote:
>>> Signed-off-by: Huang Rui <ray.huang@amd.com>
>>> ---
>>>    drivers/gpu/drm/amd/amdgpu/gfxhub_v1_0.c | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/gfxhub_v1_0.c b/drivers/gpu/drm/amd/
>> amdgpu/gfxhub_v1_0.c
>>> index 005075f..41313514 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/gfxhub_v1_0.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/gfxhub_v1_0.c
>>> @@ -368,7 +368,7 @@ static int gfxhub_v1_0_suspend(void *handle)
>>>   
>>>    static int gfxhub_v1_0_resume(void *handle)
>>>    {
>>> -     return 0;
>>> +     return gfxhub_v1_0_hw_init(handle);
>>>    }
>>>   
>>>    static bool gfxhub_v1_0_is_idle(void *handle)
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx

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

  reply	other threads:[~2017-05-17  8:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  7:38 [PATCH 1/2] drm/amdgpu: fix re-program vm invalidate eng address range for gfxhub on resume Huang Rui
     [not found] ` <1495006729-17310-1-git-send-email-ray.huang-5C7GfCeVMHo@public.gmane.org>
2017-05-17  7:38   ` [PATCH 2/2] drm/amdgpu: fix re-program vm invalidate eng address range for mmhub " Huang Rui
     [not found]     ` <1495006729-17310-2-git-send-email-ray.huang-5C7GfCeVMHo@public.gmane.org>
2017-05-17  8:01       ` Wang, Ken
2017-05-17  7:43   ` [PATCH 1/2] drm/amdgpu: fix re-program vm invalidate eng address range for gfxhub " zhoucm1
     [not found]     ` <591BFF33.2010303-5C7GfCeVMHo@public.gmane.org>
2017-05-17  7:55       ` Huang Rui
2017-05-17  8:11         ` zhoucm1 [this message]
     [not found]           ` <591C05B5.4090902-5C7GfCeVMHo@public.gmane.org>
2017-05-17  8:19             ` zhoucm1
2017-05-17  8:19             ` Christian König
     [not found]               ` <806d8b04-e983-ee6b-234f-9cd9fde4a3f5-5C7GfCeVMHo@public.gmane.org>
2017-05-17  8:22                 ` zhoucm1
     [not found]                   ` <591C083E.9020801-5C7GfCeVMHo@public.gmane.org>
2017-05-17  8:42                     ` Christian König
2017-05-17  8:16         ` Christian König
     [not found]           ` <73fa42d9-1994-83ed-db9f-7c601f8a4598-5C7GfCeVMHo@public.gmane.org>
2017-05-17  8:33             ` Huang Rui

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=591C05B5.4090902@amd.com \
    --to=david1.zhou-5c7gfcevmho@public.gmane.org \
    --cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=Alvin.Huan-5C7GfCeVMHo@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=Ken.Wang-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=ray.huang-5C7GfCeVMHo@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 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.