From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/5] ARM: dev_archdata: add private iommu extension
Date: Mon, 26 Sep 2011 19:30:01 -0600 [thread overview]
Message-ID: <20110927013001.GA20588@ponder.secretlab.ca> (raw)
In-Reply-To: <1316948337-7924-2-git-send-email-ohad@wizery.com>
On Sun, Sep 25, 2011 at 01:58:53PM +0300, Ohad Ben-Cohen wrote:
> Add a private iommu pointer to the ARM-specific arch data in the
> device struct, which will be used to attach iommu-specific data
> to devices which require iommu support.
>
> Different iommu implementations (on different platforms) will attach
> different types of data to this pointer, so 'void *' is currently used
> (the downside is reduced typesafety).
>
> Note: ia64, x86 and sparc have this exact iommu extension as well, and
> if others are likely to adopt it too, we might want to consider
> adding this to the device struct itself directly.
>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> ---
> arch/arm/include/asm/device.h | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/include/asm/device.h b/arch/arm/include/asm/device.h
> index 9f390ce..6615f03 100644
> --- a/arch/arm/include/asm/device.h
> +++ b/arch/arm/include/asm/device.h
> @@ -10,6 +10,9 @@ struct dev_archdata {
> #ifdef CONFIG_DMABOUNCE
> struct dmabounce_device_info *dmabounce;
> #endif
> +#ifdef CONFIG_IOMMU_API
> + void *iommu; /* private IOMMU data */
> +#endif
Blech. Oh well. Not much point in doing something different if x86
uses a void*.
g.
next prev parent reply other threads:[~2011-09-27 1:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 10:58 [RFC 0/5] OMAP groundwork for IOMMU-based DMA API Ohad Ben-Cohen
[not found] ` <1316948337-7924-3-git-send-email-ohad@wizery.com>
2011-09-26 22:53 ` [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata Kevin Hilman
2011-09-27 18:09 ` Ohad Ben-Cohen
2011-10-04 18:15 ` Kevin Hilman
2011-10-04 19:54 ` Ohad Ben-Cohen
2011-10-04 20:29 ` Kevin Hilman
2011-10-05 7:01 ` Ohad Ben-Cohen
2011-10-04 21:40 ` Cousson, Benoit
[not found] ` <1316948337-7924-2-git-send-email-ohad@wizery.com>
2011-09-27 1:30 ` Grant Likely [this message]
2011-10-02 18:48 ` [RFC 1/5] ARM: dev_archdata: add private iommu extension Ohad Ben-Cohen
2011-10-05 9:26 ` Ohad Ben-Cohen
2011-10-13 9:15 ` Ohad Ben-Cohen
2011-10-13 10:42 ` Russell King - ARM Linux
2011-10-13 11:55 ` Ohad Ben-Cohen
[not found] ` <1316948337-7924-6-git-send-email-ohad@wizery.com>
2011-09-27 11:46 ` [RFC 5/5] iommu/omap: eliminate the public omap_find_iommu_device() method Laurent Pinchart
2011-11-09 8:50 ` Ohad Ben-Cohen
2011-11-09 9:17 ` Laurent Pinchart
2011-11-14 21:02 ` Tony Lindgren
[not found] ` <1316948337-7924-5-git-send-email-ohad@wizery.com>
2011-11-09 9:17 ` [RFC 4/5] ARM: OMAP3: bind omap3isp_device to its iommu device Laurent Pinchart
2011-11-09 9:29 ` Ohad Ben-Cohen
2011-11-14 21:01 ` Tony Lindgren
[not found] ` <1316948337-7924-4-git-send-email-ohad@wizery.com>
2011-11-14 21:01 ` [RFC 3/5] ARM: OMAP: iommu: declare a private iommu binding struct Tony Lindgren
2011-11-15 10:39 ` [RFC 0/5] OMAP groundwork for IOMMU-based DMA API Roedel, Joerg
2011-11-15 10:45 ` Ohad Ben-Cohen
2011-11-15 11:10 ` Roedel, Joerg
2011-11-15 11:18 ` Ohad Ben-Cohen
2011-12-05 14:21 ` Ohad Ben-Cohen
2011-12-05 15:18 ` Roedel, Joerg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110927013001.GA20588@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).