From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA0A9ECAAD5 for ; Tue, 6 Sep 2022 16:32:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234197AbiIFQcF (ORCPT ); Tue, 6 Sep 2022 12:32:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60368 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234022AbiIFQbh (ORCPT ); Tue, 6 Sep 2022 12:31:37 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84AC418C for ; Tue, 6 Sep 2022 09:04:30 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 84522336D0; Tue, 6 Sep 2022 16:04:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1662480268; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AjzLZ3rHiihQrfLWNjF73yb4DNX3TJs0K7iqQQYIzQo=; b=qYKnMbTM2t9wVFrOaIDTF/7pRF1f/JPbZAAVu8dONP4NXKb54xTxNNQ0fk7NeISe5+Da4O ItVoOUJgur+9LHy9chr3m3zjPTmh6gPqLws/dZT4MAbFCXSuAXX5+Iz1FWkuV9+8a/N7W8 y4Ypb91KWk5RhdFz2AgDdCmRXailzqM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1662480268; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AjzLZ3rHiihQrfLWNjF73yb4DNX3TJs0K7iqQQYIzQo=; b=/rXtOPbKB0N9AvfH9HkXXKgjzQsE+kCoPHdCkMRCJlmjsNbF1OEU7+U3pDk2Zx7KvhneRb rMCQxvMrSgRyU/CA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 57DFD13A19; Tue, 6 Sep 2022 16:04:28 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id hOKcFIxvF2OKLQAAMHmgww (envelope-from ); Tue, 06 Sep 2022 16:04:28 +0000 Date: Tue, 06 Sep 2022 18:04:27 +0200 Message-ID: <877d2gfq0k.wl-tiwai@suse.de> From: Takashi Iwai To: Jason Gunthorpe Cc: Takashi Iwai , Lu Baolu , Joerg Roedel , Greg Kroah-Hartman , Bjorn Helgaas , Robin Murphy , Eric Auger , regressions@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 In-Reply-To: References: <874jy4cqok.wl-tiwai@suse.de> <20220823010021.GA5967@nvidia.com> <87h723sdde.wl-tiwai@suse.de> <87ilmjqj1f.wl-tiwai@suse.de> <20220823202824.GA4516@nvidia.com> <87edwofqkd.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 06 Sep 2022 17:53:44 +0200, Jason Gunthorpe wrote: > > On Tue, Sep 06, 2022 at 05:52:34PM +0200, Takashi Iwai wrote: > > On Tue, 06 Sep 2022 17:41:51 +0200, > > Jason Gunthorpe wrote: > > > > > > 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? > > > > I really have no much preference regarding the fix for this > > regression from my side. If you can work on it, it'd be greatly > > appreciated. > > If you say this patch works I will formally propose it, but I have no > ability to test on this special AMD HW. Erm, it's not clear which patch you're referring to. The mentioned URL points to a patch series. If you can send (or point) a patch for test, I can set up a test kernel and ask reporters for testing it. thanks, Takashi