Hi Jacopo,
On Thu, Dec 28, 2017 at 3:01 PM, Jacopo Mondi <jacopo+rene...@jmondi.org> wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
Thanks for your patch!
> Signed-off-by: Jacopo Mondi <jacopo+rene...@jmondi.org>
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt
> @@ -0,0 +1,85 @@
> +Renesas Capture Engine Unit (CEU)
> +----------------------------------------------
> +
> +The Capture Engine Unit is the image capture interface found on Renesas
> +RZ chip series and on SH Mobile ones.
> +
> +The interface supports a single parallel input with data bus width up to
> +8/16 bits.
> +
> +Required properties:
> +- compatible
> + Must be one of:
> + - "renesas,ceu"
Isn't "renesas,ceu" the generic fallback?
> + - "renesas,r7s72100-ceu"
> +- reg
> + Physical address base and size.
> +- interrupts
> + The interrupt specifier.
> +- pinctrl-names, pinctrl-0
> + phandle of pin controller sub-node configuring pins for CEU
> operations.
> +- remote-endpoint
> + phandle to an 'endpoint' subnode of a remote device node.
"remote-endpoint" is not a direct property, but must be part of nested "ports"
and "endpoint" subnodes, like in the example?
> +Example:
> +
> +The example describes the connection between the Capture Engine Unit and an
> +OV7670 image sensor sitting on bus i2c1.
> +
> +ceu: ceu@e8210000 {
> + reg = <0xe8210000 0x209c>;
> + compatible = "renesas,ceu";
> + interrupts = <GIC_SPI 332 IRQ_TYPE_LEVEL_HIGH>;
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&vio_pins>;
> +
> + status = "okay";
> +
> + port {
> + ceu_in: endpoint {
> + remote-endpoint = <&ov7670_out>;
> +
> + hsync-active = <1>;
> + vsync-active = <0>;
> + };
> + };
> +};
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
