linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petko Manolov <petko.manolov@konsulko.com>
To: linux-media@vger.kernel.org
Cc: Petko Manolov <petko.manolov@konsulko.com>
Subject: [PATCH v4 0/1] media: ovm6211: Adds support for OVM6211
Date: Sun, 23 Jan 2022 16:21:33 +0200	[thread overview]
Message-ID: <20220123142134.3074180-1-petko.manolov@konsulko.com> (raw)

v4: More unused header files removed, use media_entity_cleanup() where
necessary and some other minor cleanups.

v3: As usual, not everything is perfect, hence v3.  The patch set is now merged
into one big patch, redundant code was removed and the end result tested on the
board.  DT bindings are coming some time later.

v2: Removes an unused function (ovm6211_set_pix_clk) and this patch series is
now based on media/master; Didn't receive any comments about the RFC version,
thus i assume everything is perfect... :P

This patch adds ovm6211 driver into the staging directory.  It also creates
media/i2c entry, where ovm6211.c lives for now, to mimic the generic media
source tree.

Petko Manolov (1):
  media: ovm6211: Adds support for OVM6211

 drivers/media/i2c/Kconfig   |   10 +
 drivers/media/i2c/Makefile  |    1 +
 drivers/media/i2c/ovm6211.c | 1032 +++++++++++++++++++++++++++++++++++
 3 files changed, 1043 insertions(+)
 create mode 100644 drivers/media/i2c/ovm6211.c


base-commit: 68b9bcc8a534cd11fe55f8bc82f948aae7d81b3c
-- 
2.30.2


             reply	other threads:[~2022-01-23 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 14:21 Petko Manolov [this message]
2022-01-23 14:21 ` [PATCH v4 1/1] media: ovm6211: Adds support for OVM6211 Petko Manolov
2022-01-23 19:06   ` kernel test robot
2022-02-02 13:34   ` 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=20220123142134.3074180-1-petko.manolov@konsulko.com \
    --to=petko.manolov@konsulko.com \
    --cc=linux-media@vger.kernel.org \
    /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).