From: Lyude Paul <lyude@redhat.com>
To: Karol Herbst <kherbst@redhat.com>, linux-kernel@vger.kernel.org
Cc: nouveau@lists.freedesktop.org, Ben Skeggs <bskeggs@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/nouveau: recognise GA103
Date: Wed, 03 Aug 2022 14:06:49 -0400 [thread overview]
Message-ID: <4fd72edfab4cfb6e8ca9731f1087c2209299bdd2.camel@redhat.com> (raw)
In-Reply-To: <20220803142745.2679510-1-kherbst@redhat.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
On Wed, 2022-08-03 at 16:27 +0200, Karol Herbst wrote:
> Appears to be ok with general GA10x code.
>
> Signed-off-by: Karol Herbst <kherbst@redhat.com>
> Cc: <stable@vger.kernel.org> # v5.15+
> ---
> .../gpu/drm/nouveau/nvkm/engine/device/base.c | 22 +++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c
> b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c
> index 62efbd0f3846..b7246b146e51 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c
> @@ -2605,6 +2605,27 @@ nv172_chipset = {
> .fifo = { 0x00000001, ga102_fifo_new },
> };
>
> +static const struct nvkm_device_chip
> +nv173_chipset = {
> + .name = "GA103",
> + .bar = { 0x00000001, tu102_bar_new },
> + .bios = { 0x00000001, nvkm_bios_new },
> + .devinit = { 0x00000001, ga100_devinit_new },
> + .fb = { 0x00000001, ga102_fb_new },
> + .gpio = { 0x00000001, ga102_gpio_new },
> + .i2c = { 0x00000001, gm200_i2c_new },
> + .imem = { 0x00000001, nv50_instmem_new },
> + .mc = { 0x00000001, ga100_mc_new },
> + .mmu = { 0x00000001, tu102_mmu_new },
> + .pci = { 0x00000001, gp100_pci_new },
> + .privring = { 0x00000001, gm200_privring_new },
> + .timer = { 0x00000001, gk20a_timer_new },
> + .top = { 0x00000001, ga100_top_new },
> + .disp = { 0x00000001, ga102_disp_new },
> + .dma = { 0x00000001, gv100_dma_new },
> + .fifo = { 0x00000001, ga102_fifo_new },
> +};
> +
> static const struct nvkm_device_chip
> nv174_chipset = {
> .name = "GA104",
> @@ -3092,6 +3113,7 @@ nvkm_device_ctor(const struct nvkm_device_func *func,
> case 0x167: device->chip = &nv167_chipset; break;
> case 0x168: device->chip = &nv168_chipset; break;
> case 0x172: device->chip = &nv172_chipset; break;
> + case 0x173: device->chip = &nv173_chipset; break;
> case 0x174: device->chip = &nv174_chipset; break;
> case 0x176: device->chip = &nv176_chipset; break;
> case 0x177: device->chip = &nv177_chipset; break;
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
prev parent reply other threads:[~2022-08-03 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 14:27 Karol Herbst
2022-08-03 18:06 ` Lyude Paul [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=4fd72edfab4cfb6e8ca9731f1087c2209299bdd2.camel@redhat.com \
--to=lyude@redhat.com \
--cc=bskeggs@redhat.com \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®