My static checker complains that "dma_alias" is uninitialized unless we
are dealing with a pci device. This is true but harmless. Anyway, we
can flip the condition around to silence the warning.
Signed-off-by: Dan Carpenter
diff --git a/drivers/iommu/intel-iommu.c
Joerg Roedel wrote:
> Maybe I can get one of those cards myself to reproduce it. Can you guys
> send me some more detailed information about the sound cards that cause
> the problems?
Most of the PCIe Xonar cards use the same architecture: a PCI chip and
a PCIe/PCI bridge. Consider the Asus
On Mon, 4 Apr 2016 08:30:11 +
Eric Auger wrote:
> This patch allows the user-space to know whether MSI addresses need to
> be mapped in the IOMMU. The user-space uses VFIO_IOMMU_GET_INFO ioctl and
> IOMMU_INFO_REQUIRE_MSI_MAP gets set if they need to.
>
> Also the
Hi Mitch,
On 05/04/16 22:01, Mitchel Humpherys wrote:
Currently we use a single pgsize_bitmap per IOMMU driver. However, some
IOMMU drivers might service different IOMMUs with different supported
page sizes. Some drivers might also want to restrict page sizes for
different use cases. Support
On Mon, 4 Apr 2016 08:07:01 +
Eric Auger wrote:
> This patch introduces iommu_get/put_single_reserved.
>
> iommu_get_single_reserved allows to allocate a new reserved iova page
> and map it onto the physical page that contains a given physical address.
> Page size is
On Mon, 4 Apr 2016 08:06:55 +
Eric Auger wrote:
> This series introduces the dma-reserved-iommu api used to:
> - create/destroy an iova domain dedicated to reserved iova bindings
> - map/unmap physical addresses onto reserved IOVAs.
> - unmap and destroy all IOVA
On Mon, 4 Apr 2016 08:06:59 +
Eric Auger wrote:
> Introduce alloc/free_reserved_iova_domain in the IOMMU API.
> alloc_reserved_iova_domain initializes an iova domain at a given
> iova base address and with a given size. This iova domain will
> be used to allocate iova
Le mercredi 06 avril 2016 à 17:47 +0200, Joerg Roedel a écrit :
> Vendor and exact product name would be helpful.
I use the Asus Essence STX II (the one withOUT the additional 7.1
surround card):
http://www.asus.com/Sound-Cards/Essence_STX_II/
I use it in its original configuration, without
> > > Martin/Tomasz, could we get the amd_iommu_dump dmesg output for
> > > an earlier kernel?
Sorry, I don't have access to that system at the moment and supply the
info as early as I get back home in 10 days. Please keep me in cc.
As for the other questions:
- no proprietary drivers
> -Original Message-
> From: Ulf Hansson [mailto:ulf.hans...@linaro.org]
> Sent: Tuesday, April 05, 2016 7:28 PM
> To: Yangbo Lu
> Cc: devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> linux-ker...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
>
On 5 April 2016 at 21:10, Heiko Stuebner wrote:
> Am Dienstag, 5. April 2016, 18:28:58 schrieb John Keeping:
>> On Tue, 05 Apr 2016 10:21:27 -0700, Heiko Stuebner wrote:
>> > Am Dienstag, 5. April 2016, 15:05:46 schrieb John Keeping:
>> > > Since commit cd6438c5f844
>>
>> I was about to queue this for next, when I noticed that checkpatch is
>> complaining/warning lots about these patches. Can you please a round of
>> checkpatch and fix what makes sense.
>>
>> Kind regards
>> Uffe
>
> [Lu Yangbo-B47093] Sorry about this, Uffe...
No worries!
> Should I ignore
Hi Robin,
On 04/05/2016 01:39 PM, Robin Murphy wrote:
> Teach the LPAE format to create Device mappings when asked.
>
> Signed-off-by: Robin Murphy
don't know if it helps in any way but I tested that with my KVM PCIe/MSI
passthrough series for mapping the GICv2m doorbell.
> Can you guys send me some more detailed information about
> the sound cards that cause the problems? Vendor and exact product name
> would be helpful.
I'm using Asus Xonar DX card: https://www.asus.com/Sound-Cards/Xonar_DX/
Let me add that I also did no BIOS upgrade in the meantime and I use
This iommu uses the armv7 short descriptor format. So use the
generic ARMV7S pagetable ops instead of rewriting the same stuff
in the driver.
Signed-off-by: Sricharan R
---
drivers/iommu/Kconfig | 1 +
drivers/iommu/msm_iommu.c | 378
There are only two functions left in msm_iommu_dev.c. Move it to
msm_iommu.c and delete the file.
Signed-off-by: Sricharan R
---
drivers/iommu/Makefile| 2 +-
drivers/iommu/msm_iommu.c | 182
The msm_iommu.c driver currently works based on platform data.
A single master device can be connected to more than one iommu
and multiple contexts in each of the iommu. This association
between master and iommus was represented from platform data
using parent/child devices. The master drivers
Now that the driver is DT adapted, bus_set_iommu gets called only
when on compatible matching. So the driver should not break multiplatform
builds now. So remove the BROKEN config.
Signed-off-by: Sricharan R
---
drivers/iommu/Kconfig | 1 -
1 file changed, 1
The driver currently works based on platform data. Remove this
and add support for DT. A single master can have multiple ports
connected to more than one iommu.
master
|
|
|
On Wed, Apr 06, 2016 at 09:06:31AM +0200, Martin Haiden wrote:
> Sorry, I don't have access to that system at the moment and supply the
> info as early as I get back home in 10 days. Please keep me in cc.
>
> As for the other questions:
>
> - no proprietary drivers installed
> - no BIOS update
20 matches
Mail list logo