[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b18d88302acfca001a6693d78909bc2a@kernel.org>
Date: Mon, 29 Jan 2024 11:32:02 +0100
From: Michael Walle <mwalle@...nel.org>
To: Dave Airlie <airlied@...il.com>
Cc: Inki Dae <daeinki@...il.com>, Neil Armstrong
<neil.armstrong@...aro.org>, Laurent Pinchart
<Laurent.pinchart@...asonboard.com>, Robert Foss <rfoss@...nel.org>, Frieder
Schrempf <frieder.schrempf@...tron.de>, Jagan Teki
<jagan@...rulasolutions.com>, Andrzej Hajda <andrzej.hajda@...el.com>, Marek
Szyprowski <m.szyprowski@...sung.com>, Jonas Karlman <jonas@...boo.se>,
Jernej Skrabec <jernej.skrabec@...il.com>, Tim Harvey
<tharvey@...eworks.com>, Alexander Stein <alexander.stein@...tq-group.com>,
linux-kernel@...r.kernel.org, DRI mailing list
<dri-devel@...ts.freedesktop.org>, Daniel Vetter <daniel@...ll.ch>, Michael
Trimarchi <michael@...rulasolutions.com>, Dario Binacchi
<dario.binacchi@...rulasolutions.com>, Dmitry Osipenko
<dmitry.osipenko@...labora.com>
Subject: Re: [PATCH] drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE
> Just FYI this conflictted pretty heavily with drm-misc-next changes in
> the same area, someone should check drm-tip has the correct
> resolution, I'm not really sure what is definitely should be.
FWIW, this looks rather messy now. The drm-tip doesn't build.
There was a new call to samsung_dsim_set_stop_state() introduced
in commit b2fe2292624ac (drm: bridge: samsung-dsim: enter display
mode in the enable() callback).
Also merge commit 663a907e199b (Merge remote-tracking branch
'drm-misc/drm-misc-next' into drm-tip) is broken because it
completely removes samsung_dsim_atomic_disable(). Dunno whats
going on there.
I'm just about to look at getting it to compile again and
I'm trying to retest it.
-michael
Powered by blists - more mailing lists