CIP-dev Archive on
 help / color / Atom feed
From: "Pavel Machek" <>
To: Biju Das <>
	Nobuhiro Iwamatsu <>,
	Pavel Machek <>,
	Chris Paterson <>,
	Prabhakar Mahadev Lad <>
Subject: Re: [cip-dev] [PATCH 4.19.y-cip] drm: rcar-du: Fix crash when using LVDS1 clock for CRTC
Date: Tue, 13 Apr 2021 12:12:11 +0200
Message-ID: <20210413101210.GC26782@amd> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]


> From: Laurent Pinchart <>
> [ Upstream commit 53ced169373aab52d3b5da0fee6a342002d1876d ]
> On D3 and E3 platforms, the LVDS encoder includes a PLL that can
> generate a clock for the corresponding CRTC, used even when the CRTC
> output to a non-LVDS port. This mechanism is supported by the driver,
> but the implementation is broken in dual-link LVDS mode. In that case,
> the LVDS1 drm_encoder is skipped, which causes a crash when trying to
> access its bridge later on.
> Fix this by storing bridge pointers internally instead of retrieving
> them from the encoder. The rcar_du_device encoders field isn't used
> anymore and can be dropped.

The patch looks okay to me. I'll test it and can apply it if it works

But I don't believe it is in our 5.10, so I'd like it to be submitted
for 5.10, too.

Or just tell me it is okay and I'll apply it there, too.

Best regards,

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 428 bytes --]

Links: You receive all messages sent to this group.
View/Reply Online (#6365):
Mute This Topic:
Group Owner:
Unsubscribe: []

  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-04-12  7:19 ` Nobuhiro Iwamatsu
2021-04-12  7:25   ` Biju Das
2021-04-13 10:12 ` Pavel Machek [this message]
2021-04-13 10:18   ` Biju Das
2021-04-13 11:21     ` Pavel Machek
2021-04-13 11:25       ` Biju Das

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 \
    --in-reply-to=20210413101210.GC26782@amd \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

CIP-dev Archive on

Archives are clonable:
	git clone --mirror cip-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 cip-dev cip-dev/ \
	public-inbox-index cip-dev

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone