From: Michael Walle <mwalle@kernel.org>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: Inki Dae <inki.dae@samsung.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Tim Harvey <tharvey@gateworks.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE
Date: Tue, 14 Nov 2023 16:53:40 +0100 [thread overview]
Message-ID: <a180549d4fe67492cd2080f807ea3c66@kernel.org> (raw)
In-Reply-To: <11fe6f0e-49e7-44d4-a31a-3b739f77489f@kontron.de>
Hi,
> My current guess would be that the issue I was seeing was already fixed
> with dd9e329af723 ("drm/bridge: ti-sn65dsi83: Fix enable/disable flow
> to
> meet spec") and I didn't properly test both changes separately.
I had the exact same thought, as I've found your second patch.
> My cheap scope is not able to capture the DSI signals and I admit that
> we didn't use our more expensive equipment to verify the changes back
> then.
>
> Instead, we had an automated test setup to do cyclic on/off switching
> for the display and check for a black screen using a sensor. It is
> quite
> a hassle to set up and I'm currently not planning to spend that much
> effort to verify this change again.
That is actually, what we are also doing right now and how the issue was
found in the first place.
> Anyway, I currently don't see any reasons to not revert my changes.
> Your
> revert looks correct and seems to work fine as far as I can tell.
>
> Reviewed-by: Frieder Schrempf <frieder.schrempf@kontron.de>
Thanks!
-michael
next prev parent reply other threads:[~2023-11-14 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 16:43 [PATCH] drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE Michael Walle
2023-11-14 7:15 ` Alexander Stein
2023-11-14 8:52 ` Michael Walle
2023-11-14 14:29 ` Frieder Schrempf
2023-11-14 15:53 ` Michael Walle [this message]
2023-12-01 9:04 ` Michael Walle
2023-12-18 11:24 ` Frieder Schrempf
[not found] ` <CAAQKjZMccDwa63_PNJCP0rNOaHjTwcOz8AbKa=JXLQi-b0QVVw@mail.gmail.com>
2024-01-09 8:47 ` Michael Walle
2024-01-09 12:50 ` Daniel Vetter
[not found] ` <CAAQKjZNnJQDn_r1+WNmsxM-2O48O0+yWAUAqpjZRjMYMT3xGwg@mail.gmail.com>
2024-01-26 18:28 ` Dave Airlie
2024-01-29 9:20 ` Frieder Schrempf
2024-01-29 16:51 ` Frieder Schrempf
2024-01-29 10:32 ` Michael Walle
2024-01-29 10:39 ` Michael Walle
2024-01-29 16:06 ` Michael Walle
2024-01-30 9:11 ` Dario Binacchi
2024-01-30 9:24 ` Michael Walle
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=a180549d4fe67492cd2080f807ea3c66@kernel.org \
--to=mwalle@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=inki.dae@samsung.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=tharvey@gateworks.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