On Thu, May 25, 2023 at 2:31 AM Ben Skeggs <skeg...@gmail.com> wrote:
>
> From: Ben Skeggs <bske...@redhat.com>
>
> This can be completely normal in some situations (ie. non-stall intrs
> when nothing is waiting on them).
>
> Signed-off-by: Ben Skeggs <bske...@redhat.com>
> ---
>  drivers/gpu/drm/nouveau/nvkm/core/intr.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nvkm/core/intr.c 
> b/drivers/gpu/drm/nouveau/nvkm/core/intr.c
> index e20b7ca218c3..36a747f0039e 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/core/intr.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/core/intr.c
> @@ -212,8 +212,8 @@ nvkm_intr(int irq, void *arg)
>                 list_for_each_entry(intr, &device->intr.intr, head) {
>                         for (leaf = 0; leaf < intr->leaves; leaf++) {
>                                 if (intr->stat[leaf]) {
> -                                       nvkm_warn(intr->subdev, "intr%d: 
> %08x\n",
> -                                                 leaf, intr->stat[leaf]);
> +                                       nvkm_debug(intr->subdev, "intr%d: 
> %08x\n",
> +                                                  leaf, intr->stat[leaf]);
>                                         nvkm_intr_block_locked(intr, leaf, 
> intr->stat[leaf]);
>                                 }
>                         }
> --
> 2.40.1
>

Reviewed-by: Karol Herbst <kher...@redhat.com>

Reply via email to