archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Jacopo Mondi <>
Cc: Laurent Pinchart <>,
	Kieran Bingham <>,
	David Airlie <>, Daniel Vetter <>,
	Fabrizio Castro <>,
	open list <>
Subject: Re: [PATCH] drm: rcar_lvds: Fix dual link mode operations
Date: Wed, 24 Jul 2019 09:28:58 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Jacopo,

On Wed, Jul 24, 2019 at 3:38 AM Jacopo Mondi <> wrote:
> The R-Car LVDS encoder units support dual-link operations by splitting
> the pixel output between the primary encoder and the companion one.
> In order for the primary encoder to succesfully control the companion's
> operations this should not fail at probe time and register itself its
> associated drm bridge so that the primary one can find it.
> Currently the companion encoder fails at probe time, causing the
> registration of the primary to fail preventing the whole DU unit to be
> registered correctly.
> Fixes: fa440d870358 ("drm: rcar-du: lvds: Add support for dual-link mode")
> Reported-by: Fabrizio Castro <>
> Signed-off-by: Jacopo Mondi <>
> ---
> The "Fixes" tag refers to a patch currently part of the
> renesas-drivers-2019-07-09-v5.2 branch of Geert's renesas-drivers tree.

The broken commit is also present in v5.3-rc1.



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2019-07-24  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 16:57 [PATCH] drm: rcar_lvds: Fix dual link mode operations Jacopo Mondi
2019-07-24  7:28 ` Geert Uytterhoeven [this message]
2019-07-24  8:37   ` Jacopo Mondi
2019-07-24  8:10 ` Fabrizio Castro
2019-08-01 15:11 ` Laurent Pinchart
2019-08-05  7:51   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).