From patchwork Thu Feb 16 02:19:03 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Steve Longerbeam X-Patchwork-Id: 728471 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3vP0Wb5ncxz9rxw for ; Thu, 16 Feb 2017 13:30:51 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="hVc/en9f"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753019AbdBPCUE (ORCPT ); Wed, 15 Feb 2017 21:20:04 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:36407 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752865AbdBPCT6 (ORCPT ); Wed, 15 Feb 2017 21:19:58 -0500 Received: by mail-pg0-f68.google.com with SMTP id 75so474814pgf.3; Wed, 15 Feb 2017 18:19:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=cZlTi2ehkfCej9qYJnIQFjON8I2rHRMWIB26/PfCsog=; b=hVc/en9f3aHjZ0bEOfboavrZCBfmf8FNtUw1OSR+K627fn5G9xIL4gaYuzWNov97ET /9vGEUlp2Z8uDh+/Z/LLNsmLEf/ArcvCx8pi3s5z4iQgBdtmi/TiCYoe6l9un635u7Nu yWPDIYmdAA3pG+iQNFC//uc1Q3ntXJiclYkjO7R2dZ66EGC+0oGS6zBMJAFMo6SL5Ua+ 9+11a1YCfkSd25UeUawsYLxwqC8xmc/oqSdldZjS8iNIr6qtAS0FWslDUwwUuDq5DVcP oXuj1tZnVJqkvhUvdv4tMZQpE72flemMvh5FIp4oldnfyKx+dEkGOGS/+wcpERIVLb2b qV7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=cZlTi2ehkfCej9qYJnIQFjON8I2rHRMWIB26/PfCsog=; b=cuHdVxK1kzxnivLStKbCb3SCyfsCDdhv0lUUpInGo0hFLq7n5YK1RRExu4ake5nR9s MoxWaFPQOyrKDw+sQqypCuIW4kBeB0DIhhRZCtqsOxdmxvP5sRhQn2hlCeIr9vU3Gqbj gsIjRNlQTePtVHzPtC4PY1er9zcipjkPDB0K47sytFGwvpsQvVh4qki2LZy+fxNYNFWF wcOXfB8cZlBWPZTJug+0qsHFUPdYHQvvz3hmAfw2XzUcYyjUIKryv6Q/2v+D9Ym5S7Jg Awv2ewoho7OpfAhJAEw5VK5YuvEC/bdkjHrTdBZajRJCN8Y8zoqapBIzXAvpQiXYo1Rk PWIQ== X-Gm-Message-State: AMke39nmqOJT7x3W3+EcFUkhHvKUMm4DoMheedFntndiSzjaZvt8uWepYpv5cZ6GDImQXw== X-Received: by 10.99.102.134 with SMTP id a128mr42127306pgc.215.1487211597483; Wed, 15 Feb 2017 18:19:57 -0800 (PST) Received: from majic.sklembedded.com (c-98-210-181-167.hsd1.ca.comcast.net. [98.210.181.167]) by smtp.googlemail.com with ESMTPSA id t6sm9869352pgt.8.2017.02.15.18.19.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 15 Feb 2017 18:19:56 -0800 (PST) From: Steve Longerbeam X-Google-Original-From: Steve Longerbeam To: robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org, kernel@pengutronix.de, fabio.estevam@nxp.com, linux@armlinux.org.uk, mchehab@kernel.org, hverkuil@xs4all.nl, nick@shmanahar.org, markus.heiser@darmarIT.de, p.zabel@pengutronix.de, laurent.pinchart+renesas@ideasonboard.com, bparrot@ti.com, geert@linux-m68k.org, arnd@arndb.de, sudipm.mukherjee@gmail.com, minghsiu.tsai@mediatek.com, tiffany.lin@mediatek.com, jean-christophe.trotin@st.com, horms+renesas@verge.net.au, niklas.soderlund+renesas@ragnatech.se, robert.jarzmik@free.fr, songjun.wu@microchip.com, andrew-ct.chen@mediatek.com, gregkh@linuxfoundation.org, shuah@kernel.org, sakari.ailus@linux.intel.com, pavel@ucw.cz Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org, devel@driverdev.osuosl.org, Steve Longerbeam Subject: [PATCH v4 01/36] [media] dt-bindings: Add bindings for i.MX media driver Date: Wed, 15 Feb 2017 18:19:03 -0800 Message-Id: <1487211578-11360-2-git-send-email-steve_longerbeam@mentor.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1487211578-11360-1-git-send-email-steve_longerbeam@mentor.com> References: <1487211578-11360-1-git-send-email-steve_longerbeam@mentor.com> Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Add bindings documentation for the i.MX media driver. Signed-off-by: Steve Longerbeam --- Documentation/devicetree/bindings/media/imx.txt | 66 +++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/imx.txt diff --git a/Documentation/devicetree/bindings/media/imx.txt b/Documentation/devicetree/bindings/media/imx.txt new file mode 100644 index 0000000..fd5af50 --- /dev/null +++ b/Documentation/devicetree/bindings/media/imx.txt @@ -0,0 +1,66 @@ +Freescale i.MX Media Video Device +================================= + +Video Media Controller node +--------------------------- + +This is the media controller node for video capture support. It is a +virtual device that lists the camera serial interface nodes that the +media device will control. + +Required properties: +- compatible : "fsl,imx-capture-subsystem"; +- ports : Should contain a list of phandles pointing to camera + sensor interface ports of IPU devices + +example: + +capture-subsystem { + compatible = "fsl,capture-subsystem"; + ports = <&ipu1_csi0>, <&ipu1_csi1>; +}; + +fim child node +-------------- + +This is an optional child node of the ipu_csi port nodes. If present and +available, it enables the Frame Interval Monitor. Its properties can be +used to modify the method in which the FIM measures frame intervals. +Refer to Documentation/media/v4l-drivers/imx.rst for more info on the +Frame Interval Monitor. + +Optional properties: +- fsl,input-capture-channel: an input capture channel and channel flags, + specified as . The channel number + must be 0 or 1. The flags can be + IRQ_TYPE_EDGE_RISING, IRQ_TYPE_EDGE_FALLING, or + IRQ_TYPE_EDGE_BOTH, and specify which input + capture signal edge will trigger the input + capture event. If an input capture channel is + specified, the FIM will use this method to + measure frame intervals instead of via the EOF + interrupt. The input capture method is much + preferred over EOF as it is not subject to + interrupt latency errors. However it requires + routing the VSYNC or FIELD output signals of + the camera sensor to one of the i.MX input + capture pads (SD1_DAT0, SD1_DAT1), which also + gives up support for SD1. + + +mipi_csi2 node +-------------- + +This is the device node for the MIPI CSI-2 Receiver, required for MIPI +CSI-2 sensors. + +Required properties: +- compatible : "fsl,imx6-mipi-csi2", "snps,dw-mipi-csi2"; +- reg : physical base address and length of the register set; +- clocks : the MIPI CSI-2 receiver requires three clocks: hsi_tx + (the DPHY clock), video_27m, and eim_podf; +- clock-names : must contain "dphy", "cfg", "pix"; + +Optional properties: +- interrupts : must contain two level-triggered interrupts, + in order: 100 and 101;