public inbox for amd-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kuehling, Felix" <Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
To: "Deucher,
	Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
	Alex Deucher
	<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 1/2] drm/amdgpu: add some additional vega10 pci ids
Date: Fri, 7 Dec 2018 22:14:37 +0000	[thread overview]
Message-ID: <aeab7c77-79a0-cd23-3ff7-82af3eb8db4b@amd.com> (raw)
In-Reply-To: <BN6PR12MB1809D26AB85CB852B36B355CF7AA0-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

Thanks. I see you added the KFD change in a separate patch series.


This one is also Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>


On 2018-12-07 4:16 p.m., Deucher, Alexander wrote:
>
> Will do.
>
>
> Alex
>
> ------------------------------------------------------------------------
> *From:* Kuehling, Felix
> *Sent:* Friday, December 7, 2018 4:14:39 PM
> *To:* Alex Deucher; amd-gfx@lists.freedesktop.org
> *Cc:* Deucher, Alexander; stable@vger.kernel.org
> *Subject:* Re: [PATCH 1/2] drm/amdgpu: add some additional vega10 pci ids
>  
> Can you add them amdkfd/kfd_device.c as well while you're at it.
>
> Thanks,
>   Felix
>
> On 2018-12-07 4:03 p.m., Alex Deucher wrote:
> > New vega ids.
> >
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > Cc: stable@vger.kernel.org
> > ---
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > index 90f474f98b6e..e32f6f43a46b 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > @@ -873,7 +873,13 @@ static const struct pci_device_id pciidlist[] = {
> >        {0x1002, 0x6864, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> >        {0x1002, 0x6867, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> >        {0x1002, 0x6868, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x6869, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x686a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x686b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> >        {0x1002, 0x686c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x686d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x686e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> > +     {0x1002, 0x686f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> >        {0x1002, 0x687f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
> >        /* Vega 12 */
> >        {0x1002, 0x69A0, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA12},
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2018-12-07 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 21:03 [PATCH 1/2] drm/amdgpu: add some additional vega10 pci ids Alex Deucher
     [not found] ` <20181207210325.24656-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2018-12-07 21:03   ` [PATCH 2/2] drm/amdgpu: add some additional vega20 " Alex Deucher
2018-12-07 21:14 ` [PATCH 1/2] drm/amdgpu: add some additional vega10 " Kuehling, Felix
     [not found]   ` <f61b8451-51bf-cb8f-eb07-f01e3c5361ee-5C7GfCeVMHo@public.gmane.org>
2018-12-07 21:16     ` Deucher, Alexander
     [not found]       ` <BN6PR12MB1809D26AB85CB852B36B355CF7AA0-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-12-07 22:14         ` Kuehling, Felix [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=aeab7c77-79a0-cd23-3ff7-82af3eb8db4b@amd.com \
    --to=felix.kuehling-5c7gfcevmho@public.gmane.org \
    --cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@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