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
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,
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
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
4 matches
Mail list logo