RE: [RFC 1/8] TILER-DMM: DMM-PAT driver for TI TILER

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Sin, David
> Sent: Wednesday, July 28, 2010 8:09 PM
> To: Laurent Pinchart; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Cc: Hiremath, Vaibhav; linux-omap@xxxxxxxxxxxxxxx; Tony Lindgren; Russell
> King; Ohad Ben-Cohen; Kanigeri, Hari; Shilimkar, Santosh; Molnar, Lajos
> Subject: RE: [RFC 1/8] TILER-DMM: DMM-PAT driver for TI TILER
> 
> > -----Original Message-----
> > From: Laurent Pinchart [mailto:laurent.pinchart@xxxxxxxxxxxxxxxx]
> > Sent: Wednesday, July 28, 2010 5:00 AM
> > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> > Cc: Hiremath, Vaibhav; Sin, David;
> > linux-omap@xxxxxxxxxxxxxxx; Tony Lindgren; Russell King; Ohad
> > Ben-Cohen; Kanigeri, Hari; Shilimkar, Santosh; Molnar, Lajos
> > Subject: Re: [RFC 1/8] TILER-DMM: DMM-PAT driver for TI TILER
<snip>

> > I think I agree with it. The tiler provides dynamic views on
> > arbitrary
> > physical memory. Ideally it shouldn't be tied to the
> > media/video subsystem
> > (obviously it should still provide an interface for V4L drivers).
> >
> > It's getting a bit hard to comment on the proposal, as
> > there's no public
> > documentation I'm aware of beside the Documentation/arm/TILER
> > file in the
> > patch set, and that information is far too concise and vague.
> >
> > --
> > Regards,
> >
> > Laurent Pinchart
> >
> 
> [dhs] I understand what you're stating here, conceptually, but I'm missing
> some details.  Do you mean that there needs to be a generic layer between a
> given video memory allocator and V4L? 
> and that set of APIs should point to
> specific functions based on availability (e.g. VRFB, TILER, future TILER,
> other IP, etc)?
> 
[Hiremath, Vaibhav] David,
As far as Memory allocator is concerned I think it is more generic term and should not really tie to underneath hardware/feature (Tiler, VRFB or could be anything). This is long time issue with every Embedded devices dealing with Video, due to their dynamic requirement of memory/buffers.

Have you looked at Samsung (CMA) and Qualcomm (IOMMU) patches for memory allocation/management? I think it is worth to look at their approach. 

Thanks,
Vaibhav

> Laurent:  The TRM for DMM-TILER should be publicly available already, but
> for some reason, I'm not able to see the link.  I will work on this...
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux