From: Louis Kuo <louis.kuo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: hans.verkuil-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org,
laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org,
tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
keiichiw-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sean.Cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Rynn.Wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
holmes.chiou-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Jerry-ch.Chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
jungo.lin-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
sj.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
yuzhao-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
zwisler-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
christie.yu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
frederic.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC PATCH V1 0/4] media: support Mediatek sensor interface driver
Date: Thu, 14 Mar 2019 22:18:32 +0800 [thread overview]
Message-ID: <1552573116-21421-1-git-send-email-louis.kuo@mediatek.com> (raw)
Hello,
This is the RFC patch adding Sensor Inferface(seninf) driver on
Mediatek mt8183 SoC, which will be used in camera features on CrOS application.
It belongs to the first Mediatek's camera driver series based on V4L2 and media controller framework.
I posted the main part of the seninf driver as RFC to discuss first and would like some review comments
on the overall structure of the driver.
The driver is implemented with V4L2 framework.
1. Register as a V4L2 sub-device.
2. Only one entity with sink pads linked to camera sensors for choosing desired camera sensor by setup link
and with source pads linked to cam-io for routing different types of decoded packet datas to PASS1 driver
to generate sensor image frame and meta-data.
The overall file structure of the seninf driver is as following:
* mtk_seninf.c: Implement software and HW control flow of seninf driver.
* seninf_drv_def.h: Define data structure and enumeration.
* seninf_reg.h: Define HW register R/W macros and HW register names.
[ v1: use recommended coding style, remove unused function, remove redundant code, do error handling ]
Louis Kuo (4):
media: platform: mtk-isp: Add Mediatek sensor interface driver
media: platform: Add Mediatek sensor interface driver KConfig
dt-bindings: mt8183: Add sensor interface dt-bindings
dts: arm64: mt8183: Add sensor interface nodes
.../devicetree/bindings/media/mediatek-seninf.txt | 52 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 34 +
drivers/media/platform/Makefile | 2 +
drivers/media/platform/mtk-isp/Kconfig | 16 +
drivers/media/platform/mtk-isp/Makefile | 14 +
drivers/media/platform/mtk-isp/isp_50/Makefile | 17 +
.../media/platform/mtk-isp/isp_50/seninf/Makefile | 4 +
.../platform/mtk-isp/isp_50/seninf/mtk_seninf.c | 1246 ++++++++++++++++++++
.../mtk-isp/isp_50/seninf/seninf_drv_def.h | 201 ++++
.../platform/mtk-isp/isp_50/seninf/seninf_reg.h | 992 ++++++++++++++++
10 files changed, 2578 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt
create mode 100644 drivers/media/platform/mtk-isp/Kconfig
create mode 100644 drivers/media/platform/mtk-isp/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/mtk_seninf.c
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_drv_def.h
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_reg.h
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
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>
Subject: [RFC PATCH V1 0/4] media: support Mediatek sensor interface driver
Date: Thu, 14 Mar 2019 22:18:32 +0800 [thread overview]
Message-ID: <1552573116-21421-1-git-send-email-louis.kuo@mediatek.com> (raw)
Hello,
This is the RFC patch adding Sensor Inferface(seninf) driver on
Mediatek mt8183 SoC, which will be used in camera features on CrOS application.
It belongs to the first Mediatek's camera driver series based on V4L2 and media controller framework.
I posted the main part of the seninf driver as RFC to discuss first and would like some review comments
on the overall structure of the driver.
The driver is implemented with V4L2 framework.
1. Register as a V4L2 sub-device.
2. Only one entity with sink pads linked to camera sensors for choosing desired camera sensor by setup link
and with source pads linked to cam-io for routing different types of decoded packet datas to PASS1 driver
to generate sensor image frame and meta-data.
The overall file structure of the seninf driver is as following:
* mtk_seninf.c: Implement software and HW control flow of seninf driver.
* seninf_drv_def.h: Define data structure and enumeration.
* seninf_reg.h: Define HW register R/W macros and HW register names.
[ v1: use recommended coding style, remove unused function, remove redundant code, do error handling ]
Louis Kuo (4):
media: platform: mtk-isp: Add Mediatek sensor interface driver
media: platform: Add Mediatek sensor interface driver KConfig
dt-bindings: mt8183: Add sensor interface dt-bindings
dts: arm64: mt8183: Add sensor interface nodes
.../devicetree/bindings/media/mediatek-seninf.txt | 52 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 34 +
drivers/media/platform/Makefile | 2 +
drivers/media/platform/mtk-isp/Kconfig | 16 +
drivers/media/platform/mtk-isp/Makefile | 14 +
drivers/media/platform/mtk-isp/isp_50/Makefile | 17 +
.../media/platform/mtk-isp/isp_50/seninf/Makefile | 4 +
.../platform/mtk-isp/isp_50/seninf/mtk_seninf.c | 1246 ++++++++++++++++++++
.../mtk-isp/isp_50/seninf/seninf_drv_def.h | 201 ++++
.../platform/mtk-isp/isp_50/seninf/seninf_reg.h | 992 ++++++++++++++++
10 files changed, 2578 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt
create mode 100644 drivers/media/platform/mtk-isp/Kconfig
create mode 100644 drivers/media/platform/mtk-isp/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/mtk_seninf.c
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_drv_def.h
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_reg.h
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
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: devicetree@vger.kernel.org, Sean.Cheng@mediatek.com,
Rynn.Wu@mediatek.com, srv_heupstream@mediatek.com,
holmes.chiou@mediatek.com, Jerry-ch.Chen@mediatek.com,
jungo.lin@mediatek.com, sj.huang@mediatek.com,
yuzhao@chromium.org, linux-mediatek@lists.infradead.org,
zwisler@chromium.org, christie.yu@mediatek.com,
frederic.chen@mediatek.com, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [RFC PATCH V1 0/4] media: support Mediatek sensor interface driver
Date: Thu, 14 Mar 2019 22:18:32 +0800 [thread overview]
Message-ID: <1552573116-21421-1-git-send-email-louis.kuo@mediatek.com> (raw)
Hello,
This is the RFC patch adding Sensor Inferface(seninf) driver on
Mediatek mt8183 SoC, which will be used in camera features on CrOS application.
It belongs to the first Mediatek's camera driver series based on V4L2 and media controller framework.
I posted the main part of the seninf driver as RFC to discuss first and would like some review comments
on the overall structure of the driver.
The driver is implemented with V4L2 framework.
1. Register as a V4L2 sub-device.
2. Only one entity with sink pads linked to camera sensors for choosing desired camera sensor by setup link
and with source pads linked to cam-io for routing different types of decoded packet datas to PASS1 driver
to generate sensor image frame and meta-data.
The overall file structure of the seninf driver is as following:
* mtk_seninf.c: Implement software and HW control flow of seninf driver.
* seninf_drv_def.h: Define data structure and enumeration.
* seninf_reg.h: Define HW register R/W macros and HW register names.
[ v1: use recommended coding style, remove unused function, remove redundant code, do error handling ]
Louis Kuo (4):
media: platform: mtk-isp: Add Mediatek sensor interface driver
media: platform: Add Mediatek sensor interface driver KConfig
dt-bindings: mt8183: Add sensor interface dt-bindings
dts: arm64: mt8183: Add sensor interface nodes
.../devicetree/bindings/media/mediatek-seninf.txt | 52 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 34 +
drivers/media/platform/Makefile | 2 +
drivers/media/platform/mtk-isp/Kconfig | 16 +
drivers/media/platform/mtk-isp/Makefile | 14 +
drivers/media/platform/mtk-isp/isp_50/Makefile | 17 +
.../media/platform/mtk-isp/isp_50/seninf/Makefile | 4 +
.../platform/mtk-isp/isp_50/seninf/mtk_seninf.c | 1246 ++++++++++++++++++++
.../mtk-isp/isp_50/seninf/seninf_drv_def.h | 201 ++++
.../platform/mtk-isp/isp_50/seninf/seninf_reg.h | 992 ++++++++++++++++
10 files changed, 2578 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mediatek-seninf.txt
create mode 100644 drivers/media/platform/mtk-isp/Kconfig
create mode 100644 drivers/media/platform/mtk-isp/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/Makefile
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/mtk_seninf.c
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_drv_def.h
create mode 100644 drivers/media/platform/mtk-isp/isp_50/seninf/seninf_reg.h
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-03-14 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 14:18 Louis Kuo [this message]
2019-03-14 14:18 ` [RFC PATCH V1 0/4] media: support Mediatek sensor interface driver Louis Kuo
2019-03-14 14:18 ` Louis Kuo
[not found] ` <1552573116-21421-1-git-send-email-louis.kuo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-14 14:18 ` [RFC PATCH V1 1/4] media: platform: mtk-isp: Add " Louis Kuo
2019-03-14 14:18 ` Louis Kuo
2019-03-14 14:18 ` Louis Kuo
2019-05-03 0:37 ` Drew Davenport
2019-03-14 14:18 ` [RFC PATCH V1 2/4] media: platform: Add Mediatek sensor interface driver KConfig Louis Kuo
2019-03-14 14:18 ` Louis Kuo
2019-03-14 14:18 ` Louis Kuo
2019-03-14 14:18 ` [RFC PATCH V1 4/4] dts: arm64: mt8183: Add sensor interface nodes Louis Kuo
2019-03-14 14:18 ` Louis Kuo
2019-03-14 14:18 ` Louis Kuo
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 ` Louis Kuo
2019-03-14 14:18 ` 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-1-git-send-email-louis.kuo@mediatek.com \
--to=louis.kuo-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=Jerry-ch.Chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=Rynn.Wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=Sean.Cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=christie.yu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=frederic.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=hans.verkuil-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=holmes.chiou-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=jungo.lin-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=keiichiw-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mchehab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sj.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=yuzhao-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=zwisler-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.