All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	tomoharu.fukawa.eb@renesas.com,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v9 01/28] rcar-vin: add Gen3 devicetree bindings documentation
Date: Fri, 8 Dec 2017 13:55:32 +0100	[thread overview]
Message-ID: <20171208125532.GL31989@bigcity.dyn.berto.se> (raw)
In-Reply-To: <1516159.4MxLsDy55H@avalon>

Hi Laurent,

Thanks for your comments!

On 2017-12-08 09:46:24 +0200, Laurent Pinchart wrote:
> Hi Niklas,
> 
> Thank you for the patch.
> 
> On Friday, 8 December 2017 03:08:15 EET Niklas Söderlund wrote:
> > Document the devicetree bindings for the CSI-2 inputs available on Gen3.
> > 
> > There is a need to add a custom property 'renesas,id' and to define
> > which CSI-2 input is described in which endpoint under the port@1 node.
> > This information is needed since there are a set of predefined routes
> > between each VIN and CSI-2 block. This routing table will be kept
> > inside the driver but in order for it to act on it it must know which
> > VIN and CSI-2 is which.
> > 
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> >  .../devicetree/bindings/media/rcar_vin.txt         | 116 +++++++++++++++---
> >  1 file changed, 104 insertions(+), 12 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > b/Documentation/devicetree/bindings/media/rcar_vin.txt index
> > ff9697ed81396e64..5a95d9668d2c7dfd 100644
> > --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> > @@ -2,8 +2,12 @@ Renesas R-Car Video Input driver (rcar_vin)
> >  -------------------------------------------
> > 
> >  The rcar_vin device provides video input capabilities for the Renesas R-Car
> > -family of devices. The current blocks are always slaves and suppot one
> > input
> > -channel which can be either RGB, YUYV or BT656.
> > +family of devices.
> > +
> > +Each VIN instance has a single parallel input that supports RGB and YUV
> > video,
> > +with both external synchronization and BT.656 synchronization for the
> > latter.
> > +Depending on the instance the VIN input is connected to external SoC pins,
> > or
> > +on Gen3 to a CSI-2 receiver.
> > 
> >   - compatible: Must be one or more of the following
> >     - "renesas,vin-r8a7743" for the R8A7743 device
> > @@ -31,21 +35,38 @@ channel which can be either RGB, YUYV or BT656.
> >  Additionally, an alias named vinX will need to be created to specify
> >  which video input device this is.
> > 
> > -The per-board settings:
> > +The per-board settings Gen2:
> 
> Nitpicking, s/Gen2/for Gen2 platforms/
> 
> (or Gen2 hardware, or Gen2 systems, pick the one you like best)

Good catch, I guess I'm to caught up in it all and it's obvious for me 
what Gen2 is :-) I will update and use "Gen2 platform" throughout this 
document.

> 
> >   - port sub-node describing a single endpoint connected to the vin
> >     as described in video-interfaces.txt[1]. Only the first one will
> >     be considered as each vin interface has one input port.
> > 
> > -   These settings are used to work out video input format and widths
> > -   into the system.
> > +The per-board settings Gen3:
> 
> Ditto.
> 
> > +
> > +Gen3 can support both a single connected parallel input source from
> > +external SoC pins (port0) and/or multiple parallel input sources from
> > +local SoC CSI-2 receivers (port1) depending on SoC.
> > 
> > +- renesas,id - ID number of the VIN, VINx in the documentation.
> > +- ports
> > +    - port0 - sub-node describing a single endpoint connected to the VIN
> > +      from external SoC pins described in video-interfaces.txt[1]. Only
> > +      the first one will be considered as each VIN interface has at most
> > +      one set of SoC external input pins.
> 
> s/port0/port 0/ or s/port0/port@0/

I will use 'port 0' as I think it makes more sens when reading.

> 
> I'd go further than that and make it invalid to have multiple endpoints 
> instead of ignoring all but the first one.

Good catch, I'm describing what the current rcar-vin driver dose and not 
the generic case where in fact only one endpoint in port 0 is valid.  
Will update.

> 
> I would also explicitly state that VIN instances not connected to external 
> pins shall have no port 0.

It's good to be explicit, will add this.

> 
> > +    - port1 - sub-nodes describing one or more endpoints connected to
> > +      the VIN from local SoC CSI-2 receivers. The endpoint numbers must
> > +      use the following schema.
> 
> Nitpicking again, the Gen2-specific properties are indented above while the 
> Gen3 properties are not indented here. Pick the one you prefer :-)

I like it they way it is :-)

The Gen2-specific properties are all on the same level in the dt 
description. While some Gen3-specific properties (port 0 and port 1) are 
indented one level in the dt description and this is why I indented them 
one level in the documentation. To make it clear that they should be 
children of the ports node.

I don't feel strongly about this but I feel it adds to the readability.  
If you don't agree I'm happy to remove the indentation for these two 
properties.

> 
> > -Device node example
> > --------------------
> > +        - Endpoint 0 - sub-node describing the endpoint which is CSI20
> > +        - Endpoint 1 - sub-node describing the endpoint which is CSI21
> > +        - Endpoint 2 - sub-node describing the endpoint which is CSI40
> > +        - Endpoint 3 - sub-node describing the endpoint which is CSI41
> 
> How about s/which is/connected to/ ?

Sounds better, will update.


> 
> > -	aliases {
> > -	       vin0 = &vin0;
> > -	};
> > +Device node example Gen2
> 
> s/Gen2/for Gen2 platforms/
> 
> and same in a few places below.

Will fix.

> 
> > +------------------------
> > +
> > +        aliases {
> > +                vin0 = &vin0;
> > +        };
> 
> This is unrelated, but do we need aliases ?

We don't have aliases for Gen3 but they exists in DTS for Gen2. My 
feeling is that we don't need them. My plan is to once Gen3 support is 
done try to sort this out, both in the documentation and in the dts 
files for Gen2.

> 
> >          vin0: vin@0xe6ef0000 {
> >                  compatible = "renesas,vin-r8a7790",
> > "renesas,rcar-gen2-vin"; @@ -55,8 +76,8 @@ Device node example
> >                  status = "disabled";
> >          };
> > 
> > -Board setup example (vin1 composite video input)
> > -------------------------------------------------
> > +Board setup example Gen2 (vin1 composite video input)
> > +-----------------------------------------------------
> > 
> >  &i2c2   {
> >          status = "ok";
> > @@ -95,6 +116,77 @@ Board setup example (vin1 composite video input)
> >          };
> >  };
> > 
> > +Device node example Gen3
> > +------------------------
> > +
> > +        vin0: video@e6ef0000 {
> > +                compatible = "renesas,vin-r8a7795";
> > +                reg = <0 0xe6ef0000 0 0x1000>;
> > +                interrupts = <GIC_SPI 188 IRQ_TYPE_LEVEL_HIGH>;
> > +                clocks = <&cpg CPG_MOD 811>;
> > +                power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
> > +                resets = <&cpg 811>;
> > +                renesas,id = <0>;
> > +
> > +                ports {
> > +                        #address-cells = <1>;
> > +                        #size-cells = <0>;
> > +
> > +                        port@1 {
> > +                                #address-cells = <1>;
> > +                                #size-cells = <0>;
> > +
> > +                                reg = <1>;
> > +
> > +                                vin0csi20: endpoint@0 {
> > +                                        reg = <0>;
> > +                                        remote-endpoint= <&csi20vin0>;
> > +                                };
> > +                                vin0csi21: endpoint@1 {
> > +                                        reg = <1>;
> > +                                        remote-endpoint= <&csi21vin0>;
> > +                                };
> > +                                vin0csi40: endpoint@2 {
> > +                                        reg = <2>;
> > +                                        remote-endpoint= <&csi40vin0>;
> > +                                };
> > +                        };
> > +                };
> > +        };
> > +
> > +        csi20: csi2@fea80000 {
> > +                compatible = "renesas,r8a7795-csi2";
> > +                reg = <0 0xfea80000 0 0x10000>;
> > +                interrupts = <GIC_SPI 184 IRQ_TYPE_LEVEL_HIGH>;
> > +                clocks = <&cpg CPG_MOD 714>;
> > +                power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
> > +                resets = <&cpg 714>;
> > +
> > +                ports {
> > +                        #address-cells = <1>;
> > +                        #size-cells = <0>;
> > +
> > +                        port@0 {
> > +                                reg = <0>;
> > +                                csi20_in: endpoint {
> > +                                        clock-lanes = <0>;
> > +                                        data-lanes = <1>;
> > +                                        remote-endpoint = <&adv7482_txb>;
> > +                                };
> > +                        };
> > +
> > +                        port@1 {
> > +                                #address-cells = <1>;
> > +                                #size-cells = <0>;
> > 
> > +                                reg = <1>;
> > +
> > +                                csi20vin0: endpoint@0 {
> > +                                        reg = <0>;
> > +                                        remote-endpoint = <&vin0csi20>;
> > +                                };
> > +                        };
> > +                };
> > +        };
> > 
> >  [1] video-interfaces.txt common video media interface
> 
> -- 
> Regards,
> 
> Laurent Pinchart
> 

-- 
Regards,
Niklas Söderlund

WARNING: multiple messages have this Message-ID (diff)
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	tomoharu.fukawa.eb@renesas.com,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v9 01/28] rcar-vin: add Gen3 devicetree bindings documentation
Date: Fri, 8 Dec 2017 13:55:32 +0100	[thread overview]
Message-ID: <20171208125532.GL31989@bigcity.dyn.berto.se> (raw)
In-Reply-To: <1516159.4MxLsDy55H@avalon>

Hi Laurent,

Thanks for your comments!

On 2017-12-08 09:46:24 +0200, Laurent Pinchart wrote:
> Hi Niklas,
> 
> Thank you for the patch.
> 
> On Friday, 8 December 2017 03:08:15 EET Niklas S�derlund wrote:
> > Document the devicetree bindings for the CSI-2 inputs available on Gen3.
> > 
> > There is a need to add a custom property 'renesas,id' and to define
> > which CSI-2 input is described in which endpoint under the port@1 node.
> > This information is needed since there are a set of predefined routes
> > between each VIN and CSI-2 block. This routing table will be kept
> > inside the driver but in order for it to act on it it must know which
> > VIN and CSI-2 is which.
> > 
> > Signed-off-by: Niklas S�derlund <niklas.soderlund+renesas@ragnatech.se>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> >  .../devicetree/bindings/media/rcar_vin.txt         | 116 +++++++++++++++---
> >  1 file changed, 104 insertions(+), 12 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > b/Documentation/devicetree/bindings/media/rcar_vin.txt index
> > ff9697ed81396e64..5a95d9668d2c7dfd 100644
> > --- a/Documentation/devicetree/bindings/media/rcar_vin.txt
> > +++ b/Documentation/devicetree/bindings/media/rcar_vin.txt
> > @@ -2,8 +2,12 @@ Renesas R-Car Video Input driver (rcar_vin)
> >  -------------------------------------------
> > 
> >  The rcar_vin device provides video input capabilities for the Renesas R-Car
> > -family of devices. The current blocks are always slaves and suppot one
> > input
> > -channel which can be either RGB, YUYV or BT656.
> > +family of devices.
> > +
> > +Each VIN instance has a single parallel input that supports RGB and YUV
> > video,
> > +with both external synchronization and BT.656 synchronization for the
> > latter.
> > +Depending on the instance the VIN input is connected to external SoC pins,
> > or
> > +on Gen3 to a CSI-2 receiver.
> > 
> >   - compatible: Must be one or more of the following
> >     - "renesas,vin-r8a7743" for the R8A7743 device
> > @@ -31,21 +35,38 @@ channel which can be either RGB, YUYV or BT656.
> >  Additionally, an alias named vinX will need to be created to specify
> >  which video input device this is.
> > 
> > -The per-board settings:
> > +The per-board settings Gen2:
> 
> Nitpicking, s/Gen2/for Gen2 platforms/
> 
> (or Gen2 hardware, or Gen2 systems, pick the one you like best)

Good catch, I guess I'm to caught up in it all and it's obvious for me 
what Gen2 is :-) I will update and use "Gen2 platform" throughout this 
document.

> 
> >   - port sub-node describing a single endpoint connected to the vin
> >     as described in video-interfaces.txt[1]. Only the first one will
> >     be considered as each vin interface has one input port.
> > 
> > -   These settings are used to work out video input format and widths
> > -   into the system.
> > +The per-board settings Gen3:
> 
> Ditto.
> 
> > +
> > +Gen3 can support both a single connected parallel input source from
> > +external SoC pins (port0) and/or multiple parallel input sources from
> > +local SoC CSI-2 receivers (port1) depending on SoC.
> > 
> > +- renesas,id - ID number of the VIN, VINx in the documentation.
> > +- ports
> > +    - port0 - sub-node describing a single endpoint connected to the VIN
> > +      from external SoC pins described in video-interfaces.txt[1]. Only
> > +      the first one will be considered as each VIN interface has at most
> > +      one set of SoC external input pins.
> 
> s/port0/port 0/ or s/port0/port@0/

I will use 'port 0' as I think it makes more sens when reading.

> 
> I'd go further than that and make it invalid to have multiple endpoints 
> instead of ignoring all but the first one.

Good catch, I'm describing what the current rcar-vin driver dose and not 
the generic case where in fact only one endpoint in port 0 is valid.  
Will update.

> 
> I would also explicitly state that VIN instances not connected to external 
> pins shall have no port 0.

It's good to be explicit, will add this.

> 
> > +    - port1 - sub-nodes describing one or more endpoints connected to
> > +      the VIN from local SoC CSI-2 receivers. The endpoint numbers must
> > +      use the following schema.
> 
> Nitpicking again, the Gen2-specific properties are indented above while the 
> Gen3 properties are not indented here. Pick the one you prefer :-)

I like it they way it is :-)

The Gen2-specific properties are all on the same level in the dt 
description. While some Gen3-specific properties (port 0 and port 1) are 
indented one level in the dt description and this is why I indented them 
one level in the documentation. To make it clear that they should be 
children of the ports node.

I don't feel strongly about this but I feel it adds to the readability.  
If you don't agree I'm happy to remove the indentation for these two 
properties.

> 
> > -Device node example
> > --------------------
> > +        - Endpoint 0 - sub-node describing the endpoint which is CSI20
> > +        - Endpoint 1 - sub-node describing the endpoint which is CSI21
> > +        - Endpoint 2 - sub-node describing the endpoint which is CSI40
> > +        - Endpoint 3 - sub-node describing the endpoint which is CSI41
> 
> How about s/which is/connected to/ ?

Sounds better, will update.


> 
> > -	aliases {
> > -	       vin0 = &vin0;
> > -	};
> > +Device node example Gen2
> 
> s/Gen2/for Gen2 platforms/
> 
> and same in a few places below.

Will fix.

> 
> > +------------------------
> > +
> > +        aliases {
> > +                vin0 = &vin0;
> > +        };
> 
> This is unrelated, but do we need aliases ?

We don't have aliases for Gen3 but they exists in DTS for Gen2. My 
feeling is that we don't need them. My plan is to once Gen3 support is 
done try to sort this out, both in the documentation and in the dts 
files for Gen2.

> 
> >          vin0: vin@0xe6ef0000 {
> >                  compatible = "renesas,vin-r8a7790",
> > "renesas,rcar-gen2-vin"; @@ -55,8 +76,8 @@ Device node example
> >                  status = "disabled";
> >          };
> > 
> > -Board setup example (vin1 composite video input)
> > -------------------------------------------------
> > +Board setup example Gen2 (vin1 composite video input)
> > +-----------------------------------------------------
> > 
> >  &i2c2   {
> >          status = "ok";
> > @@ -95,6 +116,77 @@ Board setup example (vin1 composite video input)
> >          };
> >  };
> > 
> > +Device node example Gen3
> > +------------------------
> > +
> > +        vin0: video@e6ef0000 {
> > +                compatible = "renesas,vin-r8a7795";
> > +                reg = <0 0xe6ef0000 0 0x1000>;
> > +                interrupts = <GIC_SPI 188 IRQ_TYPE_LEVEL_HIGH>;
> > +                clocks = <&cpg CPG_MOD 811>;
> > +                power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
> > +                resets = <&cpg 811>;
> > +                renesas,id = <0>;
> > +
> > +                ports {
> > +                        #address-cells = <1>;
> > +                        #size-cells = <0>;
> > +
> > +                        port@1 {
> > +                                #address-cells = <1>;
> > +                                #size-cells = <0>;
> > +
> > +                                reg = <1>;
> > +
> > +                                vin0csi20: endpoint@0 {
> > +                                        reg = <0>;
> > +                                        remote-endpoint= <&csi20vin0>;
> > +                                };
> > +                                vin0csi21: endpoint@1 {
> > +                                        reg = <1>;
> > +                                        remote-endpoint= <&csi21vin0>;
> > +                                };
> > +                                vin0csi40: endpoint@2 {
> > +                                        reg = <2>;
> > +                                        remote-endpoint= <&csi40vin0>;
> > +                                };
> > +                        };
> > +                };
> > +        };
> > +
> > +        csi20: csi2@fea80000 {
> > +                compatible = "renesas,r8a7795-csi2";
> > +                reg = <0 0xfea80000 0 0x10000>;
> > +                interrupts = <GIC_SPI 184 IRQ_TYPE_LEVEL_HIGH>;
> > +                clocks = <&cpg CPG_MOD 714>;
> > +                power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
> > +                resets = <&cpg 714>;
> > +
> > +                ports {
> > +                        #address-cells = <1>;
> > +                        #size-cells = <0>;
> > +
> > +                        port@0 {
> > +                                reg = <0>;
> > +                                csi20_in: endpoint {
> > +                                        clock-lanes = <0>;
> > +                                        data-lanes = <1>;
> > +                                        remote-endpoint = <&adv7482_txb>;
> > +                                };
> > +                        };
> > +
> > +                        port@1 {
> > +                                #address-cells = <1>;
> > +                                #size-cells = <0>;
> > 
> > +                                reg = <1>;
> > +
> > +                                csi20vin0: endpoint@0 {
> > +                                        reg = <0>;
> > +                                        remote-endpoint = <&vin0csi20>;
> > +                                };
> > +                        };
> > +                };
> > +        };
> > 
> >  [1] video-interfaces.txt common video media interface
> 
> -- 
> Regards,
> 
> Laurent Pinchart
> 

-- 
Regards,
Niklas S�derlund

  reply	other threads:[~2017-12-08 12:55 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  1:08 [PATCH v9 00/28] rcar-vin: Add Gen3 with media controller Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 01/28] rcar-vin: add Gen3 devicetree bindings documentation Niklas Söderlund
2017-12-08  7:46   ` Laurent Pinchart
2017-12-08 12:55     ` Niklas Söderlund [this message]
2017-12-08 12:55       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 02/28] rcar-vin: rename poorly named initialize and cleanup functions Niklas Söderlund
2017-12-08  7:49   ` Laurent Pinchart
2017-12-08 12:58     ` Niklas Söderlund
2017-12-08 12:58       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 03/28] rcar-vin: unregister video device on driver removal Niklas Söderlund
2017-12-08  7:54   ` Laurent Pinchart
2017-12-08  8:46     ` Hans Verkuil
2017-12-08  8:49       ` Laurent Pinchart
2017-12-08 13:09     ` Niklas Söderlund
2017-12-08 13:09       ` Niklas Söderlund
2017-12-08 19:07       ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 04/28] rcar-vin: move subdevice handling to async callbacks Niklas Söderlund
2017-12-08  8:03   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 05/28] rcar-vin: move chip information to own struct Niklas Söderlund
2017-12-08  8:08   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 06/28] rcar-vin: move max width and height information to chip information Niklas Söderlund
2017-12-08  8:10   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 07/28] rcar-vin: change name of video device Niklas Söderlund
2017-12-08  8:17   ` Laurent Pinchart
2017-12-14 14:25     ` Sakari Ailus
2017-12-14 14:25       ` Sakari Ailus
2017-12-14 15:50       ` Laurent Pinchart
2017-12-20 15:20         ` Niklas Söderlund
2017-12-20 15:20           ` Niklas Söderlund
2018-01-08 16:35           ` Laurent Pinchart
2018-01-08 16:42             ` Niklas Söderlund
2018-01-08 16:42               ` Niklas Söderlund
2018-01-08 17:48               ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 08/28] rcar-vin: move functions regarding scaling Niklas Söderlund
2017-12-08  8:28   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 09/28] rcar-vin: all Gen2 boards can scale simplify logic Niklas Söderlund
2017-12-08  8:33   ` Laurent Pinchart
2017-12-20 16:17     ` Niklas Söderlund
2017-12-20 16:17       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 10/28] rcar-vin: do not reset crop and compose when setting format Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 11/28] rcar-vin: do not allow changing scaling and composing while streaming Niklas Söderlund
2017-12-08  9:04   ` Laurent Pinchart
2017-12-08 14:14     ` Niklas Söderlund
2017-12-08 14:14       ` Niklas Söderlund
2017-12-08 19:20       ` Laurent Pinchart
2017-12-20 16:26         ` Niklas Söderlund
2017-12-20 16:26           ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 12/28] rcar-vin: read subdevice format for crop only when needed Niklas Söderlund
2017-12-08  9:11   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 13/28] rcar-vin: fix handling of single field frames (top, bottom and alternate fields) Niklas Söderlund
2017-12-08  9:35   ` Laurent Pinchart
2017-12-08 14:06     ` Niklas Söderlund
2017-12-08 14:06       ` Niklas Söderlund
2017-12-08 19:30       ` Laurent Pinchart
2017-12-20 17:17         ` Niklas Söderlund
2017-12-20 17:17           ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 14/28] rcar-vin: move media bus configuration to struct rvin_info Niklas Söderlund
2017-12-08  9:40   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 15/28] rcar-vin: enable Gen3 hardware configuration Niklas Söderlund
2017-12-08  9:47   ` Laurent Pinchart
2017-12-20 21:09     ` Niklas Söderlund
2017-12-20 21:09       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 16/28] rcar-vin: add function to manipulate Gen3 chsel value Niklas Söderlund
2017-12-08  9:52   ` Laurent Pinchart
2017-12-20 21:20     ` Niklas Söderlund
2017-12-20 21:20       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 17/28] rcar-vin: add flag to switch to media controller mode Niklas Söderlund
2017-12-08  9:52   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 18/28] rcar-vin: break out format alignment and checking Niklas Söderlund
2017-12-08 10:01   ` Laurent Pinchart
2017-12-21  0:25     ` Niklas Söderlund
2017-12-21  0:25       ` Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 19/28] rcar-vin: use different v4l2 operations in media controller mode Niklas Söderlund
2017-12-08 10:14   ` Laurent Pinchart
2017-12-08 10:24     ` Hans Verkuil
2017-12-08 19:31       ` Laurent Pinchart
2018-01-19  0:46     ` Niklas Söderlund
2018-01-19  0:46       ` Niklas Söderlund
2018-03-02 11:33       ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 20/28] rcar-vin: prepare for media controller mode initialization Niklas Söderlund
2017-12-08 10:20   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 21/28] rcar-vin: add group allocator functions Niklas Söderlund
2017-12-08 20:12   ` Laurent Pinchart
2018-01-08 17:24     ` Niklas Söderlund
2018-01-08 17:24       ` Niklas Söderlund
2018-01-08 17:57       ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 22/28] rcar-vin: add chsel information to rvin_info Niklas Söderlund
2017-12-08 20:37   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 23/28] rcar-vin: parse Gen3 OF and setup media graph Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 24/28] rcar-vin: add link notify for Gen3 Niklas Söderlund
2017-12-08  1:08 ` [PATCH v9 25/28] rcar-vin: extend {start,stop}_streaming to work with media controller Niklas Söderlund
2017-12-08 20:45   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 26/28] rcar-vin: enable support for r8a7795 Niklas Söderlund
2017-12-08 10:21   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 27/28] rcar-vin: enable support for r8a7796 Niklas Söderlund
2017-12-08 10:25   ` Laurent Pinchart
2017-12-08  1:08 ` [PATCH v9 28/28] rcar-vin: enable support for r8a77970 Niklas Söderlund

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=20171208125532.GL31989@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=hverkuil@xs4all.nl \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=tomoharu.fukawa.eb@renesas.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.