[{"id":1771084,"web_url":"http://patchwork.ozlabs.org/comment/1771084/","msgid":"<20170919143248.c65slho3l5vnvzku@rob-hp-laptop>","list_archive_url":null,"date":"2017-09-19T14:32:48","subject":"Re: [PATCH v2 2/4] [media] dt-bindings: Document BCM283x CSI2/CCP2\n\treceiver","submitter":{"id":62529,"url":"http://patchwork.ozlabs.org/api/people/62529/","name":"Rob Herring (Arm)","email":"robh@kernel.org"},"content":"On Wed, Sep 13, 2017 at 04:07:47PM +0100, Dave Stevenson wrote:\n> Document the DT bindings for the CSI2/CCP2 receiver peripheral\n> (known as Unicam) on BCM283x SoCs.\n> \n> Signed-off-by: Dave Stevenson \n> ---\n> .../devicetree/bindings/media/bcm2835-unicam.txt | 107 +++++++++++++++++++++\n> 1 file changed, 107 insertions(+)\n> create mode 100644 Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n> \n> diff --git a/Documentation/devicetree/bindings/media/bcm2835-unicam.txt b/Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n> new file mode 100644\n> index 0000000..2ee5af7\n> --- /dev/null\n> +++ b/Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n> @@ -0,0 +1,107 @@\n> +Broadcom BCM283x Camera Interface (Unicam)\n> +------------------------------------------\n> +\n> +The Unicam block on BCM283x SoCs is the receiver for either\n> +CSI-2 or CCP2 data from image sensors or similar devices.\n> +\n> +There are two camera drivers in the kernel for BCM283x - this one\n> +and bcm2835-camera (currently in staging).\n\nLinux detail that is n/a for bindings.\n\n> +\n> +This driver is purely the kernel controlling the Unicam peripheral - there\n\nBindings describe h/w blocks, not drivers.\n\n> +is no involvement with the VideoCore firmware. Unicam receives CSI-2\n> +(or CCP2) data and writes it into SDRAM. There is no additional processing\n> +performed.\n> +It should be possible to connect it to any sensor with a\n> +suitable output interface and V4L2 subdevice driver.\n> +\n> +bcm2835-camera uses the VideoCore firmware to control the sensor,\n> +Unicam, ISP, and various tuner control loops. Fully processed frames are\n> +delivered to the driver by the firmware. It only has sensor drivers\n> +for Omnivision OV5647, and Sony IMX219 sensors, and is closed source.\n> +\n> +The two drivers are mutually exclusive for the same Unicam instance.\n> +The firmware checks the device tree configuration during boot. If\n> +it finds device tree nodes called csi0 or csi1 then it will block the\n> +firmware from accessing the peripheral, and bcm2835-camera will\n> +not be able to stream data.\n\nAll interesting, but irrelavent to the binding other than the part about \nnode name. Reword to just state the requirements to get the firmware to \nignore things.\n\n> +It should be possible to use bcm2835-camera on one camera interface\n> +and bcm2835-unicam on the other interface if there is a need to.\n\nFor upstream, I don't think we care to support that. We don't need 2 \nbindings.\n\n> +\n> +Required properties:\n> +===================\n> +- compatible\t: must be \"brcm,bcm2835-unicam\".\n> +- reg\t\t: physical base address and length of the register sets for the\n> +\t\t device.\n> +- interrupts\t: should contain the IRQ line for this Unicam instance.\n> +- clocks\t: list of clock specifiers, corresponding to entries in\n> +\t\t clock-names property.\n> +- clock-names\t: must contain an \"lp_clock\" entry, matching entries\n> +\t\t in the clocks property.\n\n_clock is redundant.\n\n> +\n> +Unicam supports a single port node. It should contain one 'port' child node\n> +with child 'endpoint' node. Please refer to the bindings defined in\n> +Documentation/devicetree/bindings/media/video-interfaces.txt.\n> +\n> +Within the endpoint node, the following properties are mandatory:\n> +- remote-endpoint\t: links to the source device endpoint.\n> +- data-lanes\t\t: An array denoting how many data lanes are physically\n> +\t\t\t present for this CSI-2 receiver instance. This can\n> +\t\t\t be limited by either the SoC itself, or by the\n> +\t\t\t breakout on the platform.\n> +\t\t\t Lane reordering is not supported, so lanes must be\n> +\t\t\t in order, starting at 1.\n\nJust refer to docs for standard properties. Just add any info on limits \nof values like number of cells.\n\n\n> +\n> +Lane reordering is not supported on the clock lane, so the optional property\n> +\"clock-lane\" will implicitly be <0>.\n> +Similarly lane inversion is not supported, therefore \"lane-polarities\" will\n> +implicitly be <0 0 0 0 0>.\n> +Neither of these values will be checked.\n> +\n> +Example:\n> +\tcsi1: csi@7e801000 {\n\nI thought the node had to be called csi0 or csi1. The label (csi1) will \nbe gone from the compiled dtb.\n\n> +\t\tcompatible = \"brcm,bcm2835-unicam\";\n> +\t\treg = <0x7e801000 0x800>,\n> +\t\t <0x7e802004 0x4>;\n> +\t\tinterrupts = <2 7>;\n> +\t\tclocks = <&clocks BCM2835_CLOCK_CAM1>;\n> +\t\tclock-names = \"lp_clock\";\n> +\n> +\t\tport {\n> +\t\t\t#address-cells = <1>;\n> +\t\t\t#size-cells = <0>;\n\nDon't need these with a single endpoint.\n\n> +\n> +\t\t\tcsi1_ep: endpoint {\n> +\t\t\t\tremote-endpoint = <&tc358743_0>;\n> +\t\t\t\tdata-lanes = <1 2>;\n> +\t\t\t};\n> +\t\t};\n> +\t};\n> +\n> +\ti2c0: i2c@7e205000 {\n> +\n> +\t\ttc358743: csi-hdmi-bridge@0f {\n> +\t\t\tcompatible = \"toshiba,tc358743\";\n> +\t\t\treg = <0x0f>;\n> +\t\t\tstatus = \"okay\";\n\nDon't show status in examples.\n\n> +\n> +\t\t\tclocks = <&tc358743_clk>;\n> +\t\t\tclock-names = \"refclk\";\n> +\n> +\t\t\ttc358743_clk: bridge-clk {\n> +\t\t\t\tcompatible = \"fixed-clock\";\n> +\t\t\t\t#clock-cells = <0>;\n> +\t\t\t\tclock-frequency = <27000000>;\n> +\t\t\t};\n> +\n> +\t\t\tport {\n> +\t\t\t\ttc358743_0: endpoint {\n> +\t\t\t\t\tremote-endpoint = <&csi1_ep>;\n> +\t\t\t\t\tclock-lanes = <0>;\n> +\t\t\t\t\tdata-lanes = <1 2>;\n> +\t\t\t\t\tclock-noncontinuous;\n> +\t\t\t\t\tlink-frequencies =\n> +\t\t\t\t\t\t/bits/ 64 <297000000>;\n> +\t\t\t\t};\n> +\t\t\t};\n> +\t\t};\n> +\t};\n> -- \n> 2.7.4\n> \n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xxQMW1QrNz9s7h\n\tfor ;\n\tWed, 20 Sep 2017 00:32:55 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1750948AbdISOcw (ORCPT\n\t);\n\tTue, 19 Sep 2017 10:32:52 -0400","from mail-io0-f194.google.com ([209.85.223.194]:38524 \"EHLO\n\tmail-io0-f194.google.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S1751165AbdISOcu (ORCPT\n\t); Tue, 19 Sep 2017 10:32:50 -0400","by mail-io0-f194.google.com with SMTP id e9so3308246iod.5;\n\tTue, 19 Sep 2017 07:32:49 -0700 (PDT)","from localhost (rrcs-67-78-118-34.sw.biz.rr.com. [67.78.118.34])\n\tby smtp.gmail.com with ESMTPSA id\n\t33sm326466otx.36.2017.09.19.07.32.48\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tTue, 19 Sep 2017 07:32:48 -0700 (PDT)"],"X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:in-reply-to:user-agent;\n\tbh=/vZ8l3DO5yhcSIyK3T4h9EmBb9CrFGaoo0gxJSOqeG0=;\n\tb=NPaSuEhKnbuIktFHUsY/l+OicT8f0MSX4k7cWLn8Y/FmWfNiNFgprIFttY/zkRVF65\n\tBd7dINtWl9KcvABsLHRtavv6TM3VVyLQYmCTRXQA4HMUZprn5nfyGzNzl4JSbC4DIIfF\n\tdQYlyzed+Wcg9B3hOArkVzWKP9Um/YWkAZF542BRKXYZNW/3y0AHtbgoOtee3OaBWt3n\n\tcRTFvfcGruun2/7dUNPkgTSImQCO25/bpP3Qk8w2XtyL0iT0NJq0d6N1aYs/taLI8mLU\n\t6t+hD/8bRXLGuvX6dT3G6CesIyHCdi20pDt51i+xGUPrE/Ph55JDKgMXkMlB2SUay0hg\n\tPLTA==","X-Gm-Message-State":"AHPjjUiNTLiGM/+KL/RjC4rBlmewWGjjmXf9qYMQDDRROy3wIRmMg1Wc\n\t7TBKJ2HiBUEI22CyPeSCGw==","X-Google-Smtp-Source":"AOwi7QCDU+14VlDGU3JyNXg3Pi4His+YrChiKxNslIkqzWyLvbefVdLgsS+Y4rqt0bkTivkfxCLl7w==","X-Received":"by 10.202.171.142 with SMTP id u136mr1689508oie.0.1505831569347; \n\tTue, 19 Sep 2017 07:32:49 -0700 (PDT)","Date":"Tue, 19 Sep 2017 09:32:48 -0500","From":"Rob Herring ","To":"Dave Stevenson ","Cc":"Mauro Carvalho Chehab ,\n\tHans Verkuil , Eric Anholt , \n\tStefan Wahren ,\n\tSakari Ailus , \n\tlinux-media@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,\n\tdevicetree@vger.kernel.org","Subject":"Re: [PATCH v2 2/4] [media] dt-bindings: Document BCM283x CSI2/CCP2\n\treceiver","Message-ID":"<20170919143248.c65slho3l5vnvzku@rob-hp-laptop>","References":"\n\t<9ad8b23d5c394b64ed02f9a5ebc49209696a5ace.1505314390.git.dave.stevenson@raspberrypi.org>","MIME-Version":"1.0","Content-Type":"text/plain; charset=us-ascii","Content-Disposition":"inline","In-Reply-To":"<9ad8b23d5c394b64ed02f9a5ebc49209696a5ace.1505314390.git.dave.stevenson@raspberrypi.org>","User-Agent":"NeoMutt/20170113 (1.7.2)","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}},{"id":1771140,"web_url":"http://patchwork.ozlabs.org/comment/1771140/","msgid":"","list_archive_url":null,"date":"2017-09-19T15:12:57","subject":"Re: [PATCH v2 2/4] [media] dt-bindings: Document BCM283x CSI2/CCP2\n\treceiver","submitter":{"id":72357,"url":"http://patchwork.ozlabs.org/api/people/72357/","name":"Dave Stevenson","email":"dave.stevenson@raspberrypi.org"},"content":"Hi Rob.\n\nThanks for the review.\n\nOn 19 September 2017 at 15:32, Rob Herring wrote:\n> On Wed, Sep 13, 2017 at 04:07:47PM +0100, Dave Stevenson wrote:\n>> Document the DT bindings for the CSI2/CCP2 receiver peripheral\n>> (known as Unicam) on BCM283x SoCs.\n>>\n>> Signed-off-by: Dave Stevenson \n>> ---\n>> .../devicetree/bindings/media/bcm2835-unicam.txt | 107 +++++++++++++++++++++\n>> 1 file changed, 107 insertions(+)\n>> create mode 100644 Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n>>\n>> diff --git a/Documentation/devicetree/bindings/media/bcm2835-unicam.txt b/Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n>> new file mode 100644\n>> index 0000000..2ee5af7\n>> --- /dev/null\n>> +++ b/Documentation/devicetree/bindings/media/bcm2835-unicam.txt\n>> @@ -0,0 +1,107 @@\n>> +Broadcom BCM283x Camera Interface (Unicam)\n>> +------------------------------------------\n>> +\n>> +The Unicam block on BCM283x SoCs is the receiver for either\n>> +CSI-2 or CCP2 data from image sensors or similar devices.\n>> +\n>> +There are two camera drivers in the kernel for BCM283x - this one\n>> +and bcm2835-camera (currently in staging).\n>\n> Linux detail that is n/a for bindings.\n>\n>> +\n>> +This driver is purely the kernel controlling the Unicam peripheral - there\n>\n> Bindings describe h/w blocks, not drivers.\n>\n>> +is no involvement with the VideoCore firmware. Unicam receives CSI-2\n>> +(or CCP2) data and writes it into SDRAM. There is no additional processing\n>> +performed.\n>> +It should be possible to connect it to any sensor with a\n>> +suitable output interface and V4L2 subdevice driver.\n>> +\n>> +bcm2835-camera uses the VideoCore firmware to control the sensor,\n>> +Unicam, ISP, and various tuner control loops. Fully processed frames are\n>> +delivered to the driver by the firmware. It only has sensor drivers\n>> +for Omnivision OV5647, and Sony IMX219 sensors, and is closed source.\n>> +\n>> +The two drivers are mutually exclusive for the same Unicam instance.\n>> +The firmware checks the device tree configuration during boot. If\n>> +it finds device tree nodes called csi0 or csi1 then it will block the\n>> +firmware from accessing the peripheral, and bcm2835-camera will\n>> +not be able to stream data.\n>\n> All interesting, but irrelavent to the binding other than the part about\n> node name. Reword to just state the requirements to get the firmware to\n> ignore things.\n\nHans had suggested it was potentially appropriate for DT bindings too\non last review [1] (which I apologise for missing off devicetree folk\nfrom), but I'll remove all mention of Linux/driver detail for v3.\nThat will leave only a reworded version of the bit about making the\nfirmware ignore the blocks.\n\n[1] http://www.spinics.net/lists/linux-media/msg117047.html\n\n>> +It should be possible to use bcm2835-camera on one camera interface\n>> +and bcm2835-unicam on the other interface if there is a need to.\n>\n> For upstream, I don't think we care to support that. We don't need 2\n> bindings.\n\nI'll remove as irrelevant, but in that case wouldn't you have 2\nbindings - one to bcm2835-camera which references the vchi node to the\nGPU, and one to bcm2835-unicam that gives the full block config as\nbeing discussed in this doc.\n(Currently bcm2835-camera is a platform device so has no binding doc).\nThis probably isn't the place for such a discussion.\n\n>> +\n>> +Required properties:\n>> +===================\n>> +- compatible : must be \"brcm,bcm2835-unicam\".\n>> +- reg : physical base address and length of the register sets for the\n>> + device.\n>> +- interrupts : should contain the IRQ line for this Unicam instance.\n>> +- clocks : list of clock specifiers, corresponding to entries in\n>> + clock-names property.\n>> +- clock-names : must contain an \"lp_clock\" entry, matching entries\n>> + in the clocks property.\n>\n> _clock is redundant.\n\nSo just \"lp\" as the clock name? Will assume so.\n\n>> +\n>> +Unicam supports a single port node. It should contain one 'port' child node\n>> +with child 'endpoint' node. Please refer to the bindings defined in\n>> +Documentation/devicetree/bindings/media/video-interfaces.txt.\n>> +\n>> +Within the endpoint node, the following properties are mandatory:\n>> +- remote-endpoint : links to the source device endpoint.\n>> +- data-lanes : An array denoting how many data lanes are physically\n>> + present for this CSI-2 receiver instance. This can\n>> + be limited by either the SoC itself, or by the\n>> + breakout on the platform.\n>> + Lane reordering is not supported, so lanes must be\n>> + in order, starting at 1.\n>\n> Just refer to docs for standard properties. Just add any info on limits\n> of values like number of cells.\n\nSo again from v1 Sakari had asked for a statement of mandatory\nproperties for the endpoint [1].\nWould you be happy with something like:\n\"Within the endpoint node the \"remote-endpoint\" and \"data-lanes\"\nproperties are mandatory. Lane reordering is not supported so the\nlanes must be in order, starting at 1. The number of data lanes should\nrepresent the number of lanes usable on the platform, which may be\nlimited by the SoC or the platform breakout.\"\n\n[1] http://www.spinics.net/lists/linux-media/msg117080.html\n\n>> +\n>> +Lane reordering is not supported on the clock lane, so the optional property\n>> +\"clock-lane\" will implicitly be <0>.\n>> +Similarly lane inversion is not supported, therefore \"lane-polarities\" will\n>> +implicitly be <0 0 0 0 0>.\n>> +Neither of these values will be checked.\n>> +\n>> +Example:\n>> + csi1: csi@7e801000 {\n>\n> I thought the node had to be called csi0 or csi1. The label (csi1) will\n> be gone from the compiled dtb.\n\nYes, typo :-(\n\n>> + compatible = \"brcm,bcm2835-unicam\";\n>> + reg = <0x7e801000 0x800>,\n>> + <0x7e802004 0x4>;\n>> + interrupts = <2 7>;\n>> + clocks = <&clocks BCM2835_CLOCK_CAM1>;\n>> + clock-names = \"lp_clock\";\n>> +\n>> + port {\n>> + #address-cells = <1>;\n>> + #size-cells = <0>;\n>\n> Don't need these with a single endpoint.\n\nOK.\n\n>> +\n>> + csi1_ep: endpoint {\n>> + remote-endpoint = <&tc358743_0>;\n>> + data-lanes = <1 2>;\n>> + };\n>> + };\n>> + };\n>> +\n>> + i2c0: i2c@7e205000 {\n>> +\n>> + tc358743: csi-hdmi-bridge@0f {\n>> + compatible = \"toshiba,tc358743\";\n>> + reg = <0x0f>;\n>> + status = \"okay\";\n>\n> Don't show status in examples.\n\nOK.\n\n>> +\n>> + clocks = <&tc358743_clk>;\n>> + clock-names = \"refclk\";\n>> +\n>> + tc358743_clk: bridge-clk {\n>> + compatible = \"fixed-clock\";\n>> + #clock-cells = <0>;\n>> + clock-frequency = <27000000>;\n>> + };\n>> +\n>> + port {\n>> + tc358743_0: endpoint {\n>> + remote-endpoint = <&csi1_ep>;\n>> + clock-lanes = <0>;\n>> + data-lanes = <1 2>;\n>> + clock-noncontinuous;\n>> + link-frequencies =\n>> + /bits/ 64 <297000000>;\n>> + };\n>> + };\n>> + };\n>> + };\n>> --\n>> 2.7.4\n>>\n\nThanks.\n Dave\n--\nTo unsubscribe from this list: send the line \"unsubscribe devicetree\" in\nthe body of a message to majordomo@vger.kernel.org\nMore majordomo info at http://vger.kernel.org/majordomo-info.html","headers":{"Return-Path":"","X-Original-To":"incoming-dt@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming-dt@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=devicetree-owner@vger.kernel.org; receiver=)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tsecure) header.d=raspberrypi.org header.i=@raspberrypi.org\n\theader.b=\"Q8EOLC3i\"; \n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tunprotected) header.d=raspberrypi-org.20150623.gappssmtp.com\n\theader.i=@raspberrypi-org.20150623.gappssmtp.com header.b=\"nNTTkwmN\"; \n\tdkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xxRFs2Jrmz9s7B\n\tfor ;\n\tWed, 20 Sep 2017 01:13:05 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751846AbdISPND (ORCPT\n\t);\n\tTue, 19 Sep 2017 11:13:03 -0400","from mx08-00252a01.pphosted.com ([91.207.212.211]:38154 \"EHLO\n\tmx08-00252a01.pphosted.com\" rhost-flags-OK-OK-OK-OK)\n\tby vger.kernel.org with ESMTP id S1751513AbdISPNC (ORCPT\n\t); Tue, 19 Sep 2017 11:13:02 -0400","from pps.filterd (m0102629.ppops.net [127.0.0.1])\n\tby mx08-00252a01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id\n\tv8JF954Z027532\n\tfor ; Tue, 19 Sep 2017 16:13:00 +0100","from mail-pg0-f69.google.com (mail-pg0-f69.google.com\n\t[74.125.83.69])\n\tby mx08-00252a01.pphosted.com with ESMTP id 2d0reg1mef-1\n\t(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128\n\tverify=OK)\n\tfor ; Tue, 19 Sep 2017 16:13:00 +0100","by mail-pg0-f69.google.com with SMTP id 188so6995053pgb.3\n\tfor ;\n\tTue, 19 Sep 2017 08:13:00 -0700 (PDT)","by 10.100.185.135 with HTTP; Tue, 19 Sep 2017 08:12:57 -0700 (PDT)"],"DKIM-Signature":["v=1; a=rsa-sha256; c=relaxed/relaxed; d=raspberrypi.org;\n\th=mime-version :\n\tin-reply-to : references : from : date : message-id : subject : to :\n\tcc :\n\tcontent-type; s=pp; bh=tRTvU2jQlJEa8Ny6UPA8ZfZellMH33dedxuXkJSh61Y=; \n\tb=Q8EOLC3ieZUCDT3huxGzeQpsFyLqjq6iLh4sDLPFmASsbN0vrBoNMVrAKk3zGxI6tH8H\n\tPKN2mBRSIAwLXHkVBtUWoNfsvp6g4QXYuP2Wxoo/PZx74/Snsyyd4V3IXgbX1GfSts+i\n\t2nQw1UuwZ+zbSeWoU+3hqWt4tVlENNGHLJ91r1ImByiBpATC+9wQpH6i82pi62j29+Lg\n\t8stUwrNJAXoJqiSLEWvhS4zwtaQng1flmQ7P/1GTVNv/tZVsbw5ZV5rN3UNKr3qMRzn0\n\tQMUck+kC/2fDpF8Jwp2VlodGHqOIwvZGWmVXpRFT1zwOeBliNmT91OcmCJo9CXtI+gTb\n\tMQ== ","v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=raspberrypi-org.20150623.gappssmtp.com; s=20150623;\n\th=mime-version:in-reply-to:references:from:date:message-id:subject:to\n\t:cc; bh=tRTvU2jQlJEa8Ny6UPA8ZfZellMH33dedxuXkJSh61Y=;\n\tb=nNTTkwmNnTVmDyU/EJJIbujZHAq7/3vnkhL/TT+CQWWN+BYjVVdYUwPkclXzs9QtHM\n\tY8PCQU3YHJlp7yxLEr0iAV6muHHwjG1qAWKqFityE6xmP1RRRJnHCyUFjs2zcgQC4fxf\n\tF6FwDqxTYdYE3l79IZ9XRF5Gh+z+E9XHA42nfytcwTaN4mJKFRBjID582Ek2pYbPIjR0\n\tj3Bj+AfF61PgX7V65urBvcHU65FK2nPxzMhM3owKw86mv1kusWlstztz9St9LYb9Vjjq\n\tieiP1kW6cg6t6/TXfuJMOevsKiU6iZR5D49bP9rjfWT4tOj04Gddo2odd13UtIc1IR6w\n\tTq3g=="],"X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:mime-version:in-reply-to:references:from:date\n\t:message-id:subject:to:cc;\n\tbh=tRTvU2jQlJEa8Ny6UPA8ZfZellMH33dedxuXkJSh61Y=;\n\tb=JWZzQ1NQ00vbvbHgu2+UHoT/ujGK0JHiYWP/sxBjLZYl4LzxeQp9/MCEHsS/tRryYN\n\tWvMRUSgSASKF3GJfbddTasXeG5L+t9wm0pk7r4173B9nSVdS6uenDYAK1rydPflzs+HL\n\tBrYdTEkN34w4amMW1MPOyPc5l329hj+Ol9bpp+iqSIQasGm1CDhWbnjcZhp5w9503A5T\n\tgLNY78Sfz9mGkj35EsGY+be6BuPWhGVeHGKUuG6AM0q4CW9yu853vXs5ZWawhbzUlVNN\n\thGYDQ5b7M3wp2tWKhKUaZ4udXk7A+5imcsKO1UU+sJ5ODbDxtc5tdN4nfbssGV9/zSy8\n\tAe4g==","X-Gm-Message-State":"AHPjjUg9iNtrjpwjzdqavL5z/zoh/a5kwLlXwlx3FPx7CXRMT/YCTx/s\n\taLyB3lvfLbt60JDw7Bg5JarIPj0DPU0vNrCMEvcjA8E0Pjb0il53h9dBh9T97YLiLpGqayf+ZqV\n\t75SEC5bqL4YWdm2GAN6hgRxZ83eN253I3RHdQ","X-Received":["by 10.99.105.196 with SMTP id e187mr1621481pgc.360.1505833978245;\n\tTue, 19 Sep 2017 08:12:58 -0700 (PDT)","by 10.99.105.196 with SMTP id e187mr1621456pgc.360.1505833977876;\n\tTue, 19 Sep 2017 08:12:57 -0700 (PDT)"],"X-Google-Smtp-Source":"AOwi7QAO7yJWnWUjTBeb+9UUEkrCeV9M/8vywYH3BmChN+iJrIwKIPoj3vrVgI+XJ1BcAhQ/ihKTZ9wPxzN4ZoTEmbU=","MIME-Version":"1.0","In-Reply-To":"<20170919143248.c65slho3l5vnvzku@rob-hp-laptop>","References":"\n\t<9ad8b23d5c394b64ed02f9a5ebc49209696a5ace.1505314390.git.dave.stevenson@raspberrypi.org>\n\t<20170919143248.c65slho3l5vnvzku@rob-hp-laptop>","From":"Dave Stevenson ","Date":"Tue, 19 Sep 2017 16:12:57 +0100","Message-ID":"","Subject":"Re: [PATCH v2 2/4] [media] dt-bindings: Document BCM283x CSI2/CCP2\n\treceiver","To":"Rob Herring ","Cc":"Mauro Carvalho Chehab ,\n\tHans Verkuil , Eric Anholt , \n\tStefan Wahren ,\n\tSakari Ailus , \n\tlinux-media@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,\n\tdevicetree@vger.kernel.org","Content-Type":"text/plain; charset=\"UTF-8\"","X-Proofpoint-Virus-Version":"vendor=fsecure engine=2.50.10432:, ,\n\tdefinitions=2017-09-19_06:, , signatures=0","X-Proofpoint-Spam-Details":"rule=outbound_spam_notspam policy=outbound_spam\n\tscore=0 priorityscore=1501\n\tmalwarescore=0 suspectscore=2 phishscore=0 bulkscore=0 spamscore=0\n\tclxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0\n\tclassifier=spam adjust=0 reason=mlx scancount=1\n\tengine=8.0.1-1707230000\n\tdefinitions=main-1709190215","Sender":"devicetree-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"devicetree@vger.kernel.org"}}]