mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ramón Jesús Miranda" <ramonjesusmiranda@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Jessica Zhang <jesszhan0024@gmail.com>,
	Sean Paul <sean@poorly.run>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dpu: keep vblank enabled when entering self refresh
Date: Sun, 25 Oct 2026 12:53:27 +0000	[thread overview]
Message-ID: <20261025125327.208328-1-ramonjesusmiranda@gmail.com> (raw)
In-Reply-To: <9ee7225b-588b-4253-b766-5e6ee6dffb04@oss.qualcomm.com>

On 10/19/26 3:27 PM, Konrad Dybcio wrote:
> FWIW this is not enough to get self-refresh to work on the Glymur
> Zenbook A16 and the 8280-based x13s, the screen stays black if
> there's no updates (it worked on the latter in the past). Dmitry promised
> to take a look one day.

Thanks. For the record, I had already withdrawn this patch after the
sashiko-bot review (the self refresh exit path, and the vblank worker
touching DPU registers after the last runtime PM reference is gone). It
was never meant to make self refresh work, only to avoid the atomic
helper warning about vblank being disabled on a self refresh "disable".

I have no fix for the black screen, but I am happy to test whatever
Dmitry comes up with on the Surface Pro 11 (x1e80100, OLED eDP panel).

Ramón

  reply	other threads:[~2026-10-25 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 15:54 Ramón Jesús Miranda
2026-10-19 13:27 ` Konrad Dybcio
2026-10-25 12:53   ` Ramón Jesús Miranda [this message]
     [not found] <sashiko-outbox-176261@kernel.org>
2026-10-18 21:56 ` Ramón Jesús Miranda

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=20261025125327.208328-1-ramonjesusmiranda@gmail.com \
    --to=ramonjesusmiranda@gmail.com \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    /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
all inboxes | Powered by JetHome®