From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Conor Dooley <conor@kernel.org>
Cc: Julien Stephan <jstephan@baylibre.com>,
Andy Hsieh <andy.hsieh@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Phi-bang Nguyen <pnguyen@baylibre.com>
Subject: Re: [PATCH v5 2/5] dt-bindings: media: add mediatek ISP3.0 camsv
Date: Fri, 5 Jul 2024 01:51:56 +0300 [thread overview]
Message-ID: <20240704225156.GE10099@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20240704-unpopular-afraid-95f2cc570f14@spud>
On Thu, Jul 04, 2024 at 05:29:59PM +0100, Conor Dooley wrote:
> On Thu, Jul 04, 2024 at 03:36:41PM +0200, Julien Stephan wrote:
> > From: Phi-bang Nguyen <pnguyen@baylibre.com>
> >
> > This adds the bindings, for the ISP3.0 camsv module embedded in
> > some Mediatek SoC, such as the mt8365
> >
> > Signed-off-by: Phi-bang Nguyen <pnguyen@baylibre.com>
> > Link: https://lore.kernel.org/r/20230807094940.329165-4-jstephan@baylibre.com
>
> Another confusing link tag, why is it here?
>
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > + #include <dt-bindings/clock/mediatek,mt8365-clk.h>
> > + #include <dt-bindings/memory/mediatek,mt8365-larb-port.h>
> > + #include <dt-bindings/power/mediatek,mt8365-power.h>
> > +
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + camsv1: camsv@15050000 {
>
> Didn't Krzysztof already comment about the node name here?
> Additionally, the "camsv1" label doest appear to be used, so should be
> dropped.
You're right about the label, it should be dropped. Regarding the name,
as far as I understand, Krzysztof was fine with specific names when no
generic alternative can be easily found, which I think is the case here.
If my understanding is incorrect, could someone help finding a better
name ?
> > + compatible = "mediatek,mt8365-camsv";
> > + reg = <0 0x15050000 0 0x0040>,
> > + <0 0x15050208 0 0x0020>,
> > + <0 0x15050400 0 0x0100>;
> > + interrupts = <GIC_SPI 186 IRQ_TYPE_LEVEL_LOW>;
> > + clocks = <&camsys CLK_CAM>,
> > + <&camsys CLK_CAMTG>,
> > + <&camsys CLK_CAMSV0>;
> > + clock-names = "cam", "camtg", "camsv";
> > + iommus = <&iommu M4U_PORT_CAM_IMGO>;
> > + power-domains = <&spm MT8365_POWER_DOMAIN_CAM>;
> > +
> > + ports {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + port@0 {
> > + reg = <0>;
> > + camsv1_endpoint: endpoint {
> > + remote-endpoint = <&seninf_camsv1_endpoint>;
> > + };
> > + };
> > + };
> > + };
> > + };
> > +...
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 6bd7df1c3e08..9ac8c08ba692 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -14163,6 +14163,7 @@ M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > M: Julien Stephan <jstephan@baylibre.com>
> > M: Andy Hsieh <andy.hsieh@mediatek.com>
> > S: Supported
> > +F: Documentation/devicetree/bindings/media/mediatek,mt8365-camsv.yaml
> > F: Documentation/devicetree/bindings/media/mediatek,mt8365-seninf.yaml
> >
> > MEDIATEK SMI DRIVER
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-07-04 22:52 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 [this message]
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 (胡俊光)
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=20240704225156.GE10099@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andy.hsieh@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jstephan@baylibre.com \
--cc=krzk+dt@kernel.org \
--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=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