[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1910092124260.13160@cbobk.fhfr.pm>
Date: Wed, 9 Oct 2019 21:25:00 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: "Shah, Nehal-bakulchandra" <nbshah@....com>
cc: Kurt Garloff <kurt@...loff.de>, Joerg Roedel <joro@...tes.org>,
LKML <linux-kernel@...r.kernel.org>,
"Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@....com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
"Singh, Sandeep" <Sandeep.Singh@....com>
Subject: Re: IOMMU vs Ryzen embedded EMMC controller
On Fri, 27 Sep 2019, Shah, Nehal-bakulchandra wrote:
> >>> Do you have BAR memory allocation failures in dmesg with IOMMU on?
> >
> > No. The device is *not* treated as PCI device and I still think that
> > this is the source of the evil.
> >
> >>> Actually, sharing both working and non-working dmesg, as well as
> >>> /proc/iomem contents, would be helpful.
> >> Yes, can you please grab dmesg from a boot with iommu enabled and add
> >> 'amd_iommu_dump' to the kernel command line? That should give some
> >> hints on what is going on.
> >
> > For now I attach a dmesg and iomem from the boot with IOMMU enabled.
> > Nothing much interesting without IOMMU, sdhci-acpi there just works --
> > let me know if you still want me to send the kernel msg.
> >
> > Thanks for looking into this!
> >
>
> I have added Suravee from AMD in the mail loop. He works on IOMMU part.
> As per my understanding, it needs a patch in IOMMU driver for adding
> support of EMMC. Note that on Ryzen platform we have EMMC 5.0 as ACPI
> device.
Friendly ping ... any news here?
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists