From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Andrzej Hajda <a.hajda@samsung.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: [PATCH v2 00/10] R-Car DU: LVDS dual-link mode support
Date: Sun, 12 May 2019 13:15:47 +0300 [thread overview]
Message-ID: <20190512101547.GA4960@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdWqvKXXfjSAk3GRyk8fwa2TS+EwcV_n0YwcEU9d8XohUA@mail.gmail.com>
Hi Geert,
On Sun, May 12, 2019 at 10:55:20AM +0200, Geert Uytterhoeven wrote:
> On Sat, May 11, 2019 at 11:07 PM Laurent Pinchart wrote:
> > On the receiving side, the THC63LVD1024 LVDS-to-parallel bridge has two
> > LVDS inputs and two parallel outputs. It can operate in four different
> > modes:
> >
> > - Single-in, single-out: The first LVDS input receives the video stream,
> > and the bridge outputs it on the first parallel output. The second
> > LVDS input and the second parallel output are not used.
> >
> > - Single-in, dual-out: The first LVDS input receives the video stream,
> > and the bridge splits even- and odd-numbered pixels and outputs them
> > on the first and second parallel outputs. The second LVDS input is not
> > used.
> >
> > - Dual-in, single-out: The two LVDS inputs are used in dual-link mode,
> > and the bridge combines the even- and odd-numbered pixels and outputs
> > them on the first parallel output. The second parallel output is not
> > used.
> >
> > - Dual-in, dual-out: The two LVDS inputs are used in dual-link mode,
> > and the bridge outputs the even- and odd-numbered pixels on the first
> > parallel output.
>
> and the second?
I should have read "on the first and second parallel outputs
respectively" indeed.
> > The operating mode is selected by two input pins of the bridge, which
> > are connected to DIP switches on the development boards I use. The mode
> > is thus fixed from a Linux point of view.
>
> Can the state of these switches be read from software?
Unfortunately not :-(
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: [PATCH v2 00/10] R-Car DU: LVDS dual-link mode support
Date: Sun, 12 May 2019 13:15:47 +0300 [thread overview]
Message-ID: <20190512101547.GA4960@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdWqvKXXfjSAk3GRyk8fwa2TS+EwcV_n0YwcEU9d8XohUA@mail.gmail.com>
Hi Geert,
On Sun, May 12, 2019 at 10:55:20AM +0200, Geert Uytterhoeven wrote:
> On Sat, May 11, 2019 at 11:07 PM Laurent Pinchart wrote:
> > On the receiving side, the THC63LVD1024 LVDS-to-parallel bridge has two
> > LVDS inputs and two parallel outputs. It can operate in four different
> > modes:
> >
> > - Single-in, single-out: The first LVDS input receives the video stream,
> > and the bridge outputs it on the first parallel output. The second
> > LVDS input and the second parallel output are not used.
> >
> > - Single-in, dual-out: The first LVDS input receives the video stream,
> > and the bridge splits even- and odd-numbered pixels and outputs them
> > on the first and second parallel outputs. The second LVDS input is not
> > used.
> >
> > - Dual-in, single-out: The two LVDS inputs are used in dual-link mode,
> > and the bridge combines the even- and odd-numbered pixels and outputs
> > them on the first parallel output. The second parallel output is not
> > used.
> >
> > - Dual-in, dual-out: The two LVDS inputs are used in dual-link mode,
> > and the bridge outputs the even- and odd-numbered pixels on the first
> > parallel output.
>
> and the second?
I should have read "on the first and second parallel outputs
respectively" indeed.
> > The operating mode is selected by two input pins of the bridge, which
> > are connected to DIP switches on the development boards I use. The mode
> > is thus fixed from a Linux point of view.
>
> Can the state of these switches be read from software?
Unfortunately not :-(
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-12 10:16 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 21:06 [PATCH v2 00/10] R-Car DU: LVDS dual-link mode support Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-11 21:06 ` [PATCH v2 01/10] drm: bridge: Add dual_link field to the drm_bridge_timings structure Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-11 21:06 ` [PATCH v2 02/10] dt-bindings: display: bridge: thc63lvd1024: Document dual-link operation Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-12 8:58 ` Geert Uytterhoeven
2019-05-12 8:58 ` Geert Uytterhoeven
2019-05-12 10:22 ` Laurent Pinchart
2019-05-12 10:22 ` Laurent Pinchart
2019-05-14 20:17 ` Rob Herring
2019-05-14 20:17 ` Rob Herring
2019-05-11 21:06 ` [PATCH v2 03/10] drm: bridge: thc63: Report input bus mode through bridge timings Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-28 9:05 ` Jacopo Mondi
2019-05-28 9:05 ` Jacopo Mondi
2019-05-11 21:06 ` [PATCH v2 04/10] dt-bindings: display: renesas: lvds: Add renesas,companion property Laurent Pinchart
2019-05-11 21:06 ` [PATCH v2 04/10] dt-bindings: display: renesas: lvds: Add renesas, companion property Laurent Pinchart
2019-05-28 9:28 ` [PATCH v2 04/10] dt-bindings: display: renesas: lvds: Add renesas,companion property Jacopo Mondi
2019-05-28 9:28 ` Jacopo Mondi
2019-05-28 12:30 ` Laurent Pinchart
2019-05-28 12:30 ` Laurent Pinchart
2019-05-11 21:06 ` [PATCH v2 05/10] drm: rcar-du: lvds: Remove LVDS double-enable checks Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-28 9:40 ` Jacopo Mondi
2019-05-28 9:40 ` Jacopo Mondi
2019-05-11 21:06 ` [PATCH v2 06/10] drm: rcar-du: lvds: Add support for dual-link mode Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-28 9:35 ` Jacopo Mondi
2019-05-28 9:35 ` Jacopo Mondi
2019-05-28 12:46 ` Laurent Pinchart
2019-05-28 12:46 ` Laurent Pinchart
2019-05-11 21:06 ` [PATCH v2 07/10] drm: rcar-du: Skip LVDS1 output on Gen3 when using dual-link LVDS mode Laurent Pinchart
2019-05-11 21:06 ` Laurent Pinchart
2019-05-28 9:38 ` Jacopo Mondi
2019-05-28 9:38 ` Jacopo Mondi
2019-05-11 21:07 ` [PATCH v2 08/10] arm64: dts: renesas: r8a7799[05]: Point LVDS0 to its companion LVDS1 Laurent Pinchart
2019-05-11 21:07 ` Laurent Pinchart
2019-05-28 9:39 ` Jacopo Mondi
2019-05-28 9:39 ` Jacopo Mondi
2019-05-11 21:07 ` [PATCH v2 09/10] [HACK] arm64: dts: renesas: draak: Enable LVDS dual-link operation Laurent Pinchart
2019-05-11 21:07 ` Laurent Pinchart
2019-05-11 21:07 ` [PATCH v2 10/10] [HACK] arm64: dts: renesas: ebisu: " Laurent Pinchart
2019-05-11 21:07 ` Laurent Pinchart
2019-05-12 8:55 ` [PATCH v2 00/10] R-Car DU: LVDS dual-link mode support Geert Uytterhoeven
2019-05-12 8:55 ` Geert Uytterhoeven
2019-05-12 10:15 ` Laurent Pinchart [this message]
2019-05-12 10:15 ` Laurent Pinchart
2019-05-28 10:20 ` Jacopo Mondi
2019-05-28 10:20 ` Jacopo Mondi
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=20190512101547.GA4960@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=jacopo+renesas@jmondi.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.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 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.