From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "mchehab@kernel.org" <mchehab@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"Andy Hsieh (謝智皓)" <Andy.Hsieh@mediatek.com>,
"jstephan@baylibre.com" <jstephan@baylibre.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Louis Kuo (郭德寧)" <louis.kuo@mediatek.com>,
"fsylvestre@baylibre.com" <fsylvestre@baylibre.com>,
"pnguyen@baylibre.com" <pnguyen@baylibre.com>
Subject: Re: [PATCH v5 3/5] media: platform: mediatek: isp_30: add mediatek ISP3.0 sensor interface
Date: Thu, 18 Jul 2024 02:36:38 +0000 [thread overview]
Message-ID: <22178efb11985153e99cee158102b9da50efeff4.camel@mediatek.com> (raw)
In-Reply-To: <20240704-add-mtk-isp-3-0-support-v5-3-bfccccc5ec21@baylibre.com>
Hi, Julien:
On Thu, 2024-07-04 at 15:36 +0200, Julien Stephan wrote:
>
> External email : Please do not click links or open attachments until you have verified the sender or the content.
> From: Louis Kuo <louis.kuo@mediatek.com>
>
> This will add the mediatek ISP3.0 seninf (sensor interface) driver found
> on several Mediatek SoCs such as the mt8365.
>
> Then seninf module has 4 physical CSI-2 inputs. Depending on the soc they
> may not be all connected.
>
> Signed-off-by: Louis Kuo <louis.kuo@mediatek.com>
> Signed-off-by: Phi-bang Nguyen <pnguyen@baylibre.com>
> Signed-off-by: Florian Sylvestre <fsylvestre@baylibre.com>
> Co-developed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Co-developed-by: Julien Stephan <jstephan@baylibre.com>
> Signed-off-by: Julien Stephan <jstephan@baylibre.com>
> ---
> MAINTAINERS | 1 +
> drivers/media/platform/mediatek/Kconfig | 1 +
> drivers/media/platform/mediatek/Makefile | 1 +
> drivers/media/platform/mediatek/isp/Kconfig | 2 +
> drivers/media/platform/mediatek/isp/Makefile | 3 +
> drivers/media/platform/mediatek/isp/isp_30/Kconfig | 16 +
> .../media/platform/mediatek/isp/isp_30/Makefile | 3 +
> .../platform/mediatek/isp/isp_30/seninf/Makefile | 5 +
> .../mediatek/isp/isp_30/seninf/mtk_seninf.c | 1576 ++++++++++++++++++++
> .../mediatek/isp/isp_30/seninf/mtk_seninf_reg.h | 117 ++
I think you could put mtk_seninf.c and mtk_seninf_reg.h in
drivers/media/platform/mediatek/isp. The seninf driver has only two
files, so it's not necessary to create a folder 'seninf' for only two
files. And for isp_30, we have no any information how many difference
with other isp_xx, for example isp_40, if seninf driver in isp_30 and
in isp_40 has only 10% difference, it's not necessary to duplicate the
90% common code in different folder. So initially, just place the
seninf driver in mediatek/isp folder. When other SoC seninf driver
upstream, we would have enough information to decide to generate new
file or new folder for new SoC.
Regards,
CK
next prev parent reply other threads:[~2024-07-18 2:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 13:36 [PATCH v5 0/5] Add Mediatek ISP3.0 Julien Stephan
2024-07-04 13:36 ` [PATCH v5 1/5] dt-bindings: media: add mediatek ISP3.0 sensor interface Julien Stephan
2024-07-04 16:26 ` Conor Dooley
2024-07-05 7:50 ` Julien Stephan
2024-07-05 9:23 ` Conor Dooley
2024-07-05 9:35 ` Julien Stephan
2024-07-04 13:36 ` [PATCH v5 2/5] dt-bindings: media: add mediatek ISP3.0 camsv Julien Stephan
2024-07-04 16:29 ` Conor Dooley
2024-07-04 22:51 ` Laurent Pinchart
2024-07-04 13:36 ` [PATCH v5 3/5] media: platform: mediatek: isp_30: add mediatek ISP3.0 sensor interface Julien Stephan
2024-07-18 2:36 ` CK Hu (胡俊光) [this message]
2024-07-18 2:44 ` CK Hu (胡俊光)
2024-07-29 12:46 ` Julien Stephan
2024-07-30 2:11 ` CK Hu (胡俊光)
2024-07-04 13:36 ` [PATCH v5 4/5] media: platform: mediatek: isp_30: add mediatek ISP3.0 camsv Julien Stephan
2024-07-18 2:54 ` CK Hu (胡俊光)
2024-07-29 13:40 ` Julien Stephan
2024-07-29 14:14 ` Laurent Pinchart
2024-07-30 2:39 ` CK Hu (胡俊光)
2024-07-18 2:59 ` CK Hu (胡俊光)
2024-07-18 3:26 ` CK Hu (胡俊光)
2024-07-18 3:32 ` CK Hu (胡俊光)
2024-07-30 7:25 ` Markus Elfring
2024-07-30 7:46 ` Markus Elfring
2024-07-04 13:36 ` [PATCH v5 5/5] arm64: dts: mediatek: mt8365: Add support for camera Julien Stephan
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=22178efb11985153e99cee158102b9da50efeff4.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Andy.Hsieh@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fsylvestre@baylibre.com \
--cc=jstephan@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=pnguyen@baylibre.com \
--cc=robh@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).