Archive-only list for patches
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
	Mikko Perttunen <mperttunen@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
	patches@lists.linux.dev
Subject: Re: [PATCH] drm/tegra: Remove of_dma_configure() from host1x_device_add()
Date: Thu, 1 Feb 2024 16:02:12 -0400	[thread overview]
Message-ID: <20240201200212.GQ1455070@nvidia.com> (raw)
In-Reply-To: <a1597113-3ec9-445c-90d1-62df97406fb2@nvidia.com>

On Thu, Feb 01, 2024 at 07:35:24PM +0000, Jon Hunter wrote:
> > You mean this sequence?
> > 
> > 		err = device_add(&ctx->dev);
> > 		if (err) {
> > 			dev_err(host1x->dev, "could not add context device %d: %d\n", i, err);
> > 			put_device(&ctx->dev);
> > 			goto unreg_devices;
> > 		}
> > 
> > 		err = of_dma_configure_id(&ctx->dev, node, true, &i);
> > 		if (err) {
> > 			dev_err(host1x->dev, "IOMMU configuration failed for context device %d: %d\n",
> > 				i, err);
> > 			device_unregister(&ctx->dev);
> > 			goto unreg_devices;
> > 		}
> 
> Yes this sequence.
> 
> > I didn't seem an obvious place that this would get fixed up later?
> > 
> > device_add() was done before so the iommu_device_link() shouldn't be
> > failing? Are you hitting a duplicate link (ie remove the nowarn from
> > iommu_device_link())
> 
> 
> Removing the '_nowarn' does appear to fix it, although it is not clear to me
> why?

What did you do to remove? Just the letters or the whole line?

I was thinking the letters because it triggers a large debug message.

But, what is the actual log output you see, is it -EEXIST?

If it is coming and going is it a race of some kind?

Jason

  reply	other threads:[~2024-02-01 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 16:15 [PATCH] drm/tegra: Remove of_dma_configure() from host1x_device_add() Jason Gunthorpe
2024-01-30 21:55 ` Jon Hunter
2024-01-31 15:33   ` Jason Gunthorpe
2024-02-01 19:35     ` Jon Hunter
2024-02-01 20:02       ` Jason Gunthorpe [this message]
2024-02-02 10:40         ` Jon Hunter
2024-02-02 14:35           ` Jason Gunthorpe
2024-02-02 15:56             ` Jon Hunter
2024-02-02 16:15               ` Jason Gunthorpe
2024-02-07 13:05                 ` Jason Gunthorpe

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=20240201200212.GQ1455070@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mperttunen@nvidia.com \
    --cc=patches@lists.linux.dev \
    --cc=thierry.reding@gmail.com \
    /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