Re: [PATCH v5 1/3] iommu/rockchip: rk3288 iommu driver

2014-10-16 Thread Daniel Kurtz
On Tue, Oct 14, 2014 at 4:02 PM, Daniel Kurtz wrote: > The rk3288 has several iommus. Each iommu belongs to a single master > device. There is one device (ISP) that has two slave iommus, but that > case is not yet supported by this driver. > > At subsys init, the iommu driver registers itself as

Re: [PATCH v3 22/27] s390/MSI: Use MSI chip framework to configure MSI/MSI-X irq

2014-10-16 Thread Yijing Wang
On 2014/10/16 20:13, Sebastian Ott wrote: > On Wed, 15 Oct 2014, Yijing Wang wrote: >> Use MSI chip framework instead of arch MSI functions to configure >> MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. >> >> Signed-off-by: Yijing Wang >> --- >> Hi Sebastian, >>I dropped

Re: [PATCH v5 1/1] iommu-api: Add map_sg/unmap_sg functions

2014-10-16 Thread Olav Haugan
On 10/15/2014 2:16 AM, Thierry Reding wrote: On Mon, Oct 06, 2014 at 12:02:47PM -0700, Olav Haugan wrote: On 9/25/2014 10:01 AM, Joerg Roedel wrote: On Mon, Aug 11, 2014 at 03:45:50PM -0700, Olav Haugan wrote: +static inline int iommu_map_sg(struct iommu_domain *domain, unsigned long iova, +

[RFC PATCH v2 4/4] vfio: platform: devtree: return arrays of u32, u16, or u8 data

2014-10-16 Thread Antonios Motakis
Certain properties of a device tree node are accessible as an array of unsigned integers, either u32, u16, or u8. Let the VFIO user query this type of device node properties. Accessing u64 arrays is not yet implemented in this RFC. Signed-off-by: Antonios Motakis --- drivers/vfio/platform/devtre

[RFC PATCH v2 2/4] vfio: platform: devtree: return available property names

2014-10-16 Thread Antonios Motakis
The available properties of a device are not indexed numerically, instead they are accessible by property name. Passing type = VFIO_DEVTREE_PROP_LIST to VFIO_DEVICE_GET_DEVTREE_INFO, returns a list of strings with the available properties that the VFIO user can access. Signed-off-by: Antonios Mota

[RFC PATCH v2 1/4] vfio: platform: add device tree info API and skeleton

2014-10-16 Thread Antonios Motakis
This patch introduced the API to return device tree info about a PLATFORM device (if described by a device tree) and the skeleton of the implementation for VFIO_PLATFORM. Information about any device node bound by VFIO_PLATFORM should be queried via the introduced ioctl VFIO_DEVICE_GET_DEVTREE_INFO

[RFC PATCH v2 3/4] vfio: platform: devtree: access property as a list of strings

2014-10-16 Thread Antonios Motakis
Certain device tree properties (e.g. the device node name, the compatible string), are available as a list of strings (separated by the null terminating character). Let the VFIO user query this type of properties. Signed-off-by: Antonios Motakis --- drivers/vfio/platform/devtree.c | 43 +

[RFC PATCH v2 0/4] vfio: platform: return device tree info for a platform device node

2014-10-16 Thread Antonios Motakis
This RFC's intention is to show what an interface to access device node properties for the VFIO platform driver can look like. If a device tree node corresponding to a platform device bound by VFIO PLATFORM or VFIO AMBA is available, this patch series will allow the user to query the properties as

Re: [PATCH v3 22/27] s390/MSI: Use MSI chip framework to configure MSI/MSI-X irq

2014-10-16 Thread Sebastian Ott
On Wed, 15 Oct 2014, Yijing Wang wrote: > Use MSI chip framework instead of arch MSI functions to configure > MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework. > > Signed-off-by: Yijing Wang > --- > Hi Sebastian, >I dropped the Acked-by , because this version has a > lot c

Re: PCIe PASID (Process Address Space ID) and iommu code

2014-10-16 Thread Joerg Roedel
On Wed, Oct 15, 2014 at 09:50:58PM -0600, Bjorn Helgaas wrote: > [+cc Joerg, Suravee, Jay, iommu list, linux-pci] > > On Wed, Oct 15, 2014 at 5:44 PM, Kallol Biswas wrote: > > Resending, as message got bounced for html content. > > > > Hi, > > PCIe