From: Jason Gunthorpe <jgg@nvidia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <jroedel@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Robin Murphy <robin.murphy@arm.com>,
Eric Auger <eric.auger@redhat.com>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19
Date: Tue, 6 Sep 2022 12:41:51 -0300 [thread overview]
Message-ID: <YxdqP9i0bEwUg4VJ@nvidia.com> (raw)
In-Reply-To: <20220823202824.GA4516@nvidia.com>
On Tue, Aug 23, 2022 at 05:28:24PM -0300, Jason Gunthorpe wrote:
> On Tue, Aug 23, 2022 at 01:46:36PM +0200, Takashi Iwai wrote:
> > It was tested now and confirmed that the call path is via AMDGPU, as
> > expected:
> > amdgpu_pci_probe ->
> > amdgpu_driver_load_kms ->
> > amdgpu_device_init ->
> > amdgpu_amdkfd_device_init ->
> > kgd2kfd_device_init ->
> > kgd2kfd_resume_iommu ->
> > kfd_iommu_resume ->
> > amd_iommu_init_device ->
> > iommu_attach_group ->
> > __iommu_attach_group
>
> Oh, when you said sound intel I thought this was an Intel CPU..
>
> Yes, there is this hacky private path from the amdgpu to
> the amd iommu driver that makes a mess of it here. We discussed it in
> this thread:
>
> https://lore.kernel.org/linux-iommu/YgtuJQhY8SNlv9%2F6@8bytes.org/
>
> But nobody put it together that it would be a problem with this.
>
> Something like this, perhaps, but I didn't check if overriding the
> type would cause other problems.
Takashi, do we want to do this patch?
Thanks,
Jason
next prev parent reply other threads:[~2022-09-06 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 14:12 [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 Takashi Iwai
2022-08-23 1:00 ` Jason Gunthorpe
2022-08-23 6:06 ` Takashi Iwai
2022-08-23 11:46 ` Takashi Iwai
2022-08-23 20:28 ` Jason Gunthorpe
2022-08-23 21:01 ` Robin Murphy
2022-08-24 0:02 ` Jason Gunthorpe
2022-09-06 15:41 ` Jason Gunthorpe [this message]
2022-09-06 15:52 ` Takashi Iwai
2022-09-06 15:53 ` Jason Gunthorpe
2022-09-06 16:04 ` Takashi Iwai
2022-09-06 16:08 ` Jason Gunthorpe
2022-09-06 16:16 ` Takashi Iwai
2022-09-07 10:08 ` Takashi Iwai
2022-09-07 13:28 ` Takashi Iwai
2022-09-07 13:48 ` Jason Gunthorpe
2022-09-08 6:23 ` Takashi Iwai
2022-08-24 7:13 ` Thorsten Leemhuis
2022-09-19 15:23 ` [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 #forregzbot Thorsten Leemhuis
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=YxdqP9i0bEwUg4VJ@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=eric.auger@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).