On Thu, Feb 9, 2012 at 11:28 AM, Greg KH <gre...@linuxfoundation.org> wrote: > On Fri, Jan 13, 2012 at 02:41:59PM -0600, Rob Clark wrote: >> From: Rob Clark <r...@ti.com> >> >> Register OMAP DRM/KMS platform device, and reserve a CMA region for >> the device to use for buffer allocation. >> >> v1: initial patch >> v2: move platform data structs into plat-omap to avoid having to >> #include headers from drivers/staging and cleanups >> >> Signed-off-by: Rob Clark <r...@ti.com> >> --- >> Note: after applying this patch there will be duplicate copies of the >> platform data structs (until the 2nd patch is applied). But I tested >> to ensure this does not cause build breaks. So the 2nd patch which >> should go thru staging tree is safe to be held until this patch hits >> Linus's master branch. >> >> arch/arm/plat-omap/Makefile | 2 +- >> arch/arm/plat-omap/common.c | 3 +- >> arch/arm/plat-omap/drm.c | 83 >> +++++++++++++++++++++++++++++++++ >> arch/arm/plat-omap/include/plat/drm.h | 70 +++++++++++++++++++++++++++ >> 4 files changed, 156 insertions(+), 2 deletions(-) >> create mode 100644 arch/arm/plat-omap/drm.c >> create mode 100644 arch/arm/plat-omap/include/plat/drm.h > > Did this ever get applied?
Not yet, there was requested some omap hwmod related changes for how the driver gets SoC version specific information (irq, base addr), so I'll resubmit again the device file registration (and the 2nd patch) but that might have to be for 3.4 You can drop the existing 2/2 patch BR, -R > As I can't apply 2/2 without it, please feel > free to add: > Acked-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> > > to 2/2 when some dri/omap developer commits this one. > > thanks, > > greg k-h -- 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
