To Aguirre Rodriguez, Sergio Alberto <saaguirre@xxxxxx> wrote: >> Hi >> >> Current TI ISP implementation doesn't allow exclusive use of Resizer, >> I mean CCDC->Resizer. > > Yeah, we haven't added that functionality yet to the driver because we didn't have the need with our customers yet. But as more people like you are demanding this, then a solution for implementing it shall be discussed. > What kind of complexity/effort involved using just the resizer? As my sensor gives YUV 4:2:2, I can directly feed this to the resizer pipeline. To kick start could you please share a quick hack? I can then take it forward. >> >> Any specific reason why CCDC->Preview->Resizer path has been taken? >> Please share the background of this decision. > > The reason on deciding about this ISP datapath is because we wanted to emphasize the use of the OMAP3 ISP, instead of the use of a sensor internal ISP. > I can see from your design that you have character device wrapper to use Resizer, can we fit this hack with CCDC->Resizer logic? this is my quick guess, correct If I am wrong. >> >> My sensor gives only YUV data, but the Preview pipeline is happy only >> with RAW Bayer. >> Is this a hardware limitation? > > Yeah, the ISP Preview module can only convert from 10-bit Bayer data to YCbCr 4:2:2 data (YUV). > -- 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
