Ohad Ben-Cohen <ohad@xxxxxxxxxx> writes: > On Tue, Oct 4, 2011 at 8:15 PM, Kevin Hilman <khilman@xxxxxx> 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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
