From: Kevin Hilman <khilman@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Joerg Roedel <Joerg.Roedel@amd.com>,
<iommu@lists.linux-foundation.org>, Arnd Bergmann <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>, Cousson Benoit <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata
Date: Mon, 26 Sep 2011 15:53:22 -0700 [thread overview]
Message-ID: <87sjni9aql.fsf@ti.com> (raw)
In-Reply-To: <1316948337-7924-3-git-send-email-ohad@wizery.com> (Ohad Ben-Cohen's message of "Sun, 25 Sep 2011 13:58:54 +0300")
Hi Ohad,
Ohad Ben-Cohen <ohad@wizery.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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Joerg Roedel <Joerg.Roedel@amd.com>,
iommu@lists.linux-foundation.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, Cousson Benoit <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata
Date: Mon, 26 Sep 2011 15:53:22 -0700 [thread overview]
Message-ID: <87sjni9aql.fsf@ti.com> (raw)
In-Reply-To: <1316948337-7924-3-git-send-email-ohad@wizery.com> (Ohad Ben-Cohen's message of "Sun, 25 Sep 2011 13:58:54 +0300")
Hi Ohad,
Ohad Ben-Cohen <ohad@wizery.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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata
Date: Mon, 26 Sep 2011 15:53:22 -0700 [thread overview]
Message-ID: <87sjni9aql.fsf@ti.com> (raw)
In-Reply-To: <1316948337-7924-3-git-send-email-ohad@wizery.com> (Ohad Ben-Cohen's message of "Sun, 25 Sep 2011 13:58:54 +0300")
Hi Ohad,
Ohad Ben-Cohen <ohad@wizery.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
next prev parent reply other threads:[~2011-09-26 22:53 UTC|newest]
Thread overview: 78+ 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
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-09-25 10:58 ` [RFC 1/5] ARM: dev_archdata: add private iommu extension Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-09-27 1:30 ` Grant Likely
2011-09-27 1:30 ` Grant Likely
2011-10-02 18:48 ` Ohad Ben-Cohen
2011-10-02 18:48 ` Ohad Ben-Cohen
2011-10-02 18:48 ` Ohad Ben-Cohen
2011-10-05 9:26 ` Ohad Ben-Cohen
2011-10-05 9:26 ` Ohad Ben-Cohen
2011-10-13 9:15 ` Ohad Ben-Cohen
2011-10-13 9:15 ` Ohad Ben-Cohen
2011-10-13 10:42 ` Russell King - ARM Linux
2011-10-13 10:42 ` Russell King - ARM Linux
2011-10-13 11:55 ` Ohad Ben-Cohen
2011-10-13 11:55 ` Ohad Ben-Cohen
2011-10-13 11:55 ` Ohad Ben-Cohen
2011-09-25 10:58 ` [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-09-26 22:53 ` Kevin Hilman [this message]
2011-09-26 22:53 ` Kevin Hilman
2011-09-26 22:53 ` Kevin Hilman
2011-09-27 18:09 ` Ohad Ben-Cohen
2011-09-27 18:09 ` Ohad Ben-Cohen
2011-09-27 18:09 ` Ohad Ben-Cohen
2011-10-04 18:15 ` Kevin Hilman
2011-10-04 18:15 ` Kevin Hilman
2011-10-04 19:54 ` Ohad Ben-Cohen
2011-10-04 19:54 ` Ohad Ben-Cohen
2011-10-04 20:29 ` Kevin Hilman
2011-10-04 20:29 ` Kevin Hilman
2011-10-05 7:01 ` Ohad Ben-Cohen
2011-10-05 7:01 ` Ohad Ben-Cohen
2011-10-04 21:40 ` Cousson, Benoit
2011-10-04 21:40 ` Cousson, Benoit
2011-10-04 21:40 ` Cousson, Benoit
2011-09-25 10:58 ` [RFC 3/5] ARM: OMAP: iommu: declare a private iommu binding struct Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-11-14 21:01 ` Tony Lindgren
2011-11-14 21:01 ` Tony Lindgren
2011-09-25 10:58 ` [RFC 4/5] ARM: OMAP3: bind omap3isp_device to its iommu device Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-11-09 9:17 ` Laurent Pinchart
2011-11-09 9:17 ` Laurent Pinchart
2011-11-09 9:29 ` Ohad Ben-Cohen
2011-11-09 9:29 ` Ohad Ben-Cohen
2011-11-14 21:01 ` Tony Lindgren
2011-11-14 21:01 ` Tony Lindgren
2011-09-25 10:58 ` [RFC 5/5] iommu/omap: eliminate the public omap_find_iommu_device() method Ohad Ben-Cohen
2011-09-25 10:58 ` Ohad Ben-Cohen
2011-09-27 11:46 ` Laurent Pinchart
2011-09-27 11:46 ` Laurent Pinchart
2011-11-09 8:50 ` Ohad Ben-Cohen
2011-11-09 8:50 ` Ohad Ben-Cohen
2011-11-09 9:17 ` Laurent Pinchart
2011-11-09 9:17 ` Laurent Pinchart
2011-11-14 21:02 ` Tony Lindgren
2011-11-14 21:02 ` Tony Lindgren
2011-11-15 10:39 ` [RFC 0/5] OMAP groundwork for IOMMU-based DMA API Roedel, Joerg
2011-11-15 10:39 ` Roedel, Joerg
2011-11-15 10:39 ` Roedel, Joerg
2011-11-15 10:45 ` Ohad Ben-Cohen
2011-11-15 10:45 ` Ohad Ben-Cohen
2011-11-15 10:45 ` Ohad Ben-Cohen
2011-11-15 11:10 ` Roedel, Joerg
2011-11-15 11:10 ` Roedel, Joerg
2011-11-15 11:10 ` Roedel, Joerg
2011-11-15 11:18 ` Ohad Ben-Cohen
2011-11-15 11:18 ` Ohad Ben-Cohen
2011-11-15 11:18 ` Ohad Ben-Cohen
2011-12-05 14:21 ` Ohad Ben-Cohen
2011-12-05 14:21 ` Ohad Ben-Cohen
2011-12-05 14:21 ` Ohad Ben-Cohen
2011-12-05 15:18 ` Roedel, Joerg
2011-12-05 15:18 ` Roedel, Joerg
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=87sjni9aql.fsf@ti.com \
--to=khilman@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=Joerg.Roedel@amd.com \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.