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: Tue, 04 Oct 2011 13:29:03 -0700 [thread overview]
Message-ID: <87mxdga4c0.fsf@ti.com> (raw)
In-Reply-To: <CAK=WgbYaEPBUz_J11+f+W+G9uUG3E6aQ-5=X9bj2nRhij-w-Sw@mail.gmail.com> (Ohad Ben-Cohen's message of "Tue, 4 Oct 2011 21:54:44 +0200")
Ohad Ben-Cohen <ohad@wizery•com> writes:
> On Tue, Oct 4, 2011 at 8:15 PM, Kevin Hilman <khilman@ti•com> wrote:
>> The approach is OK with me, but I'm a bit torn about whether or not to
>> merge this since the need for this should go away when converting to DT.
>
> I guess it will still take some time until our boards are fully
> functional with DT, so I think we should regard this as an interim
> solution. Without this patch, a huge deal of code consolidation and
> generalization is gated (namely - generic iommu and dma api, and
> everything that depends on it, e.g. rpmsg/remoteproc).
>
>> Is anyone working on IOMMU DT description?
>
> Unless Benoit is, I'll happily pick this up.
tag. you're it.
>> I guess if I do merge this, we can also clean this up significantly
>> after all devices are converted to DT.
>
> Sure.
OK, as long as I have some confidence that this is going in the right
direction (and having you on the job is a good sign!) I'm willing to
merge something like this as an interim solution.
Kevin
>> Unless it has other dependencies on Benoit's further DT patches, you can
>> base this on my for_3.2/omap_device-2 branch which includes Benoit's
>> alloc changes.
>
> Ok, thanks a lot !
> Ohad.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-10-04 20:29 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 [this message]
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 ` [RFC 1/5] ARM: dev_archdata: add private iommu extension Grant Likely
2011-10-02 18:48 ` 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=87mxdga4c0.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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