lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241025080544.136280-1-mailinglist1@johanneskirchmair.de>
Date: Fri, 25 Oct 2024 10:05:44 +0200
From: mailinglist1@...anneskirchmair.de
To: aford173@...il.com
Cc: johannes.kirchmair@...data.com,
	Laurent.pinchart@...asonboard.com,
	airlied@...il.com,
	alexander.stein@...tq-group.com,
	andrzej.hajda@...el.com,
	catalin.marinas@....com,
	conor+dt@...nel.org,
	daniel@...ll.ch,
	devicetree@...r.kernel.org,
	dri-devel@...ts.freedesktop.org,
	festevam@...il.com,
	frieder.schrempf@...tron.de,
	jernej.skrabec@...il.com,
	jonas@...boo.se,
	kernel@...gutronix.de,
	kishon@...nel.org,
	krzysztof.kozlowski+dt@...aro.org,
	l.stach@...gutronix.de,
	linux-arm-kernel@...ts.infradead.org,
	linux-imx@....com,
	linux-kernel@...r.kernel.org,
	linux-phy@...ts.infradead.org,
	linux-pm@...r.kernel.org,
	maarten.lankhorst@...ux.intel.com,
	marex@...x.de,
	mripard@...nel.org,
	neil.armstrong@...aro.org,
	p.zabel@...gutronix.de,
	rfoss@...nel.org,
	robh+dt@...nel.org,
	s.hauer@...gutronix.de,
	shawnguo@...nel.org,
	tzimmermann@...e.de,
	ulf.hansson@...aro.org,
	victor.liu@....com,
	vkoul@...nel.org,
	will@...nel.org
Subject: imx8mp: HDMI display blank/black problems

Hey, 
We had some problems with the hdmi on the imx8mp and wanted to leave, what we found out about it, somewhere for others to find it.

The problem was that our hdmi display sometimes stayed blank after hot plugging and sometimes at startup. On older kernel versions 6.6 we did not have the problem with the not mainlined hdmi patches. 
We tracked the commit down that introduced the problem for us. It was the following “driver core: Enable fw_devlink=rpm by default”  https://lore.kernel.org/lkml/20231113220948.80089-1-saravanak@google.com/
So we switched back to FW_DEVLINK_FLAGS_ON via kernel parameter. Don’t really understand what the problem with RPM is.

So, this information is just for reference. Maybe someone has an idea what is going on here. And how to fix the problem in a more proper way.

Best regards Johannes

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ