From: Louis Kuo <louis.kuo@mediatek.com>
To: <hans.verkuil@cisco.com>,
<laurent.pinchart+renesas@ideasonboard.com>, <tfiga@chromium.org>,
<keiichiw@chromium.org>, <matthias.bgg@gmail.com>,
<mchehab@kernel.org>
Cc: <yuzhao@chromium.org>, <zwisler@chromium.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>, <Sean.Cheng@mediatek.com>,
<sj.huang@mediatek.com>, <christie.yu@mediatek.com>,
<holmes.chiou@mediatek.com>, <frederic.chen@mediatek.com>,
<Jerry-ch.Chen@mediatek.com>, <jungo.lin@mediatek.com>,
<Rynn.Wu@mediatek.com>, <linux-media@vger.kernel.org>,
<srv_heupstream@mediatek.com>, <devicetree@vger.kernel.org>,
Louis Kuo <louis.kuo@mediatek.com>
Subject: [RFC PATCH V1 2/4] media: platform: Add Mediatek sensor interface driver KConfig
Date: Thu, 14 Mar 2019 22:18:34 +0800 [thread overview]
Message-ID: <1552573116-21421-3-git-send-email-louis.kuo@mediatek.com> (raw)
In-Reply-To: <1552573116-21421-1-git-send-email-louis.kuo@mediatek.com>
This patch adds KConfig for sensor interface driver. Sensor interface driver
is a MIPI-CSI2 host driver, namely, a HW camera interface controller.
It support a widely adopted, simple, high-speed protocol primarily intended
for point-to-point image and video transmission between cameras and host
devices.
Signed-off-by: Louis Kuo <louis.kuo@mediatek.com>
---
drivers/media/platform/mtk-isp/Kconfig | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 drivers/media/platform/mtk-isp/Kconfig
diff --git a/drivers/media/platform/mtk-isp/Kconfig b/drivers/media/platform/mtk-isp/Kconfig
new file mode 100644
index 0000000..c665fa1
--- /dev/null
+++ b/drivers/media/platform/mtk-isp/Kconfig
@@ -0,0 +1,16 @@
+config MTK_SENINF
+ bool "Mediatek mipi csi2 driver"
+ depends on VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
+ depends on MEDIA_CAMERA_SUPPORT
+ select V4L2_FWNODE
+
+ default n
+ help
+ This driver provides a mipi-csi2 host driver used as a
+ interface to connect camera with Mediatek's
+ MT8183 SOCs. It is able to handle multiple cameras
+ at the same time.
+
+ Choose y if you want to use Mediatek SoCs to create image
+ capture application such as video recording and still image
+ capture.
--
1.9.1
next prev parent reply other threads:[~2019-03-14 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 14:18 [RFC PATCH V1 0/4] media: support Mediatek sensor interface driver Louis Kuo
2019-03-14 14:18 ` [RFC PATCH V1 1/4] media: platform: mtk-isp: Add " Louis Kuo
2019-05-03 0:37 ` Drew Davenport
2019-03-14 14:18 ` Louis Kuo [this message]
2019-03-14 14:18 ` [RFC PATCH V1 3/4] dt-bindings: mt8183: Add sensor interface dt-bindings Louis Kuo
2019-03-14 14:18 ` [RFC PATCH V1 4/4] dts: arm64: mt8183: Add sensor interface nodes Louis Kuo
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=1552573116-21421-3-git-send-email-louis.kuo@mediatek.com \
--to=louis.kuo@mediatek.com \
--cc=Jerry-ch.Chen@mediatek.com \
--cc=Rynn.Wu@mediatek.com \
--cc=Sean.Cheng@mediatek.com \
--cc=christie.yu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=frederic.chen@mediatek.com \
--cc=hans.verkuil@cisco.com \
--cc=holmes.chiou@mediatek.com \
--cc=jungo.lin@mediatek.com \
--cc=keiichiw@chromium.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=yuzhao@chromium.org \
--cc=zwisler@chromium.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).