Em Mon, 25 Jun 2018 09:48:56 +0000 "Zheng, Jian Xu" <jian.xu.zh...@intel.com> escreveu:
> Hi Mauro, > > > -----Original Message----- > > From: linux-media-ow...@vger.kernel.org [mailto:linux-media- > > ow...@vger.kernel.org] On Behalf Of Mauro Carvalho Chehab > > Sent: Friday, June 22, 2018 5:41 AM > > To: mario.limoncie...@dell.com > > Cc: pa...@ucw.cz; nico...@ndufresne.ca; linux-media@vger.kernel.org; > > sakari.ai...@linux.intel.com; niklas.soderl...@ragnatech.se; Hu, Jerry W > > <jerry.w...@intel.com>; Zheng, Jian Xu <jian.xu.zh...@intel.com> > > Subject: Re: Software-only image processing for Intel "complex" cameras > > > > Em Fri, 22 Jun 2018 06:08:50 +0900 > > Mauro Carvalho Chehab <mchehab+sams...@kernel.org> escreveu: > > > > > Em Thu, 21 Jun 2018 18:58:37 +0000 > > > <mario.limoncie...@dell.com> 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) How does it detect what driver should be loaded for Sensor A and B? Does the ACPI table identifies the sensors? If so, how the driver associates an specific PCI vendor ID with the corresponding sensor settings? > > 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 Thanks, Mauro
