From: Sakari Ailus <sakari.ailus@iki.fi>
To: Mickael Guene <mickael.guene@st.com>
Cc: linux-media@vger.kernel.org, hugues.fruchet@st.com,
Mauro Carvalho Chehab <mchehab@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: Document MIPID02 bindings
Date: Sat, 6 Apr 2019 13:35:25 +0300 [thread overview]
Message-ID: <20190406103525.amfsljsz4twi3xq2@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <1553680545-73278-2-git-send-email-mickael.guene@st.com>
Hi Mickael,
On Wed, Mar 27, 2019 at 10:55:43AM +0100, Mickael Guene wrote:
> This adds documentation of device tree for MIPID02 CSI-2 to PARALLEL
> bridge.
>
> Signed-off-by: Mickael Guene <mickael.guene@st.com>
> ---
>
> Changes in v4:
> - Fix and clarify endpoints properties documentation
>
> Changes in v3: None
> Changes in v2:
> - Add precision about first CSI-2 port data rate
> - Document endpoints supported properties
> - Rename 'mipid02@14' into generic 'csi2rx@14' in example
>
> .../bindings/media/i2c/st,st-mipid02.txt | 82 ++++++++++++++++++++++
> MAINTAINERS | 7 ++
> 2 files changed, 89 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/st,st-mipid02.txt
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/st,st-mipid02.txt b/Documentation/devicetree/bindings/media/i2c/st,st-mipid02.txt
> new file mode 100644
> index 0000000..754a175
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/st,st-mipid02.txt
> @@ -0,0 +1,82 @@
> +STMicroelectronics MIPID02 CSI-2 to PARALLEL bridge
> +
> +MIPID02 has two CSI-2 input ports, only one of those ports can be active at a
> +time. Active port input stream will be de-serialized and its content outputted
> +through PARALLEL output port.
> +CSI-2 first input port is a dual lane 800Mbps per lane whereas CSI-2 second
> +input port is a single lane 800Mbps. Both ports support clock and data lane
> +polarity swap. First port also supports data lane swap.
> +PARALLEL output port has a maximum width of 12 bits.
> +Supported formats are RAW6, RAW7, RAW8, RAW10, RAW12, RGB565, RGB888, RGB444,
> +YUV420 8-bit, YUV422 8-bit and YUV420 10-bit.
> +
> +Required Properties:
> +- compatible: should be "st,st-mipid02"
s/should/shall/ overall; other values aren't really valid in any of the
cases.
--
Sakari Ailus
next prev parent reply other threads:[~2019-04-06 10:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 6:44 [PATCH v1 0/3] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-12 6:44 ` [PATCH v1 1/3] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-16 21:46 ` Sakari Ailus
2019-03-18 8:28 ` Mickael GUENE
2019-03-18 8:48 ` Sakari Ailus
2019-03-18 9:08 ` Mickael GUENE
2019-03-12 6:44 ` [PATCH v1 2/3] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-16 22:14 ` Sakari Ailus
2019-03-18 9:57 ` Mickael GUENE
2019-03-25 11:17 ` Sakari Ailus
2019-03-25 12:14 ` Mickael GUENE
2019-03-26 11:37 ` Sakari Ailus
2019-03-26 12:07 ` Mickael GUENE
2019-03-12 6:44 ` [PATCH v1 3/3] media: MAINTAINERS: add entry for STMicroelectronics MIPID02 media driver Mickael Guene
2019-03-16 21:47 ` Sakari Ailus
2019-03-18 10:01 ` Mickael GUENE
2019-03-25 7:55 ` [PATCH v2 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-25 7:55 ` [PATCH v2 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-25 7:55 ` [PATCH v2 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-25 11:44 ` Sakari Ailus
2019-03-25 12:22 ` Mickael GUENE
2019-03-26 11:34 ` Sakari Ailus
2019-03-26 12:32 ` Mickael GUENE
2019-03-26 10:03 ` [PATCH v3 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-26 10:03 ` [PATCH v3 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-26 12:17 ` Sakari Ailus
2019-03-26 13:40 ` Mickael GUENE
2019-03-26 13:44 ` Sakari Ailus
2019-03-26 10:03 ` [PATCH v3 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
2019-03-26 11:33 ` Sakari Ailus
2019-03-26 12:57 ` Mickael GUENE
2019-03-26 13:54 ` Sakari Ailus
2019-03-26 14:12 ` Mickael GUENE
2019-03-26 14:14 ` Sakari Ailus
2019-03-26 14:36 ` Mickael GUENE
2019-04-06 11:01 ` Sakari Ailus
2019-04-08 6:17 ` Mickael GUENE
2019-04-08 9:21 ` Sakari Ailus
2019-03-27 9:55 ` [PATCH v4 0/2] Add support for MIPID02 CSI-2 to PARALLEL bridge I2C device Mickael Guene
2019-03-27 9:55 ` [PATCH v4 1/2] dt-bindings: Document MIPID02 bindings Mickael Guene
2019-03-28 17:43 ` Rob Herring
2019-04-06 10:35 ` Sakari Ailus [this message]
2019-04-06 10:38 ` Sakari Ailus
2019-04-08 6:20 ` Mickael GUENE
2019-03-27 9:55 ` [PATCH v4 2/2] media:st-mipid02: MIPID02 CSI-2 to PARALLEL bridge driver Mickael Guene
[not found] ` <20190406105606.rciacao5d4hljbbu@kekkonen.localdomain>
2019-04-08 8:20 ` Mickael GUENE
2019-04-08 9:17 ` Sakari Ailus
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=20190406103525.amfsljsz4twi3xq2@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hugues.fruchet@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mickael.guene@st.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).