Em Thu, 17 Sep 2009 08:34:23 +0200 Hans Verkuil <hverk...@xs4all.nl> escreveu:
> On Thursday 17 September 2009 00:28:38 Karicheri, Muralidharan wrote: > > > > > >> And as I explained above, a v4l2_subdev just implements an interface. It > > >has > > >> no relation to devices. And yes, I'm beginning to agree with you that > > >subdevice > > >> was a bad name because it suggested something that it simply isn't. > > >> > > >> That said, I also see some advantages in doing this. For statistics or > > >> histogram sub-devices you can implement a read() call to read the data > > >> instead of using ioctl. It is more flexible in that respect. > > > > > >I think this will be more flexible and will be less complex than creating a > > >proxy > > >device. For example, as you'll be directly addressing a device, you don't > > >need to > > >have any locking to avoid the risk that different threads accessing > > >different > > >sub-devices at the same time would result on a command sending to the wrong > > >device. > > >So, both kernel driver and userspace app can be simpler. > > > > > > Not really. User application trying to parse the output of a histogram which > > really will about 4K in size as described by Laurent. Imagine application > > does lot of parsing to decode the values thrown by the sysfs. Again on > > different platform, they can be different formats. With ioctl, each of > > these platforms provides api to access them and it is much simpler to use. > > Same for configuring IPIPE on DM355/DM365 where there are hundreds of > > parameters and write a lot of code in sysfs to parse each of these > > variables. I can see it as a nightmare for user space library or > > application developer. > > I believe Mauro was talking about normal device nodes, not sysfs. Yes. > What is a bit more complex in Mauro's scheme is that to get hold of the right > device node needed to access a sub-device you will need to first get the > subdev's entity information from the media controller, then go to libudev to > translate major/minor numbers to an actual device path, and then open that. Good point. This reforces my thesis that the media controller (or, at least his enumeration function) will be better done via sysfs. As Andy pointed, one of the biggest advantages is that udev can enrich the user's experience by calling some tweak applications or by calling special applications (like lirc) when certain media devices are created. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
