[PATCH v3 2/2] pipeline: simple: Use proper device for frame start events

[Laurent Pinchart]

(CC'ing Bingbu)

On Mon, Feb 24, 2025 at 02:29:52PM +0100, Stanislaw Gruszka wrote:
> On Mon, Feb 24, 2025 at 02:24:12PM +0200, Laurent Pinchart wrote:
> > On Mon, Feb 24, 2025 at 12:02:30PM +0100, Stanislaw Gruszka wrote:
> > > 
> > > > I expect CSI-2 errors to be extremely rare. Did you actually get some ?
> > > > Or were frames dropped by the driver due to buffer queue underruns ?
> > > 
> > > It's quite good reproducible for IPU6 when first start using camera
> > > after boot.
> > > 
> > > [   82.758542] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Payload checksum (CRC) error
> > > [   83.250939] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Single packet header error corrected
> > > [   83.250962] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Multiple packet header errors detected
> > > [   83.250964] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Payload checksum (CRC) error
> > > [   83.250965] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Incomplete long packet detected
> > > [   83.250966] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Frame sync error
> > > [   83.250967] intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-1 error: Inter-frame long packet discarded
> > > 
> > > Not really sure why. After initial errors, things get to
> > > work and no other cis2 errors happen.
> > 
> > And that's only the first time after boot ? That sounds like a driver
> > bug. What happens if you unload and reload the driver, does the first
> > capture session after reloading exhibit the same problems ?
> 
> Reloading intel-ipu6-isys does not exhibit the problem.
> However reloading the sensor driver ov2740 does.
> Is sufficient to reload ov2740 module and start the qcam
> to get those csi2-1 errors.

Bingbu, Sakari, this sounds like a bug in a driver somewhere.

-- 
Regards,

Laurent Pinchart