Yes ill fix it up and move the doc to the other patch and send a v2
From: Shilimkar, Santosh
Sent: Wednesday, March 20, 2013 1:22 AM
To: Taneja, Archit
Cc: Gross, Andy; linux-omap@vger.kernel.org; Cousson, Benoit;
devicetree-disc...@lists.ozlabs.org
Tony,
Please queue this patch at your earliest convenience.
We had some discussion on the splitting out of the DMM/Tiler driver
from the omapdrm driver. There might be some interest in leveraging
the Tiler for omapfb. However, we agreed this can be deferred until
some other device (omapfb or
Tomi,
So at this point, are you OK with deferring a split of the DMM until it
necessary to do so (if ever)? I'd like to get this patch in so that people
have a working omapdrm device when they enable the config options.
Regards,
Andy
--
To unsubscribe from this list: send the line unsubscribe
On Thu, May 24, 2012 at 1:01 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
+struct omap_drm_platform_data {
+ struct omap_kms_platform_data *kms_pdata;
+};
This one is missing struct omap_dmm_platform_data *dmm_pdata, so you
didn't just move the struct. Is that on purpose?
Good point.
On Thu, May 24, 2012 at 7:13 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-05-24 at 02:44 -0600, Rob Clark wrote:
but other drivers *can* use tiler, thanks to dmabuf.. I have omap4iss
v4l2 camera working w/ tiler buffers on my pandaboard, for example.
Maybe fbdev is an
On Wed, Mar 7, 2012 at 6:05 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Does this DMM has become synonymous mean that people just started
calling TILER DMM, and thus the name has stuck, or are there technical
reasons to handle it as DMM in the kernel? If the former, and if TILER
is the
