RE: Software-only image processing for Intel "complex" cameras

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mauro,

> -----Original Message-----
> From: linux-media-owner@xxxxxxxxxxxxxxx [mailto:linux-media-
> owner@xxxxxxxxxxxxxxx] On Behalf Of Mauro Carvalho Chehab
> Sent: Friday, June 22, 2018 5:41 AM
> To: Mario.Limonciello@xxxxxxxx
> Cc: pavel@xxxxxx; nicolas@xxxxxxxxxxxx; linux-media@xxxxxxxxxxxxxxx;
> sakari.ailus@xxxxxxxxxxxxxxx; niklas.soderlund@xxxxxxxxxxxx; Hu, Jerry W
> <jerry.w.hu@xxxxxxxxx>; Zheng, Jian Xu <jian.xu.zheng@xxxxxxxxx>
> Subject: Re: Software-only image processing for Intel "complex" cameras
> 
> Em Fri, 22 Jun 2018 06:08:50 +0900
> Mauro Carvalho Chehab <mchehab+samsung@xxxxxxxxxx> escreveu:
> 
> > Em Thu, 21 Jun 2018 18:58:37 +0000
> > <Mario.Limonciello@xxxxxxxx> escreveu:
> >
> Jerry/Jian,
> 
> Could you please shed a light about how a Dell 5285 hardware would be
> detected by the IPU3 driver and what MC graph is created by the current
> driver?

Sure, Mauro. I need to check the information on the Dell 5285.
IPU3 driver are detected by PCI vendor id and device id.

IPU3 CIO2 MC graph is:
Sensor A -> IPU3 CSI2 0(subdev) -> IPU3 CIO2 0 (video node)
Sensor B -> IPU3 CSI2 1(subdev) -> IPU3 CIO2 1 (video node)

IPU3 IMGu MC graph is:
IMGu subdev inputs:
ipu3-imgu input [Pad0] => ipu3-imgu [Pad0]
ipu3-imgu parameters [Pad0] => ipu3-imgu [Pad1]

IMGu subdev outputs:
ipu3-imgu [Pad2]  => ipu3-imgu output [Pad0] 
ipu3-imgu [Pad3]  => ipu3-imgu viewfinder [Pad0] 
ipu3-imgu [Pad4]  => ipu3-imgu postview [Pad0] 
ipu3-imgu [Pad5]  => ipu3-imgu 3a stat [Pad0]

Best Regards,
Jianxu(Clive) Zheng



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux