From: Michael Riesch <michael.riesch@wolfvision.net>
To: Rob Herring <robh@kernel.org>
Cc: "Mehdi Djait" <mehdi.djait@linux.intel.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Nicolas Dufresne" <nicolas@ndufresne.ca>,
"Sebastian Fricke" <sebastian.fricke@collabora.com>,
"Alexander Shiyan" <eagle.alexander923@gmail.com>,
"Val Packett" <val@packett.cool>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 3/6] media: dt-bindings: media: add bindings for rockchip rk3568 vicap
Date: Tue, 7 Jan 2025 12:07:42 +0100 [thread overview]
Message-ID: <88f8feee-9cac-47d7-9a8d-3c118e26d124@wolfvision.net> (raw)
In-Reply-To: <20241230200837.GA2477354-robh@kernel.org>
Hi Rob,
On 12/30/24 21:08, Rob Herring wrote:
> On Tue, Dec 17, 2024 at 04:55:15PM +0100, Michael Riesch wrote:
> [...]
>> + ports:
>> + $ref: /schemas/graph.yaml#/properties/ports
>> +
>> + properties:
>> + port@0:
>> + $ref: /schemas/graph.yaml#/$defs/port-base
>> + unevaluatedProperties: false
>> + description: input port on the parallel interface
>
> What about the CSI-2 interface?
If it is OK to add it to binding already although there is nothing in
the driver code that uses it, I will be happy to add it in v3.
Otherwise, I'll add it together with the actual MIPI CSI-2 support.
>
>> [...]
>> +examples:
>> + - |
>> + #include <dt-bindings/clock/rk3568-cru.h>
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> + #include <dt-bindings/power/rk3568-power.h>
>> + #include <dt-bindings/media/video-interfaces.h>
>> +
>> + parent {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> +
>> + vicap: video-capture@fdfe0000 {
>> + compatible = "rockchip,rk3568-vicap";
>> + reg = <0x0 0xfdfe0000 0x0 0x200>;
>> + interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
>> + assigned-clocks = <&cru DCLK_VICAP>;
>> + assigned-clock-rates = <300000000>;
>> + clocks = <&cru ACLK_VICAP>, <&cru HCLK_VICAP>,
>> + <&cru DCLK_VICAP>, <&cru ICLK_VICAP_G>;
>> + clock-names = "aclk", "hclk", "dclk", "iclk";
>> + iommus = <&vicap_mmu>;
>> + power-domains = <&power RK3568_PD_VI>;
>> + resets = <&cru SRST_A_VICAP>, <&cru SRST_H_VICAP>,
>> + <&cru SRST_D_VICAP>, <&cru SRST_P_VICAP>,
>> + <&cru SRST_I_VICAP>;
>> + reset-names = "arst", "hrst", "drst", "prst", "irst";
>> + rockchip,grf = <&grf>;
>> +
>> + ports {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + vicap_dvp: port@0 {
>> + reg = <0>;
>> +
>> + vicap_dvp_input: endpoint {
>> + bus-type = <MEDIA_BUS_TYPE_BT656>;
>> + bus-width = <16>;
>> + pclk-sample = <MEDIA_PCLK_SAMPLE_DUAL_EDGE>;
>> + remote-endpoint = <&it6801_output>;
>> + };
>> + };
>> +
>> + vicap_mipi: port@1 {
>> + reg = <1>;
>> + };
>> + };
>> + };
>> +
>> + vicap_mmu: iommu@fdfe0800 {
>> + compatible = "rockchip,rk3568-iommu";
>
> Not part of this binding, so drop this node.
Ack, will remove in v3.
Thanks and regards,
Michael
>
>> + reg = <0x0 0xfdfe0800 0x0 0x100>;
>> + interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&cru ACLK_VICAP>, <&cru HCLK_VICAP>;
>> + clock-names = "aclk", "iface";
>> + #iommu-cells = <0>;
>> + power-domains = <&power RK3568_PD_VI>;
>> + rockchip,disable-mmu-reset;
>> + };
>> + };
>> +...
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 1138c8858bc7..8dbeb2927a08 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -20223,6 +20223,7 @@ M: Michael Riesch <michael.riesch@wolfvision.net>
>> L: linux-media@vger.kernel.org
>> S: Maintained
>> F: Documentation/devicetree/bindings/media/rockchip,px30-vip.yaml
>> +F: Documentation/devicetree/bindings/media/rockchip,rk3568-vicap.yaml
>>
>> ROCKCHIP CRYPTO DRIVERS
>> M: Corentin Labbe <clabbe@baylibre.com>
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2025-01-07 11:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 15:55 [PATCH v2 0/6] media: rockchip: add a driver for the rockchip camera interface (cif) Michael Riesch
2024-12-17 15:55 ` [PATCH v2 1/6] media: dt-bindings: media: video-interfaces: add defines for sampling modes Michael Riesch
2024-12-17 15:55 ` [PATCH v2 2/6] media: dt-bindings: media: add bindings for rockchip px30 vip Michael Riesch
2024-12-30 20:00 ` Rob Herring (Arm)
2024-12-17 15:55 ` [PATCH v2 3/6] media: dt-bindings: media: add bindings for rockchip rk3568 vicap Michael Riesch
2024-12-30 20:08 ` Rob Herring
2025-01-07 11:07 ` Michael Riesch [this message]
2024-12-17 15:55 ` [PATCH v2 4/6] media: rockchip: add a driver for the rockchip camera interface (cif) Michael Riesch
2025-01-09 10:07 ` Sakari Ailus
2025-01-09 13:05 ` Michael Riesch
2025-01-09 17:06 ` Sakari Ailus
2025-01-10 9:12 ` Michael Riesch
2025-01-10 10:37 ` Sakari Ailus
2024-12-17 15:55 ` [PATCH v2 5/6] arm64: dts: rockchip: add the vip node to px30 Michael Riesch
2024-12-17 15:55 ` [PATCH v2 6/6] arm64: dts: rockchip: add vicap node to rk356x Michael Riesch
2025-01-09 17:12 ` [PATCH v2 0/6] media: rockchip: add a driver for the rockchip camera interface (cif) Laurent Pinchart
2025-01-10 8:48 ` Michael Riesch
2025-01-15 10:35 ` Mehdi Djait
2025-01-15 10:55 ` Mehdi Djait
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=88f8feee-9cac-47d7-9a8d-3c118e26d124@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eagle.alexander923@gmail.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.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-rockchip@lists.infradead.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.fricke@collabora.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=val@packett.cool \
/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
all inboxes | Powered by JetHome®