From: Shawn Guo <shawn.guo@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Konrad Dybcio <konradybcio@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/panel: Add Truly NT35521 panel driver
Date: Mon, 9 Aug 2021 12:20:19 +0800 [thread overview]
Message-ID: <20210809042018.GD6795@dragon> (raw)
In-Reply-To: <YQ/4WkA9ajpQx06A@gerhold.net>
On Sun, Aug 08, 2021 at 05:29:30PM +0200, Stephan Gerhold wrote:
> > 2) The driver works good, if the kernel is launched via "fastboot boot".
> > But if the kernel is flashed to eMMC and launched by bootloader with
> > splash screen, kernel will fail to bring up the panel. After kernel
> > boots up, a blank & unblank cycle can get panel work though.
> >
> > The problem 2) is not driver generator related. @Konrad, did you see
> > it on asus-z00t-tm5p5-n35596 driver?
> >
>
> Do you have CONFIG_DRM_MSM=y (built-in) instead of =m (module) maybe?
> I think a similar issue exists on MSM8916 but it does not happen
> for some reason if CONFIG_DRM_MSM=m instead of =y. Somehow having it
> load later during the boot process fixes some things there.
Indeed! I have CONFIG_DRM_MSM=y in my build, and changing it to module
removes the problem. Thanks much for the hint, Stephan!
Shawn
next prev parent reply other threads:[~2021-08-09 4:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 8:13 [PATCH 0/2] Add Truly NT35521 panel driver support Shawn Guo
2021-08-04 8:13 ` [PATCH 1/2] dt-bindings: display: panel: Add Truly NT35521 panel support Shawn Guo
[not found] ` <YQq6ascrSCtErWrf@ravnborg.org>
2021-08-08 12:04 ` Shawn Guo
2021-08-11 18:51 ` Rob Herring
2021-08-13 13:59 ` Shawn Guo
2021-08-04 8:13 ` [PATCH 2/2] drm/panel: Add Truly NT35521 panel driver Shawn Guo
2021-08-04 12:09 ` Stephan Gerhold
2021-08-08 13:44 ` Shawn Guo
2021-08-08 15:29 ` Stephan Gerhold
2021-08-09 4:20 ` Shawn Guo [this message]
[not found] ` <YQq/LOWEgTIk9zIT@ravnborg.org>
2021-08-08 13:49 ` Shawn Guo
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=20210809042018.GD6795@dragon \
--to=shawn.guo@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=stephan@gerhold.net \
--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;
as well as URLs for NNTP newsgroup(s).