From: Marco Felsch <m.felsch@pengutronix.de>
To: sakari.ailus@linux.intel.com, mchehab@kernel.org,
robh+dt@kernel.org, Jacopo Mondi <jacopo@jmondi.org>
Cc: devicetree@vger.kernel.org, graphics@pengutronix.de,
linux-media@vger.kernel.org
Subject: [PATCH v2 0/2] media: add Toshiba TC358746 Bridge support
Date: Wed, 19 Jun 2019 17:28:36 +0200 [thread overview]
Message-ID: <20190619152838.25079-1-m.felsch@pengutronix.de> (raw)
Hi,
this is my v2 contains all the review feedback made on my v1 [1].
Since Rob didn't responed to the question how we should handle the
different input/output config I decided to use Jacopo approach since
it is common for mux devices too.
I rebased the patches ontop of media_tree/master so there should be no
conflicts.
Regards,
Marco
[1] https://patchwork.ozlabs.org/cover/1015381/
Marco Felsch (2):
media: dt-bindings: add bindings for Toshiba TC358746
media: tc358746: add Toshiba TC358746 Parallel to CSI-2 bridge driver
.../bindings/media/i2c/toshiba,tc358746.txt | 95 +
MAINTAINERS | 7 +
drivers/media/i2c/Kconfig | 12 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/tc358746.c | 1807 +++++++++++++++++
drivers/media/i2c/tc358746_regs.h | 208 ++
6 files changed, 2130 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,tc358746.txt
create mode 100644 drivers/media/i2c/tc358746.c
create mode 100644 drivers/media/i2c/tc358746_regs.h
--
2.20.1
next reply other threads:[~2019-06-19 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 15:28 Marco Felsch [this message]
2019-06-19 15:28 ` [PATCH v2 1/2] media: dt-bindings: add bindings for Toshiba TC358746 Marco Felsch
2019-07-08 21:17 ` Rob Herring
2019-07-09 11:02 ` Jacopo Mondi
2019-08-26 8:54 ` Sakari Ailus
2019-06-19 15:28 ` [PATCH v2 2/2] media: tc358746: add Toshiba TC358746 Parallel to CSI-2 bridge driver Marco Felsch
2019-06-25 12:27 ` Sakari Ailus
2019-07-29 10:40 ` Marco Felsch
2019-08-20 14:49 ` Marco Felsch
2019-08-26 10:03 ` Sakari Ailus
2020-11-03 17:44 ` Marco Felsch
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=20190619152838.25079-1-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=graphics@pengutronix.de \
--cc=jacopo@jmondi.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.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;
as well as URLs for NNTP newsgroup(s).