Re: [RFC PATCH v3 13/13] drivers: acpi: iort: introduce iort_iommu_configure

2016-08-11 Thread Lorenzo Pieralisi
On Wed, Aug 03, 2016 at 10:19:43AM -0400, nwatt...@codeaurora.org wrote: [...] > >+const struct iommu_ops *iort_iommu_configure(struct device *dev) > >+{ > >+struct acpi_iort_node *node, *parent; > >+struct fwnode_handle *iort_fwnode; > >+u32 rid = 0, devid = 0; > > Since this routin

Re: [RFC PATCH v3 13/13] drivers: acpi: iort: introduce iort_iommu_configure

2016-08-08 Thread Lorenzo Pieralisi
Hi Nate, thanks for having a look. On Wed, Aug 03, 2016 at 10:19:43AM -0400, nwatt...@codeaurora.org wrote: > On 2016-07-20 07:23, Lorenzo Pieralisi wrote: > >DT based systems have a generic kernel API to configure IOMMUs > >for devices (ie of_iommu_configure()). > > > >On ARM based ACPI systems,

Re: [RFC PATCH v3 13/13] drivers: acpi: iort: introduce iort_iommu_configure

2016-08-03 Thread nwatters
On 2016-07-20 07:23, Lorenzo Pieralisi wrote: DT based systems have a generic kernel API to configure IOMMUs for devices (ie of_iommu_configure()). On ARM based ACPI systems, the of_iommu_configure() equivalent can be implemented atop ACPI IORT kernel API, with the corresponding functions to map

[RFC PATCH v3 13/13] drivers: acpi: iort: introduce iort_iommu_configure

2016-07-20 Thread Lorenzo Pieralisi
DT based systems have a generic kernel API to configure IOMMUs for devices (ie of_iommu_configure()). On ARM based ACPI systems, the of_iommu_configure() equivalent can be implemented atop ACPI IORT kernel API, with the corresponding functions to map device identifiers to IOMMUs and retrieve the c