[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sjni9aql.fsf@ti.com>
Date: Mon, 26 Sep 2011 15:53:22 -0700
From: Kevin Hilman <khilman@...com>
To: Ohad Ben-Cohen <ohad@...ery.com>
Cc: <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Hiroshi DOYU <Hiroshi.DOYU@...ia.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Joerg Roedel <Joerg.Roedel@....com>,
<iommu@...ts.linux-foundation.org>, Arnd Bergmann <arnd@...db.de>,
<linux-kernel@...r.kernel.org>, Cousson Benoit <b-cousson@...com>,
Tony Lindgren <tony@...mide.com>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata
Hi Ohad,
Ohad Ben-Cohen <ohad@...ery.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists