Reviewed-by: Lyude Paul <lyude at 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 at redhat.com>
> Cc: <stable at 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