[git pull] IOMMU Updates for Linux v3.15

2014-04-04 Thread Joerg Roedel
Hi Linus, The following changes since commit 455c6fdbd219161bd09b1165f11699d6d73de11c: Linux 3.14 (2014-03-30 20:40:15 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-updates-v3.15 for you to fetch changes up to e172b8

Re: [PATCH 0/5] OMAP IOMMU fixes and IOMMU architecture questions

2014-04-04 Thread Joerg Roedel
On Fri, Mar 14, 2014 at 12:00:16PM +0100, Laurent Pinchart wrote: > Right, we indeed need two levels of API, one for drivers such as remoteproc > that need direct control of the IOMMU, and one for drivers that only need to > map buffers without any additional requirement. In the second case the

Re: [PATCH 0/5] OMAP IOMMU fixes and IOMMU architecture questions

2014-04-04 Thread Marek Szyprowski
Hello, I'm sorry for a delay, I've got back from my holidays and I'm still busy trying to get thought all the emails. On 2014-03-17 23:44, Laurent Pinchart wrote: Hi Suman and Sakari, On Monday 17 March 2014 14:58:24 Suman Anna wrote: > On 03/16/2014 04:54 PM, Sakari Ailus wrote: > > On Fri,

Re: [PATCH] iommu-groups: Add list_head for iommu groups

2014-04-04 Thread Alex Williamson
On Fri, 2014-04-04 at 11:12 +0530, Ritesh Harjani wrote: > Hi All, > > Please find the below patch and let me know your suggestions on this. > > With this patch iommu groups can be linked and iommu driver will > get to know which all iommu groups belongs to a particular iommu device. > > > > E

Re: [RFC PATCH v2 1/2] pci: Create PCIe requester ID interface

2014-04-04 Thread Bjorn Helgaas
On Thu, Apr 3, 2014 at 8:51 PM, Alex Williamson wrote: > On Thu, 2014-04-03 at 15:48 -0600, Bjorn Helgaas wrote: >> [+cc George] >> >> On Fri, Aug 2, 2013 at 10:59 AM, Alex Williamson >> wrote: >> > ... >> > Great! I'm still trying to figure out how to handle the quirk around >> > Intel PCI-to-P

[PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-04 Thread Alex Williamson
The driver_override field allows us to specify the driver for a device rather than relying on the driver to provide a positive match of the device. This shortcuts the existing process of looking up the vendor and device ID, adding them to the driver new_id, binding the device, then removing the ID

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-04 Thread Guenter Roeck
On 04/04/2014 06:35 PM, Kim Phillips wrote: Needed by platform device drivers, such as the vfio-platform driver [1], in order to bypass the existing OF, ACPI, id_table and name string matches, and successfully be able to be bound to any device, like so: echo vfio-platform > /sys/bus/platform/dev