[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63913cd8-a0c5-61e3-2f52-139bade01afc@amd.com>
Date: Fri, 27 Sep 2019 10:30:16 +0000
From: "Shah, Nehal-bakulchandra" <nbshah@....com>
To: Kurt Garloff <kurt@...loff.de>, Joerg Roedel <joro@...tes.org>,
Jiri Kosina <jikos@...nel.org>
CC: 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
Hi Kurf
On 9/27/2019 3:17 PM, Kurt Garloff wrote:
> Hi Jörg,
>
> On 25/09/2019 17:42, Joerg Roedel wrote:
>> On Wed, Sep 25, 2019 at 05:27:32PM +0200, Jiri
>> Kosina wrote:
>>> On Sat, 21 Sep 2019, Kurt Garloff wrote:
>>>> [12916.740274] mmc0: sdhci:
>>>> ============================================
>>>> [12916.740337] mmc0: error -5 whilst
>>>> initialising MMC card
>>> 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.
Thanks
Nehal Shah
Powered by blists - more mailing lists