From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Ricardo Ribalda <ribalda@chromium.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Yong Zhi <yong.zhi@intel.com>, Bingbu Cao <bingbu.cao@intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Chiranjeevi Rapolu <chiranjeevi.rapolu@intel.com>
Subject: Re: [PATCH 0/7] media: ipu3 i2c: Fix v4l2-compliance issues
Date: Wed, 29 Sep 2021 08:53:44 +0800 [thread overview]
Message-ID: <cca17413-e3e4-643a-eca1-694375703fe2@linux.intel.com> (raw)
In-Reply-To: <20210928211033.2415162-1-ribalda@chromium.org>
Ricardo, thanks for your patch.
On 9/29/21 5:10 AM, Ricardo Ribalda wrote:
> Fix some issues found with v4l2-compliance. Tested in Soraka which also
> has some subdevices that had some issues with v4l2-compliance.
>
> Ricardo Ribalda (7):
...
> media: ipu3-cio2: Set valid initial format
> media: ipu3-cio2: imgu_fmt: Handle properly try
> media: ipu3-cio2: VIDIOC_QUERYCAP: Fix bus_info
These 3 should be staging ImgU category, not cio2 :).
> media: dw9714: Add implementation for events
> media: ov13858: Add implementation for events
> media: ov5670: Add implementation for events
>
> drivers/media/i2c/dw9714.c | 14 ++++++++++++--
> drivers/media/i2c/ov13858.c | 11 ++++++++++-
> drivers/media/i2c/ov5670.c | 11 ++++++++++-
> drivers/media/pci/intel/ipu3/ipu3-cio2-main.c | 8 ++++++--
> drivers/staging/media/ipu3/ipu3-v4l2.c | 9 +++++----
> 5 files changed, 43 insertions(+), 10 deletions(-)
>
--
Best regards,
Bingbu Cao
prev parent reply other threads:[~2021-09-29 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 21:10 [PATCH 0/7] media: ipu3 i2c: Fix v4l2-compliance issues Ricardo Ribalda
2021-09-28 21:10 ` [PATCH 1/7] media: ipu3-cio2: Check num_planes and sizes in queue_setup Ricardo Ribalda
2021-09-29 0:54 ` Bingbu Cao
2021-09-28 21:10 ` [PATCH 2/7] media: ipu3-cio2: Set valid initial format Ricardo Ribalda
2021-10-01 9:15 ` Sakari Ailus
2021-09-28 21:10 ` [PATCH 3/7] media: ipu3-cio2: imgu_fmt: Handle properly try Ricardo Ribalda
2021-09-28 21:10 ` [PATCH 4/7] media: ipu3-cio2: VIDIOC_QUERYCAP: Fix bus_info Ricardo Ribalda
2021-09-29 0:55 ` Bingbu Cao
2021-09-28 21:10 ` [PATCH 5/7] media: dw9714: Add implementation for events Ricardo Ribalda
2021-09-28 21:10 ` [PATCH 6/7] media: ov13858: " Ricardo Ribalda
2021-09-28 21:10 ` [PATCH 7/7] media: ov5670: " Ricardo Ribalda
2021-09-29 0:53 ` Bingbu Cao [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=cca17413-e3e4-643a-eca1-694375703fe2@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=chiranjeevi.rapolu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yong.zhi@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.