* Tony Lindgren <tony@xxxxxxxxxxx> [121026 11:02]: > * Ohad Ben-Cohen <ohad@xxxxxxxxxx> [121026 02:56]: > > Hi Laurent, > > > > On Fri, Oct 26, 2012 at 11:35 AM, Laurent Pinchart > > <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote: > > > That's on my to-do list, as well as porting the OMAP3 ISP driver to videobuf2, > > > adding DT support, moving to the common clock framework (when that will be > > > available for the OMAP3), supporting missing V4L2 features, ... All this in my > > > spare time of course, otherwise it wouldn't be fun, would it ? ;-) > > > > Hmm, seems like a short to-do list ;) > > Sounds Laurent will take care of it :) > > > > I would also like to move the tidspbridge to the DMA API, but I think we'll > > > need to move step by step there, and using the OMAP IOMMU and IOVMM APIs as an > > > intermediate step would allow splitting patches in reviewable chunks. I know > > > it's a step backwards in term of OMAP IOMMU usage, but that's in my opinion a > > > temporary nuisance to make the leap easier. > > > > Since tidspbridge is in staging I guess it's not a problem, though it > > sounds to me like using the correct API in the first place is going to > > make less churn. > > Not related to these patches, but also sounds like we may need to drop > some staging/tidspbridge code to be able to move forward with the > ARM common zImage plans. See the "[GIT PULL] omap plat header removal > for v3.8 merge window, part1" thread for more info. OK so are people happy with the patches in this series? Please everybody ack if no more comments so we can move on towards getting CONFIG_MULTIPLATFORM to work for omaps. Regards, Tony -- 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
