From: Andreas Kemnade <andreas@kemnade.info>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: 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,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, Sebastian Reichel <sre@kernel.org>
Subject: Re: [RFC PATCH] drm: omapdrm: dsi: add refsel also for omap4
Date: Wed, 13 Sep 2023 18:52:02 +0200 [thread overview]
Message-ID: <20230913185202.6e6c5341@akphone> (raw)
In-Reply-To: <48972ab0-e4ed-11b2-31fb-ad93695a4db1@ideasonboard.com>
On Wed, 13 Sep 2023 15:11:08 +0300
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> wrote:
> On 13/09/2023 09:59, Andreas Kemnade wrote:
> > Some 3.0 source has it set behind a if (omap4).
> > Maybe it is helpful maybe not, at least in the omap4460
> > trm these bits are marked as reserved.
> > But maybe some dsi video mode panel starts magically working.
>
> Sorry, what does this mean? That this fixes something, or you are
> just guessing?
>
just diffing registers between good and bad. It does not fix anything,
just reducing the diff.
> 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.
>
after we are using displays from gpu/drm/displays?
Regards
Andreas
prev parent reply other threads:[~2023-09-13 16:52 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
2023-09-13 16:52 ` Andreas Kemnade [this message]
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=20230913185202.6e6c5341@akphone \
--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