[RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata
From: Kevin Hilman <hidden>
Date: 2011-09-26 22:53:32
Also in:
linux-omap, lkml
Possibly related (same subject, not in this thread)
- 2011-10-05 · Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata · Ohad Ben-Cohen <hidden>
- 2011-10-04 · Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata · Cousson, Benoit <hidden>
- 2011-10-04 · Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata · Kevin Hilman <hidden>
- 2011-10-04 · Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata · Ohad Ben-Cohen <hidden>
- 2011-10-04 · Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata · Kevin Hilman <hidden>
Hi Ohad, Ohad Ben-Cohen [off-list ref] writes:
Make it possible to set an iommu private archdata before a newly-created omap device is registered. Binding iommu client devices with their respective iommu data this way is needed so the generic IOMMU API can later be used without employing any omap-specific IOMMU plumbing. This patch just crudely adds an omap_device_build_ss_ext() method which accepts an iommu private data, but we may actually want to do something more generic here: e.g., split the omap_device_build API to alloc+add methods, so users can just manipulate the device as needed before it is registered (very much like we can do with plain devices).
Yes indeed.
Benoit did just this in preparation for DT.
http://marc.info/?l=linux-omap&m=131672480111927&w=2
Will that meet your needs?
Kevin