From: Andreas Kemnade <andreas@kemnade.info>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Tony Lindgren <tony@atomide.com>,
airlied@gmail.com, daniel@ffwll.ch,
u.kleine-koenig@pengutronix.de, arnd@arndb.de,
laurent.pinchart@ideasonboard.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, Sebastian Reichel <sre@kernel.org>
Subject: Re: [RFC PATCH] drm: omapdrm: dsi: add refsel also for omap4
Date: Sun, 17 Sep 2023 16:34:35 +0200 [thread overview]
Message-ID: <20230917163435.6bc68110@akair> (raw)
In-Reply-To: <9efde4d8-385d-54da-fb0d-55625d3c4571@ideasonboard.com>
Am Wed, 13 Sep 2023 15:58:11 +0300
schrieb Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>:
> On 13/09/2023 15:48, Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> [230913 12:11]:
> >> I'm somewhat sure that the upstream driver used to work on omap4
> >> sdp, which has two DSI panels. But I can't even remember what
> >> omap4 version it had.
> >
> > I think those were both dsi command mode panels though, not video
> > mode?
>
> Yes, true. If the PLL is totally wrong due to refsel, I'm sure a
> command mode panel would also fail. But it's true that video mode
> panels are more sensitive to the clock rate.
>
hmm, still analyzing:
What works:
OMAP5 + Pyra (Videomode display requiring some init commands)
some command mode stuff with OMAP4 (droid4)
What does not work:
OMAP4 with some dsi videomode to something else (LVDS/DPI) converter
if init commands are sent through dsi, then these commands fail
with bta sync problems.
So sending init commands to video mode displays seems not to be a
principal problem.
But looking deeper at the drivers, there seem to be commands sent
to the converters to configure lanes on that side, e.g.
tc358762_write(ctx, DSI_LANEENABLE,
LANEENABLE_L0EN | LANEENABLE_CLEN);
There might be trouble if these are not sent in low power mode.
So probably the next analyzing step would be to check if things
are really sent in low power mode.
Regards,
Andreas
next prev parent reply other threads:[~2023-09-17 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 6:59 [RFC PATCH] drm: omapdrm: dsi: add refsel also for omap4 Andreas Kemnade
2023-09-13 7:15 ` Tony Lindgren
2023-09-13 12:11 ` Tomi Valkeinen
2023-09-13 12:48 ` Tony Lindgren
2023-09-13 12:58 ` Tomi Valkeinen
2023-09-17 14:34 ` Andreas Kemnade [this message]
2023-09-13 16:52 ` Andreas Kemnade
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=20230917163435.6bc68110@akair \
--to=andreas@kemnade.info \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
/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