From: Sam Ravnborg <sam@ravnborg.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: David Airlie <airlied@linux.ie>, Sean Paul <sean@poorly.run>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Thierry Reding <thierry.reding@gmail.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-amarula@amarulasolutions.com
Subject: Re: [PATCH V7 2/2] drm/panel: Add Sitronix ST7701 panel driver
Date: Sat, 12 Jan 2019 17:53:31 +0100 [thread overview]
Message-ID: <20190112165331.GA30019@ravnborg.org> (raw)
In-Reply-To: <CAMty3ZDTwAx6aY=KJCWjwRo-JxBKENTfPtjV_LkY=QaSxAjRWQ@mail.gmail.com>
Hi Jagan.
> When did .unprepare and .disable are actually called? I turn-off the
> backlight by echo 1 > /sys/class/backlight/backlight/bl_power and even
> power of the board I assume the video transmission stop so it would
> ended-up calling these, but I couldn't see prints. does it the same
> time uart dead or something? do you have any inputs on sanity testing
> of typical panels, if yes please share.
Sorry, I do not rememebr the details to help you here.
Maybe module unload and then manipulating the panel in /sys/ would
do the trick.
Sam
prev parent reply other threads:[~2019-01-12 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 12:47 [PATCH V7 1/2] dt-bindings: panel: Add Sitronix ST7701 panel documentation Jagan Teki
2019-01-11 12:47 ` [PATCH V7 2/2] drm/panel: Add Sitronix ST7701 panel driver Jagan Teki
2019-01-11 21:19 ` Sam Ravnborg
2019-01-11 21:41 ` Noralf Trønnes
2019-01-12 3:44 ` Jagan Teki
2019-01-12 10:14 ` Sam Ravnborg
2019-01-12 10:46 ` Jagan Teki
2019-01-12 12:00 ` Sam Ravnborg
2019-01-12 13:25 ` Jagan Teki
2019-01-12 15:33 ` Sam Ravnborg
2019-01-12 16:32 ` Jagan Teki
2019-01-12 16:53 ` Sam Ravnborg [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=20190112165331.GA30019@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=sean@poorly.run \
--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