On Wed, Mar 14, 2012 at 7:38 AM, Tomi Valkeinen <tomi.valkei...@ti.com> wrote: > Hi, > > On Tue, 2012-03-13 at 15:34 -0500, Rob Clark wrote: >> From: Andy Gross <andy.gr...@ti.com> >> >> Register OMAP DRM/KMS platform device, and reserve a CMA region for >> the device to use for buffer allocation. DMM is split into a >> separate device using hwmod. > > What's the diff with this and the previous one?
Moving drm.c to mach-omap2 (header could not move because omap_reserve() is in plat-omap.. but this seems to be the same as what is done for dspbridge). > I see you still have the platform data there. You didn't comment on > that. Where is it used after the board files are gone when we use DT? I was kind-of thinking that there would be some DT<->data-structure glue somewhere.. not sure if this goes in mach-omap2 or in the driver itself, but presumably it is needed somewhere. It is only really special cases where some board specific device-tree data is needed, so it seems like this is ok to handle later. > And how about the size of the contiguous memory area, it was left a bit > unclear to me why it cannot be dynamic. I don't think there is anything preventing adding a bootarg, but I think it is not essential so ok to add later BR, -R > Tomi > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
