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: Fri, 2 Feb 2024 10:35:18 -0400 [thread overview]
Message-ID: <20240202143518.GS1455070@nvidia.com> (raw)
In-Reply-To: <96bc6d37-1000-4651-9a26-a8446dd64803@nvidia.com>
On Fri, Feb 02, 2024 at 10:40:36AM +0000, Jon Hunter wrote:
> > But, what is the actual log output you see, is it -EEXIST?
>
> I see ...
>
> ERR KERN host1x drm: iommu configuration for device failed with -ENOENT
So that shouldn't happen in you case as far as I can tell, the device
is properly added, link->kobj should be fine and ENOENT shouldn't
happen.
> > If it is coming and going is it a race of some kind?
>
> It is consistent without the above. However, I did not think that the
> above change would change the returning on -ENOENT? I will add more
> debug.
I do not think it can either
Still wonder if there is some odd race..
Let me know when you figure out what is happening - I think there is
some bug here it is not just a harmless warning.
Jason
next prev parent reply other threads:[~2024-02-02 14:35 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
2024-02-02 10:40 ` Jon Hunter
2024-02-02 14:35 ` Jason Gunthorpe [this message]
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=20240202143518.GS1455070@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