From: Wenyou Yang <wenyou.yang@microchip.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
<linux-kernel@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
<linux-arm-kernel@lists.infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Wenyou Yang <wenyou.yang@microchip.com>
Subject: [PATCH v4 0/3] media: ov7670: Add entity init and power operation
Date: Mon, 18 Sep 2017 14:45:11 +0800 [thread overview]
Message-ID: <20170918064514.6841-1-wenyou.yang@microchip.com> (raw)
This patch set is to add the media entity pads initialization,
the s_power operation and get_fmt callback support.
Changes in v4:
- Fix the build error when not enabling Media Controller API option.
- Fix the build error when not enabling V4L2 sub-device userspace API option.
Changes in v3:
- Keep tried format info in the try_fmt member of
v4l2_subdev__pad_config struct.
- Add the internal_ops callback to set default format.
Changes in v2:
- Add the patch to support the get_fmt ops.
- Remove the redundant invoking ov7670_init_gpio().
Wenyou Yang (3):
media: ov7670: Add entity pads initialization
media: ov7670: Add the get_fmt callback
media: ov7670: Add the s_power operation
drivers/media/i2c/ov7670.c | 128 ++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 121 insertions(+), 7 deletions(-)
--
2.13.0
next reply other threads:[~2017-09-18 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 6:45 Wenyou Yang [this message]
2017-09-18 6:45 ` [PATCH v4 1/3] media: ov7670: Add entity pads initialization Wenyou Yang
2017-09-18 6:45 ` [PATCH v4 2/3] media: ov7670: Add the get_fmt callback Wenyou Yang
2017-09-18 7:35 ` kbuild test robot
2017-09-18 7:36 ` Sakari Ailus
2017-09-18 9:25 ` Yang, Wenyou
2017-09-18 6:45 ` [PATCH v4 3/3] media: ov7670: Add the s_power operation Wenyou Yang
2017-09-18 7:35 ` Sakari Ailus
2017-09-18 9:26 ` Yang, Wenyou
2017-09-18 13:26 ` Sakari Ailus
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=20170918064514.6841-1-wenyou.yang@microchip.com \
--to=wenyou.yang@microchip.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=nicolas.ferre@microchip.com \
--cc=sakari.ailus@iki.fi \
/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