On 02/10/2012 12:15 PM, Guennadi Liakhovetski wrote: >>>> On 02/10/2012 09:42 AM, Guennadi Liakhovetski wrote: >>>>> ...thinking about this interleaved data, is there anything else left, that >>>>> the following scheme would be failing to describe: >>>>> >>>>> * The data is sent in repeated blocks (periods) >>>> >>>> The data is sent in irregular chunks of varying size (few hundred of bytes >>>> for example). >>> >>> Right, the data includes headers. How about sensors providing >>> header-parsing callbacks? >> >> This implies processing of headers/footers in kernel space to some generic >> format. It might work, but sometimes there might be an unwanted performance >> loss. However I wouldn't expect it to be that significant, depends on how >> the format of an embedded data from the sensor looks like. Processing 4KiB >> of data could be acceptable. > > In principle I agree - (ideally) no processing in the kernel _at all_. > Just pass the complete frame data as is to the user-space. But if we need > any internal knowledge at all about the data, maybe callbacks would be a > better option, than trying to develop a generic descriptor. Perhaps, > something like "get me the location of n'th block of data of format X." Hmm, I thought about only processing frame embedded data to some generic format. I find the callbacks for extracting the data in the kernel impractical, with full HD video stream you may want to use some sort of hardware accelerated processing, like using NEON for example. We can allow this only by leaving the deinterleave process to the user space. > Notice, this does not (necessarily) have anything to do with the previous > discussion, concerning the way, how the CSI receiver should be getting its > configuration. -- Regards, Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
