All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Wu, Wentong" <wentong.wu@intel.com>
Cc: "hdegoede@redhat.com" <hdegoede@redhat.com>,
	"djrscally@gmail.com" <djrscally@gmail.com>,
	"laurent.pinchart@ideasonboard.com" 
	<laurent.pinchart@ideasonboard.com>,
	"bingbu.cao@linux.intel.com" <bingbu.cao@linux.intel.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Wang, Zhifeng" <zhifeng.wang@intel.com>,
	"Ye, Xiang" <xiang.ye@intel.com>,
	"Qiu, Tian Shu" <tian.shu.qiu@intel.com>
Subject: Re: [PATCH v3 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC)
Date: Wed, 29 Mar 2023 10:39:56 +0300	[thread overview]
Message-ID: <ZCPrTJ9Xg2dkxbu2@kekkonen.localdomain> (raw)
In-Reply-To: <MN2PR11MB43182A9175011A4C8E3A31068D899@MN2PR11MB4318.namprd11.prod.outlook.com>

Hi Wentong,

On Wed, Mar 29, 2023 at 12:42:06AM +0000, Wu, Wentong wrote:
> > > > > > > I have no idea what the ipu bridge would be like, but IVSC csi
> > > > > > > bridge can be configured via kconfig to enable/disable.
> > > > > >
> > > > > > Please work out the details with Bingbu.
> > > > >
> > > > > @bingbu.cao@linux.intel.com @Sakari Ailus Please share your design
> > > > > idea
> > > > here.
> > > > > What the ipu bridge would be like?  What's the responsibility of ipu bridge?
> > > >
> > > > I'd expect Bingbu to have patches to turn the current cio2_bridge to
> > > > an ipu_bridge at some point. These should come on top of those patches.
> > >
> > > When will this be ready if you already make the plan? But could you
> > > please help review my other patches except bridge?
> > 
> > Please configure your e-mail client to wrap your lines at most at 74 characters
> > or so.
> > 
> > I think it's binding this all together that is the concern, the individual drivers
> > much less so.
> 
> Thanks, I would remove the csi bridge in next version.
> 
> Ok, the IPU bridge will also cover the bridge between IVSC and sensor.
> 
> BTW, please hans and laurent help take a look the mei_csi and mei_ace
> patch.

I can review them. However they can't be tested without the bridge code in
place. I'm therefore leaning towards merging them all at the same time,
when we know how this looks like in the end and can actually test the
patches.

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2023-03-29  7:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  6:23 [PATCH v3 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC) Wentong Wu
2023-03-27  6:23 ` [PATCH v3 1/3] media: pci: intel: ivsc: Add CSI submodule Wentong Wu
2023-03-27 10:01   ` kernel test robot
2023-03-28 13:59   ` kernel test robot
2023-03-29  8:48   ` Sakari Ailus
2023-03-30  3:58     ` Wu, Wentong
2023-03-30  8:23       ` Sakari Ailus
2023-03-29  8:49   ` Sakari Ailus
2023-03-27  6:23 ` [PATCH v3 2/3] media: pci: intel: ivsc: Add ACE submodule Wentong Wu
2023-03-29  8:03   ` Sakari Ailus
2023-03-30  7:32     ` Wu, Wentong
2023-03-30  8:27       ` Sakari Ailus
2023-03-27  6:23 ` [PATCH v3 3/3] ACPI: delay enumeration of devices with a _DEP pointing to INTC1059 device Wentong Wu
2023-03-27  7:06   ` Sakari Ailus
2023-03-27  7:17     ` Wu, Wentong
2023-03-27  7:32       ` Sakari Ailus
2023-03-27  7:36         ` Wu, Wentong
2023-03-27  7:21 ` [PATCH v3 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC) Sakari Ailus
2023-03-27  7:33   ` Wu, Wentong
2023-03-27  7:49     ` Sakari Ailus
2023-03-27  8:13       ` Wu, Wentong
2023-03-27  9:36         ` Sakari Ailus
2023-03-28  7:32           ` Wu, Wentong
2023-03-28 19:48             ` Sakari Ailus
2023-03-29  0:42               ` Wu, Wentong
2023-03-29  7:39                 ` Sakari Ailus [this message]

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=ZCPrTJ9Xg2dkxbu2@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=tian.shu.qiu@intel.com \
    --cc=wentong.wu@intel.com \
    --cc=xiang.ye@intel.com \
    --cc=zhifeng.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.