public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: "Zheng, Jian Xu" <jian.xu.zheng@intel.com>
Cc: "Mario.Limonciello@dell.com" <Mario.Limonciello@dell.com>,
	"pavel@ucw.cz" <pavel@ucw.cz>,
	"nicolas@ndufresne.ca" <nicolas@ndufresne.ca>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
	"niklas.soderlund@ragnatech.se" <niklas.soderlund@ragnatech.se>,
	"Hu, Jerry W" <jerry.w.hu@intel.com>
Subject: Re: Software-only image processing for Intel "complex" cameras
Date: Mon, 25 Jun 2018 10:10:24 -0300	[thread overview]
Message-ID: <20180625101024.2573892a@coco.lan> (raw)
In-Reply-To: <FA6CF6692DF0B343ABE491A46A2CD0E76C6E491B@SHSMSX101.ccr.corp.intel.com>

Em Mon, 25 Jun 2018 09:48:56 +0000
"Zheng, Jian Xu" <jian.xu.zheng@intel.com> escreveu:

> Hi Mauro,
> 
> > -----Original Message-----
> > From: linux-media-owner@vger.kernel.org [mailto:linux-media-
> > owner@vger.kernel.org] On Behalf Of Mauro Carvalho Chehab
> > Sent: Friday, June 22, 2018 5:41 AM
> > To: Mario.Limonciello@dell.com
> > Cc: pavel@ucw.cz; nicolas@ndufresne.ca; linux-media@vger.kernel.org;
> > sakari.ailus@linux.intel.com; niklas.soderlund@ragnatech.se; Hu, Jerry W
> > <jerry.w.hu@intel.com>; Zheng, Jian Xu <jian.xu.zheng@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+samsung@kernel.org> escreveu:
> >   
> > > Em Thu, 21 Jun 2018 18:58:37 +0000
> > > <Mario.Limonciello@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

  reply	other threads:[~2018-06-25 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 20:38 Software-only image processing for Intel "complex" cameras Pavel Machek
2018-06-20 20:57 ` Nicolas Dufresne
2018-06-20 21:11   ` Pavel Machek
2018-06-21 13:41     ` Mario.Limonciello
2018-06-21 18:49       ` Mauro Carvalho Chehab
2018-06-21 18:58         ` Mario.Limonciello
2018-06-21 21:08           ` Mauro Carvalho Chehab
2018-06-21 21:40             ` Mauro Carvalho Chehab
2018-06-25  9:48               ` Zheng, Jian Xu
2018-06-25 13:10                 ` Mauro Carvalho Chehab [this message]
2018-07-27 10:58                   ` Javier Martinez Canillas
2018-06-23 21:29             ` Pavel Machek
2018-06-21 18:36   ` Mauro Carvalho Chehab
2018-06-29  6:02 ` Tomasz Figa
2018-06-29  9:18   ` Pavel Machek
2018-06-29  9:28     ` Tomasz Figa
2018-06-29 10:52       ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180625101024.2573892a@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=Mario.Limonciello@dell.com \
    --cc=jerry.w.hu@intel.com \
    --cc=jian.xu.zheng@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=pavel@ucw.cz \
    --cc=sakari.ailus@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox