From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: Tomasz Figa <tfiga@chromium.org>,
Bingbu Cao <bingbu.cao@intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
"Qiu, Tian Shu" <tian.shu.qiu@intel.com>
Subject: Re: [PATCH v2] media: staging/intel-ipu3: make imgu use fixed running mode
Date: Mon, 13 Jan 2020 19:53:07 +0200 [thread overview]
Message-ID: <20200113175306.GG5440@paasikivi.fi.intel.com> (raw)
In-Reply-To: <a73250f5-6887-8f1e-3ebf-bf37c23749b7@linux.intel.com>
Hi Bingbu,
On Thu, Jan 09, 2020 at 12:37:07PM +0800, Bingbu Cao wrote:
>
>
> On 1/9/20 12:06 PM, Tomasz Figa wrote:
> > On Thu, Jan 9, 2020 at 12:58 PM Bingbu Cao <bingbu.cao@linux.intel.com> wrote:
> >>
> >>
> >>
> >> On 1/8/20 8:57 PM, Tomasz Figa wrote:
> >>> On Mon, Dec 30, 2019 at 6:21 PM Bingbu Cao <bingbu.cao@intel.com> wrote:
> >>>>
> >>>> Currently, the imgu running mode need user to set by v4l2 ctrl.
> >>>> However, imgu only support 2 pipes and 2 operation modes - video and
> >>>> still. This patch make the first imgu subdev running as video and second
> >>>> one running as still, it will make the user understand easily, it can
> >>>> also cover current camera use cases requirement. The running mode is set
> >>>> during subdev registering, no race-condition after change, so it is safe
> >>>> to change the mode data type to integer.
> >>>>
> >>>> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
> >>>> ---
> >>>> Documentation/media/v4l-drivers/ipu3.rst | 6 +-
> >>>> drivers/staging/media/ipu3/include/intel-ipu3.h | 4 --
> >>>> drivers/staging/media/ipu3/ipu3-v4l2.c | 74 +++----------------------
> >>>> drivers/staging/media/ipu3/ipu3.h | 5 +-
> >>>> 4 files changed, 12 insertions(+), 77 deletions(-)
> >>>>
> >>>
> >>> Doesn't it make it impossible to use two video (aka fast) pipes?
> >> Hi, Tomasz,
> >> Yes, once applying this patch, you can not run two video pipes with same input.
> >> I have no idea what are fast pipes and which scenario need two video pipes if
> >> the driver did not support multiple camera?
> >
> > Processing in video pipes is faster than in still pipes and so one
> > could still want to use two video pipes for lower system load and thus
> > also lower power consumption, even for a single camera scenario, but
> > with ZSL.
> >
> > That said, AFAICT CIO2 wouldn't have problems handling 2 raw captures,
> > so why would we want to prevent anyone from having 2 video pipes for 2
> > different cameras?
> Tomasz, your comments make sense for me. we can not limit the usage.
>
> Sakari,
> Do you have comments on that? Could we revert this patch?
Please send a revert if you feel like it.
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2020-01-13 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 9:26 [PATCH v2] media: staging/intel-ipu3: make imgu use fixed running mode Bingbu Cao
2020-01-08 12:57 ` Tomasz Figa
2020-01-09 4:03 ` Bingbu Cao
2020-01-09 4:06 ` Tomasz Figa
2020-01-09 4:37 ` Bingbu Cao
2020-01-13 17:53 ` 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=20200113175306.GG5440@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=tfiga@chromium.org \
--cc=tian.shu.qiu@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