From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Vishal Sagar <vsagar@xilinx.com>
Cc: Rob Herring <robh@kernel.org>, Hyun Kwon <hyunk@xilinx.com>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
Michal Simek <michals@xilinx.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joe@perches.com" <joe@perches.com>,
Sandip Kothari <sandipk@xilinx.com>,
Dinesh Kumar <dineshk@xilinx.com>
Subject: Re: [PATCH v3 2/3] media: dt-bindings: media: xilinx: Add Xilinx UHD-SDI Receiver Subsystem
Date: Wed, 19 Aug 2020 19:40:16 +0300 [thread overview]
Message-ID: <20200819164016.GR6049@pendragon.ideasonboard.com> (raw)
In-Reply-To: <BY5PR02MB686765691549EF38B8F842E1A75D0@BY5PR02MB6867.namprd02.prod.outlook.com>
Hi Vishal,
On Wed, Aug 19, 2020 at 01:45:34PM +0000, Vishal Sagar wrote:
> On Wednesday, July 15, 2020 9:59 PM, Laurent Pinchart wrote:
> > On Mon, Jul 13, 2020 at 12:54:47PM -0600, Rob Herring wrote:
> > > On Thu, Jun 18, 2020 at 11:03:03AM +0530, Vishal Sagar wrote:
> > > > Add bindings documentation for Xilinx UHD-SDI Receiver Subsystem.
> > > >
> > > > The Xilinx UHD-SDI Receiver Subsystem consists of SMPTE UHD-SDI (RX) IP
> > > > core, an SDI RX to Video Bridge IP core to convert SDI video to native
> > > > video and a Video In to AXI4-Stream IP core to convert native video to
> > > > AXI4-Stream.
> > > >
> > > > Signed-off-by: Vishal Sagar <vishal.sagar@xilinx.com>
> > > > ---
> > > > v3
> > > > - bpc instead of bpp
> > > > - removed bpc as required property (default to 10 bpc)
> > > > - add dt-bindings/media/xilinx-sdi.h
> > > > - made line-rate as u32 instead of string
> > > > - fixed reg
> > > > - fixed s/upto/up to/
> > > >
> > > > v2
> > > > - Removed references to xlnx,video*
> > > > - Fixed as per Sakari Ailus and Rob Herring's comments
> > > > - Converted to yaml format
> > > >
> > > > .../bindings/media/xilinx/xlnx,sdirxss.yaml | 132 ++++++++++++++++++
> > > > include/dt-bindings/media/xilinx-sdi.h | 20 +++
> > > > 2 files changed, 152 insertions(+)
> > > > create mode 100644
> > Documentation/devicetree/bindings/media/xilinx/xlnx,sdirxss.yaml
> > > > create mode 100644 include/dt-bindings/media/xilinx-sdi.h
> > > >
> > > > diff --git
> > a/Documentation/devicetree/bindings/media/xilinx/xlnx,sdirxss.yaml
> > b/Documentation/devicetree/bindings/media/xilinx/xlnx,sdirxss.yaml
> > > > new file mode 100644
> > > > index 000000000000..6cfc18ca435f
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/media/xilinx/xlnx,sdirxss.yaml
> > > > @@ -0,0 +1,132 @@
> > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > > +%YAML 1.2
> > > > +---
> > > > +$id: http://devicetree.org/schemas/media/xilinx/xlnx,sdirxss.yaml#
> > > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > > +
> > > > +
> >
> > I think a single blank line is enough.
>
> Ok I will remove extra empty line in next version.
>
> > > > +title: Xilinx SMPTE UHD-SDI Receiver Subsystem
> > > > +
> > > > +maintainers:
> > > > + - Vishal Sagar <vishal.sagar@xilinx.com>
> > > > +
> > > > +description: |
> > > > + The SMPTE UHD-SDI Receiver (RX) Subsystem allows you to quickly create systems
> > > > + based on SMPTE SDI protocols. It receives unaligned native SDI streams from
> > > > + the SDI GT PHY and outputs an AXI4-Stream video stream, native video, or
> > > > + native SDI using Xilinx transceivers as the physical layer.
> > > > +
> > > > + The subsystem consists of
> > > > + 1 - SMPTE UHD-SDI Rx
> > > > + 2 - SDI Rx to Native Video Bridge
> > > > + 3 - Video In to AXI4-Stream Bridge
> > > > +
> > > > + The subsystem can capture SDI streams in up to 12G mode 8 data streams and output
> > > > + a dual pixel per clock RGB/YUV444,422/420 10/12 bits per component AXI4-Stream.
> > > > +
> > > > +properties:
> > > > + compatible:
> > > > + items:
> > > > + - enum:
> > > > + - xlnx,v-smpte-uhdsdi-rx-ss-2.0
> > >
> > > Should be indented 2 more spaces.
> >
> > Or you could simply use
> >
> > properties:
> > compatible:
> > const: xlnx,v-smpte-uhdsdi-rx-ss-2.0
>
> Ok I will fix this in the next version.
>
> > > > +
> > > > + reg:
> > > > + maxItems: 1
> > > > +
> > > > + interrupts:
> > > > + maxItems: 1
> > > > +
> > > > + clocks:
> > > > + description: List of clock specifiers
> > >
> > > Drop. That's every 'clocks' property.
>
> Ok I will drop the description in next version.
>
> > > > + items:
> > > > + - description: AXI4-Lite clock
> > > > + - description: SMPTE UHD-SDI Rx core clock
> > > > + - description: Video clock
> > > > +
> > > > + clock-names:
> > > > + items:
> > > > + - const: s_axi_aclk
> > > > + - const: sdi_rx_clk
> > > > + - const: video_out_clk
> > > > +
> > > > + xlnx,bpc:
> > > > + description: Bits per component supported. Can be 10 or 12 bits per component only.
> > > > + allOf:
> > >
> > > You can drop the 'allOf' now.
>
> Ok will update this in next version.
>
> > > > + - $ref: "/schemas/types.yaml#/definitions/uint32"
> > > > + - enum: [10, 12]
> > >
> > > Seems like this should be a standard property?
> >
> > Rob, if my understanding is correct, this tells for how many bits per
> > component the IP core has been synthesized. I think it qualifies as a
> > vendor property, as how to express constraints on supported formats (for
> > IP cores that can be synthesized with different options) is highly
> > vendor-specific.
>
> Right Laurent. This is specific to Xilinx Video IP cores.
>
> > Vishal, I think the question I asked in the review of v2 fell through
> > the cracks. Is the documentation for the new IP core version available ?
> > Should this property only be allowed for the new version, given that in
> > v2.0 the BPC is fixed to 10 ?
>
> The new IP core is released with Vivado 2020.1 but the documentation isn't yet
> publicly updated.
>
> This property is optional and the driver defaults to 10bpc in case this property is not specified.
So how about the following ?
properties:
compatible:
enum:
- xlnx,v-smpte-uhdsdi-rx-ss-1.0
- xlnx,v-smpte-uhdsdi-rx-ss-2.0
...
xlnx,bpc:
description: ...
$ref: "/schemas/types.yaml#/definitions/uint32"
enum: [10, 12]
default: 10
...
allOf:
- if:
not:
properties:
compatible:
contains:
xlnx,v-smpte-uhdsdi-rx-ss-2.0
then:
properties:
xlnx,bpc: false
This indicates that the xlnx,bpc property isn't allowed for v1.0.
Another option would be
then:
properties:
xlnx,bpc:
const: 10
to indicate it must be equal to 10 on v1.0.
> > > > +
> > > > + xlnx,line-rate:
> > > > + description: |
> > > > + The maximum mode supported by the design. Possible values are as below
> > > > + 0 - XSDI_STD_3G - 3G mode
> > > > + 1 - XSDI_STD_6G - 6G mode
> > > > + 2 - XSDI_STD_12G_8DS - 12G mode with 8 data streams
> > > > + allOf:
> > > > + - $ref: "/schemas/types.yaml#/definitions/uint32"
> > > > + - enum: [0, 1, 2]
> > >
> > > Standard?
> >
> > For this one, I'm not sure. There's little support for SDI in the
> > kernel, and I'm sure we'll get this wrong the first time. I'd rather try
> > not to over-standardize properties before we have more examples.
>
> Right. These are specific to Xilinx SDI Rx IP configuration.
I'm not sure it's Xilinx-specific, but I think we don't have enough
examples of other SDI receivers to know if the propery could be made
generic or not.
> > > > +
> > > > + xlnx,include-edh:
> > > > + type: boolean
> > > > + description: |
> > > > + This is present when the Error Detection and Handling processor is
> > > > + enabled in design.
> > > > +
> > > > + ports:
> > > > + type: object
> > > > + description: |
> > > > + Generally the SDI port is connected to a device like SDI Broadcast camera
> > > > + which is independently controlled. Hence port@0 is a source port which can be
> > > > + connected to downstream IP which can work with AXI4 Stream data.
> > > > + properties:
> > > > + port@0:
> > > > + type: object
> > > > + description: Source port
> > > > + properties:
> > > > + reg:
> > > > + const: 0
> > > > + endpoint:
> > > > + type: object
> > > > + properties:
> > > > + remote-endpoint: true
> > > > + required:
> > > > + - remote-endpoint
> > > > + additionalProperties: false
> > > > + additionalProperties: false
> >
> > Same here, I explained in the review of v2 that we should have an input
> > port.
>
> I will add the input / sink port to this device tree node.
>
> > > > +
> > > > +required:
> > > > + - compatible
> > > > + - reg
> > > > + - interrupts
> > > > + - clocks
> > > > + - clock-names
> > > > + - xlnx,line-rate
> > > > + - ports
> > > > +
> > > > +additionalProperties: false
> > > > +
> > > > +examples:
> > > > + - |
> > > > + #include <dt-bindings/media/xilinx-sdi.h>
> > > > + uhdsdirxss: v-smpte-uhdsdi-rxss@80000000 {
> >
> > The label is not used, you can drop it.
>
> Ok. I will remove this in the next version.
>
> > > > + compatible = "xlnx,v-smpte-uhdsdi-rx-ss-2.0";
> > > > + interrupt-parent = <&gic>;
> > > > + interrupts = <0 89 4>;
> > > > + reg = <0x80000000 0x10000>;
> > > > + xlnx,include-edh;
> > > > + xlnx,line-rate = <XSDI_STD_12G_8DS>;
> > > > + clocks = <&clk_1>, <&si570_1>, <&clk_2>;
> > > > + clock-names = "s_axi_aclk", "sdi_rx_clk", "video_out_clk";
> > > > + xlnx,bpc = <10>;
> >
> > I would group the xlnx,* properties after the standard properties.
>
> Noted. Will update in next version.
>
> > > > +
> > > > + ports {
> > > > + #address-cells = <1>;
> > > > + #size-cells = <0>;
> > > > + port@0 {
> > > > + reg = <0>;
> > > > + sdirx_out: endpoint {
> > > > + remote-endpoint = <&vcap_sdirx_in>;
> > > > + };
> > > > + };
> > > > + };
> > > > + };
> > > > +...
> > > > diff --git a/include/dt-bindings/media/xilinx-sdi.h b/include/dt-bindings/media/xilinx-sdi.h
> > > > new file mode 100644
> > > > index 000000000000..11938fade041
> > > > --- /dev/null
> > > > +++ b/include/dt-bindings/media/xilinx-sdi.h
> > > > @@ -0,0 +1,20 @@
> > > > +/* SPDX-License-Identifier: GPL-2.0 */
> > > > +/*
> > > > + * Xilinx SDI device tree bindings
> > > > + *
> > > > + * Copyright (C) 2020 Xilinx, Inc.
> > > > + *
> > > > + * Contacts: Vishal Sagar <vishal.sagar@xilinx.com>
> > > > + */
> > > > +
> > > > +#ifndef __DT_BINDINGS_MEDIA_XILINX_SDI_H__
> > > > +#define __DT_BINDINGS_MEDIA_XILINX_SDI_H__
> > > > +
> > > > +/*
> > > > + * SDI Configurations
> > > > + */
> > > > +#define XSDI_STD_3G 0
> > > > +#define XSDI_STD_6G 1
> > > > +#define XSDI_STD_12G_8DS 2
> > > > +
> > > > +#endif /* __DT_BINDINGS_MEDIA_XILINX_SDI_H__ */
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-08-19 16:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 5:33 [PATCH v3 0/3] Add support for Xilinx UHD-SDI Receiver subsystem Vishal Sagar
2020-06-18 5:33 ` [PATCH v3 1/3] v4l2-dv-timings: Add timings for 1920x1080P48 and 4KP48 Vishal Sagar
2020-07-15 16:16 ` Laurent Pinchart
2020-06-18 5:33 ` [PATCH v3 2/3] media: dt-bindings: media: xilinx: Add Xilinx UHD-SDI Receiver Subsystem Vishal Sagar
2020-07-13 18:54 ` Rob Herring
2020-07-15 16:29 ` Laurent Pinchart
2020-08-19 13:45 ` Vishal Sagar
2020-08-19 16:40 ` Laurent Pinchart [this message]
2020-08-24 1:00 ` Laurent Pinchart
2020-06-18 5:33 ` [PATCH v3 3/3] media: v4l: xilinx: Add Xilinx UHD-SDI Rx Subsystem driver Vishal Sagar
2020-06-18 6:53 ` kernel test robot
2020-06-18 8:13 ` kernel test robot
2020-06-25 9:43 ` Hans Verkuil
2020-07-15 21:33 ` Laurent Pinchart
2020-08-19 13:47 ` Vishal Sagar
2020-08-19 16:56 ` Laurent Pinchart
2020-08-26 14:10 ` Nicolas Dufresne
2020-08-26 14:50 ` Vishal Sagar
2020-09-10 10:22 ` Hans Verkuil
2020-09-15 2:38 ` Laurent Pinchart
2020-09-15 8:31 ` Hans Verkuil
2020-08-19 13:47 ` Vishal Sagar
2020-07-15 22:42 ` Hyun Kwon
2020-08-19 13:48 ` Vishal Sagar
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=20200819164016.GR6049@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dineshk@xilinx.com \
--cc=hverkuil@xs4all.nl \
--cc=hyunk@xilinx.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=michals@xilinx.com \
--cc=robh@kernel.org \
--cc=sandipk@xilinx.com \
--cc=vsagar@xilinx.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 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).