From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/4] media: dt-bindings: Add property to describe CSI-2 C-PHY line orders
Date: Wed, 20 Nov 2024 10:47:41 +0100 [thread overview]
Message-ID: <20241120094741.GS5315@ragnatech.se> (raw)
In-Reply-To: <Zz2YjNHk-ZTlXztw@kekkonen.localdomain>
Hi Sakari,
Tack för din feedback!
On 2024-11-20 08:06:36 +0000, Sakari Ailus wrote:
> Hejssan, Niklas!
>
> Tack för de här lapparna!
>
> On Tue, Nov 19, 2024 at 11:12:46PM +0100, Niklas Söderlund wrote:
> > Each data lane on a CSI-2 C-PHY bus uses three phase encoding and is
> > constructed from three physical wires. The wires are referred to as A, B
> > and C and their default order is ABC. However to ease hardware design
> > the specification allows for the wires to be switched in any order.
> >
> > Add a vendor neutral property to describe the line order used. The
> > property name 'line-orders', the possible values it can be assigned and
> > there names are taken from the MIPI Discovery and Configuration (DisCo)
> > Specification for Imaging.
> >
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > ---
> > .../bindings/media/video-interfaces.yaml | 20 +++++++++++++++++++
> > include/dt-bindings/media/video-interfaces.h | 7 +++++++
> > 2 files changed, 27 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/media/video-interfaces.yaml b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> > index 26e3e7d7c67b..95491e5779ba 100644
> > --- a/Documentation/devicetree/bindings/media/video-interfaces.yaml
> > +++ b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> > @@ -210,6 +210,26 @@ properties:
> > lane-polarities property is omitted, the value must be interpreted as 0
> > (normal). This property is valid for serial busses only.
> >
> > + line-orders:
> > + $ref: /schemas/types.yaml#/definitions/uint32-array
> > + minItems: 1
> > + maxItems: 8
> > + enum:
> > + - 0 # ABC
> > + - 1 # ACB
> > + - 2 # BAC
> > + - 3 # BCA
> > + - 4 # CAB
> > + - 5 # CBA
>
> Do you know hardware documentation using lettes for the lines? I do agree
> it seems less confusing but I've seen only numbers being used.
Yes the R-Car IP core documentation and schematics uses the ABC naming
for the lines. Unfortunately the documentation is not public.
>
> > + description:
> > + An array of line orders of the CSI-2 C-PHY data lanes. The order of the
> > + lanes are the same as in data-lanes property. Valid values are 0-5 as
> > + defined in the MIPI Discovery and Configuration (DisCo) Specification for
> > + Imaging. The length of the array should be the same length as the
>
> s/should/must/
>
> As this is a requirement for DTS authors in particular.
>
> > + data-lanes property. If the line-orders property is omitted, the value
> > + must be interpreted as 0 (ABC). This property is valid for CSI-2 C-PHY
>
> I would:
>
> s/must/shall/
>
> > + busses only.
> > +
> > strobe:
> > $ref: /schemas/types.yaml#/definitions/uint32
> > enum: [ 0, 1 ]
> > diff --git a/include/dt-bindings/media/video-interfaces.h b/include/dt-bindings/media/video-interfaces.h
> > index 68ac4e05e37f..88b9d05d8075 100644
> > --- a/include/dt-bindings/media/video-interfaces.h
> > +++ b/include/dt-bindings/media/video-interfaces.h
> > @@ -13,4 +13,11 @@
> > #define MEDIA_BUS_TYPE_PARALLEL 5
> > #define MEDIA_BUS_TYPE_BT656 6
> >
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_ABC 0
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_ACB 1
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_BAC 2
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_BCA 3
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_CAB 4
> > +#define MEDIA_BUS_CSI2_CPHY_LINE_ORDER_CBA 5
> > +
> > #endif /* __DT_BINDINGS_MEDIA_VIDEO_INTERFACES_H__ */
>
> --
> Med vänliga hälsningar,
>
> Sakari Ailus
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-11-20 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 22:12 [PATCH 0/4] media: v4l: fwnode: Add support for CSI-2 C-PHY line orders Niklas Söderlund
2024-11-19 22:12 ` [PATCH 1/4] media: dt-bindings: Add property to describe " Niklas Söderlund
2024-11-19 23:26 ` Rob Herring (Arm)
2024-11-20 8:06 ` Sakari Ailus
2024-11-20 9:47 ` Niklas Söderlund [this message]
2024-11-19 22:12 ` [PATCH 2/4] media: v4l: fwnode: Parse MiPI DisCo for C-PHY line-orders Niklas Söderlund
2024-11-20 8:10 ` Sakari Ailus
2024-11-20 9:50 ` Niklas Söderlund
2024-11-20 10:18 ` Sakari Ailus
2024-11-19 22:12 ` [PATCH 3/4] arm64: dts: renesas: white-hawk-csi-dsi: Define CSI-2 data line orders Niklas Söderlund
2024-11-19 22:12 ` [PATCH 4/4] media: rcar-csi2: Allow specifying C-PHY line order 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=20241120094741.GS5315@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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.