> -----Original Message-----
> From: Laurent Pinchart [mailto:[email protected]]
> Sent: Tuesday, March 23, 2010 5:11 PM
> To: [email protected]
> Cc: Hiremath, Vaibhav; [email protected]
> Subject: Re: [Resubmit: PATCH-V2] Introducing ti-media directory
> 
> On Friday 19 March 2010 10:35:50 [email protected] wrote:
> > From: Vaibhav Hiremath <[email protected]>
> >
> > Looking towards the number of files which are cluttering in media/video/
> > directory, it is required to introduce seperate working
> > directory for TI devices.
> 
> You should then move the omap24xxcam driver as well.
[Hiremath, Vaibhav] I wanted to move this file to ti-media directory, but left 
it only because it is based on V4L2-Int framework (legacy).

> 
> > Again the IP's are being re-used across the devices which makes it very
> > difficuilt to re-use the driver code. For example, DM6446 and AM3517 both
> > uses exactly same VPFE/CCDC IP, but the driver is encapsulated under
> > DAVINCI which makes it impossible to re-use.
> 
> I'm not too sure to like the ti-media name. It will soon get quite crowded,
> and name collisions might occur (look at the linux-omap-camera tree and the
> ISP driver in there for instance). Isn't there an internal name to refer to
> both the DM6446 and AM3517 that could be used ?
[Hiremath, Vaibhav] Laurent,

ti-media directory is top level directory where we are putting all TI devices 
drivers. So having said that, we should worrying about what goes inside this 
directory.
For me ISP is more generic, if you compare davinci and OMAP. 

Frankly, there are various naming convention we do have from device to device, 
even if the IP's are being reused. For example, the internal name for OMAP is 
ISP but Davinci refers it as a VPSS.

Thanks,
Vaibhav

> 
> > Signed-off-by: Vaibhav Hiremath <[email protected]>
> 
> --
> Regards,
> 
> Laurent Pinchart
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to