From: Doug Anderson <dianders@google.com>
To: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
Cc: sam@ravnborg.org, neil.armstrong@linaro.org, daniel@ffwll.ch,
hsinyi@google.com, linus.walleij@linaro.org,
swboyd@chromium.org, airlied@gmail.com,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v1 2/2] drm/panel: ili9882t: Avoid blurred screen from fast sleep
Date: Mon, 9 Oct 2023 13:44:34 -0700 [thread overview]
Message-ID: <CAD=FV=W3ef3vWrWRDPKgeUjcapEticj4=EWdC-bOb=ph0DShsA@mail.gmail.com> (raw)
In-Reply-To: <20231007060639.725350-3-yangcong5@huaqin.corp-partner.google.com>
Hi,
On Fri, Oct 6, 2023 at 11:07 PM Cong Yang
<yangcong5@huaqin.corp-partner.google.com> wrote:
>
> At present, we have found that there may be a problem of blurred
> screen during fast sleep/resume. The direct cause of the blurred
> screen is that the IC does not receive 0x28/0x10. Because of the
> particularity of the IC, before the panel enters sleep hid must
> stop scanning, i2c_hid_core_suspend before ili9882t_disable.
> This doesn't look very spec-compliant.
Presumably you could be more spec compliant if we used
"panel_follower" in this case? Would that be a better solution?
> So in order to solve this
> problem, the IC can handle it through the exception mechanism when
> it cannot receive 0X28/0X10 command. Handling exceptions requires a reset
> 50ms delay. Refer to vendor detailed analysis [1].
>
> Ilitek vendor also suggested switching the page before entering sleep to
> avoid panel IC not receiving 0x28/0x10 command.
>
> Note: 0x28 is display off, 0x10 is sleep in.
>
> [1]: https://github.com/ILITEK-LoganLin/Document/tree/main/ILITEK_Power_Sequence
>
> Signed-off-by: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
> ---
> drivers/gpu/drm/panel/panel-ilitek-ili9882t.c | 21 ++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-ilitek-ili9882t.c b/drivers/gpu/drm/panel/panel-ilitek-ili9882t.c
> index bbfcffe65623..0a1dd987b204 100644
> --- a/drivers/gpu/drm/panel/panel-ilitek-ili9882t.c
> +++ b/drivers/gpu/drm/panel/panel-ilitek-ili9882t.c
> @@ -423,6 +423,23 @@ static inline struct ili9882t *to_ili9882t(struct drm_panel *panel)
> return container_of(panel, struct ili9882t, base);
> }
>
> +static int ili9882t_switch_page(struct mipi_dsi_device *dsi, u8 page)
> +{
> + u8 switch_cmd[] = {0x98, 0x82, 0x00};
Can't you just replace the last 0x00 above with "page" and get rid of
the manual assignment below?
> + int ret;
> +
> + switch_cmd[2] = page;
> +
> + ret = mipi_dsi_dcs_write(dsi, ILI9882T_DCS_SWITCH_PAGE, switch_cmd, 3);
Instead of hardcoding 3, should use ARRAY_SIZE().
> + if (ret) {
> + dev_err(&dsi->dev,
> + "error switching panel controller page (%d)\n", ret);
> + return ret;
> + }
> +
> + return 0;
> +}
optional: It feels like it would be nice to somehow use the
"_INIT_SWITCH_PAGE_CMD" macro I suggested in patch #1 instead of
having to hardcode 0x98, 0x82 again. In patch #1 I already suggested
breaking out the function to send a sequence of commands. If you had
that function take a pointer instead of hardcoding it to look at
->init_cmds then you could probably use the same function that you do
at init time?
> static int ili9882t_enter_sleep_mode(struct ili9882t *ili)
> {
> struct mipi_dsi_device *dsi = ili->dsi;
> @@ -444,8 +461,10 @@ static int ili9882t_enter_sleep_mode(struct ili9882t *ili)
> static int ili9882t_disable(struct drm_panel *panel)
> {
> struct ili9882t *ili = to_ili9882t(panel);
> + struct mipi_dsi_device *dsi = ili->dsi;
> int ret;
>
> + ili9882t_switch_page(dsi, 0x00);
> ret = ili9882t_enter_sleep_mode(ili);
> if (ret < 0) {
> dev_err(panel->dev, "failed to set panel off: %d\n", ret);
> @@ -507,7 +526,7 @@ static int ili9882t_prepare(struct drm_panel *panel)
> gpiod_set_value(ili->enable_gpio, 1);
> usleep_range(1000, 2000);
> gpiod_set_value(ili->enable_gpio, 0);
> - usleep_range(1000, 2000);
> + usleep_range(40000, 50000);
nit: use 40000, 41000 instead of 40000, 50000. Linux almost always
uses the longer delay, so that'll save ~9 ms. The only reason for the
range is to optimize kernel wakeups which is really not a concern
here.
next prev parent reply other threads:[~2023-10-09 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231007060639.725350-1-yangcong5@huaqin.corp-partner.google.com>
2023-10-08 19:33 ` [v1 0/2] Break out as separate driver from boe-tv101wum-nl6 panel driver Linus Walleij
2023-10-09 20:53 ` Doug Anderson
2023-10-09 21:02 ` Linus Walleij
2023-10-09 21:12 ` Doug Anderson
[not found] ` <20231007060639.725350-2-yangcong5@huaqin.corp-partner.google.com>
2023-10-09 20:44 ` [v1 1/2] drm/panel: ili9882t: Break out as separate driver Doug Anderson
2023-10-10 11:21 ` cong yang
[not found] ` <20231007060639.725350-3-yangcong5@huaqin.corp-partner.google.com>
2023-10-09 20:44 ` Doug Anderson [this message]
2023-10-10 11:36 ` [v1 2/2] drm/panel: ili9882t: Avoid blurred screen from fast sleep cong yang
2023-10-10 19:11 ` Doug Anderson
2023-10-11 5:47 ` cong yang
2023-10-12 12:09 ` cong yang
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='CAD=FV=W3ef3vWrWRDPKgeUjcapEticj4=EWdC-bOb=ph0DShsA@mail.gmail.com' \
--to=dianders@google.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=sam@ravnborg.org \
--cc=swboyd@chromium.org \
--cc=yangcong5@huaqin.corp-partner.google.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).