From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tony Lindgren <tony@atomide.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Jyri Sarha <jsarha@ti.com>,
kernel@pyra-handheld.com,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>, David Shah <dave@ds0.me>
Subject: Re: module_mipi_dsi_driver panel with omapdrm?
Date: Wed, 5 Aug 2020 13:49:07 +0200 [thread overview]
Message-ID: <0DDD1D3E-4F63-44B4-91CA-1B5B853837BC@goldelico.com> (raw)
In-Reply-To: <20200805112831.akufm5wxkwqehiff@earth.universe>
Hi,
> Am 05.08.2020 um 13:28 schrieb Sebastian Reichel <sebastian.reichel@collabora.com>:
>
> Hi,
>
> On Wed, Aug 05, 2020 at 11:19:20AM +0200, H. Nikolaus Schaller wrote:
>> What I do not yet understand is how Laurent's patch should be able
>> to break it.
>
> omapdrm will not probe successfully if any DT enabled component
> does not probe correctly. Since the patch you identified touched
> HDMI and VENC and you are probably using HDMI, I suggest looking
> there first.
Yes, that is a very good explanation.
Maybe there is a subtle change in how the HDMI connector has to be defined
which is missing in our (private) DTB. Maybe the OMAP5-uEVM DTS gives a hint.
A quick check shows last hdmi specific change for omap5-board-common or uevm
was in 2017 but I may have missed something.
There are 715a5a978733f0 and 671ab615bd507f which arrived in v5.7-rc1 as well
and are related to hdmi clocks. So this may be (or not) and influencing factor.
BR and thanks,
Nikolaus
next prev parent reply other threads:[~2020-08-05 16:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 6:52 OMAP5: inconsistency between target-module and dsi_of_data_omap5 H. Nikolaus Schaller
2020-07-05 7:40 ` H. Nikolaus Schaller
2020-07-05 13:47 ` H. Nikolaus Schaller
2020-07-05 14:26 ` Tony Lindgren
2020-07-05 14:36 ` Tony Lindgren
2020-07-05 15:40 ` H. Nikolaus Schaller
2020-07-06 14:36 ` Tony Lindgren
2020-07-06 16:10 ` H. Nikolaus Schaller
2020-07-07 18:01 ` Tony Lindgren
2020-07-07 19:04 ` H. Nikolaus Schaller
2020-07-08 7:52 ` OMAP5: inconsistency between target-module and dsi_of_data_omap5 / module_mipi_dsi_driver panel with omapdrm H. Nikolaus Schaller
2020-07-23 7:03 ` Re:module_mipi_dsi_driver panel with omapdrm? H. Nikolaus Schaller
2020-07-24 1:24 ` module_mipi_dsi_driver " Laurent Pinchart
2020-07-24 5:50 ` H. Nikolaus Schaller
2020-08-01 13:43 ` H. Nikolaus Schaller
2020-08-01 23:22 ` Sebastian Reichel
2020-08-05 9:19 ` H. Nikolaus Schaller
2020-08-05 11:28 ` Sebastian Reichel
2020-08-05 11:49 ` H. Nikolaus Schaller [this message]
2020-08-05 12:08 ` Tomi Valkeinen
2020-08-06 15:50 ` David Shah
2020-08-06 16:04 ` [Letux-kernel] " David Shah
2020-08-06 18:44 ` David Shah
2020-08-06 19:01 ` H. Nikolaus Schaller
2020-08-06 19:44 ` David Shah
2020-08-07 6:53 ` Tomi Valkeinen
2020-08-16 11:24 ` H. Nikolaus Schaller
2020-08-18 9:16 ` Tony Lindgren
2020-08-04 12:43 ` Tomi Valkeinen
2020-08-05 9:25 ` H. Nikolaus Schaller
2020-08-05 11:07 ` Sebastian Reichel
2020-08-05 11:14 ` H. Nikolaus Schaller
[not found] <E1k3Hyu-0000Ac-BU@ds0.me>
2020-08-05 12:00 ` H. Nikolaus Schaller
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=0DDD1D3E-4F63-44B4-91CA-1B5B853837BC@goldelico.com \
--to=hns@goldelico.com \
--cc=dave@ds0.me \
--cc=jsarha@ti.com \
--cc=kernel@pyra-handheld.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-omap@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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 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).