From: Sam Ravnborg <sam@ravnborg.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Purism Kernel Team <kernel@puri.sm>,
Thierry Reding <thierry.reding@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/panel: jh057n00900: Move dsi init sequence to prepare
Date: Fri, 26 Jul 2019 12:25:29 +0200 [thread overview]
Message-ID: <20190726102529.GB15658@ravnborg.org> (raw)
In-Reply-To: <cover.1564132646.git.agx@sigxcpu.org>
Hi Guido.
On Fri, Jul 26, 2019 at 11:21:40AM +0200, Guido Günther wrote:
> If the panel is wrapped in a panel_bridge it gets prepar()ed before the
> upstream DSI bridge which can cause hangs (e.g. with imx-nwl since clocks
> are not enabled yet). To avoid this move the panel's first DSI access to
> enable() so the upstream bridge can prepare the DSI host controller in
> it's pre_enable().
>
> The second patch makes the disable() call symmetric to the above and the third
> one just eases debugging.
>
> Guido Günther (3):
> drm/panel: jh057n00900: Move panel DSI init to enable()
> drm/panel: jh057n00900: Move mipi_dsi_dcs_set_display_off to disable()
> drm/panel: jh057n00900: Print error code on all DRM_DEV_ERROR()s
Patch 1 + 3 are both:
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
See comment on patch 2.
While you are touching this driver can you make an extra patch?
Today the driver calls the internal prepare,enable,disable,unprepare
functions.
The right way to do it is to use the
drm_panel_(prepare,enable,disable,unprepare) variants.
The benefit is that we can move a little logic to these functions
and the drivers will then benefit from this.
Two things I have in my local queue:
- Move bool for prepared/enabled
(to protect that we do not prepare/enable twice)
- backlight support
This driver will benefit form both and this little modification will
make it simpler to introduce.
I can also prepare the patch if you prefer.
Sam
next prev parent reply other threads:[~2019-07-26 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:21 [PATCH 0/3] drm/panel: jh057n00900: Move dsi init sequence to prepare Guido Günther
2019-07-26 9:21 ` [PATCH 1/3] drm/panel: jh057n00900: Move panel DSI init to enable() Guido Günther
2019-07-26 9:21 ` [PATCH 2/3] drm/panel: jh057n00900: Move mipi_dsi_dcs_set_display_off to disable() Guido Günther
2019-07-26 10:15 ` Sam Ravnborg
2019-07-26 9:21 ` [PATCH 3/3] drm/panel: jh057n00900: Print error code on all DRM_DEV_ERROR()s Guido Günther
2019-07-26 10:25 ` Sam Ravnborg [this message]
2019-07-26 13:16 ` [PATCH 0/3] drm/panel: jh057n00900: Move dsi init sequence to prepare Guido Günther
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=20190726102529.GB15658@ravnborg.org \
--to=sam@ravnborg.org \
--cc=agx@sigxcpu.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.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