From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: Jacopo Mondi <jacopo@jmondi.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Steve Longerbeam <slongerbeam@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org,
Hugues Fruchet <hugues.fruchet@st.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar <prabhakar.csengg@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 0/2] media: ov5640 feature enhancement and fixes
Date: Fri, 31 Jul 2020 10:24:45 +0100 [thread overview]
Message-ID: <1596187487-31403-1-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
Hi All,
This patch series fixes DVP support and enables BT656 mode in
the driver.
Cheers,
Prabhakar
Lad Prabhakar (2):
media: i2c: ov5640: Enable data pins on startup for DVP mode
media: i2c: ov5640: Add support for BT656 mode
drivers/media/i2c/ov5640.c | 263 +++++++++++++++++++++++----------------------
1 file changed, 134 insertions(+), 129 deletions(-)
--
2.7.4
next reply other threads:[~2020-07-31 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:24 Lad Prabhakar [this message]
2020-07-31 9:24 ` [PATCH 1/2] media: i2c: ov5640: Enable data pins on startup for DVP mode Lad Prabhakar
2020-07-31 13:03 ` Sakari Ailus
2020-07-31 13:18 ` Lad, Prabhakar
2020-07-31 15:19 ` Sakari Ailus
2020-07-31 15:23 ` Lad, Prabhakar
2020-07-31 15:31 ` Laurent Pinchart
2020-08-01 8:51 ` Lad, Prabhakar
2020-07-31 15:27 ` Laurent Pinchart
2020-08-01 8:46 ` Lad, Prabhakar
2020-07-31 9:24 ` [PATCH 2/2] media: i2c: ov5640: Add support for BT656 mode Lad Prabhakar
2020-07-31 15:23 ` Sakari Ailus
2020-07-31 15:28 ` Lad, Prabhakar
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=1596187487-31403-1-git-send-email-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=hugues.fruchet@st.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=slongerbeam@gmail.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;
as well as URLs for NNTP newsgroup(s).