From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: VT console blank ignored by DRM drivers on QEMU
Date: Tue, 11 Jul 2017 20:10:33 +0200 [thread overview]
Message-ID: <s5hshi2g7za.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAKMK7uGLFiqLdMorw8ipNaEDZW578LoGR0QbiiQA=6-FCud-+A@mail.gmail.com>
On Tue, 11 Jul 2017 19:35:36 +0200,
Daniel Vetter wrote:
>
> On Mon, Jul 10, 2017 at 4:56 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Jul 10, 2017 at 11:37 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >>> DPMS should be an error anyway, we want that to be able to properly
> >>> thread the acquire_ctx EDEADLK backoff stuff through that we need for
> >>> atomic. That would be the best long-term plan I think.
> >>
> >> So it implies the conversions of the whole legacy stuff?
> >> That'd be great but take a long way :)
> >>
> >>> But aside from that, can't we just teach these drivers to properly do
> >>> dpms? With the atomic framework dpms is implement as simply turning
> >>> the screen off, any driver should be able to support that properly.
> >>
> >> It seems that QEMU doesn't support it yet? We'd need to implement it
> >> at first there.
> >
> > I meant to say that adding an error code to the dpms callback seems
> > like a good idea, because we need that anyway. You can ignore the
> > blabla about why exactly atomic drivers need it, and ofc I'm not going
> > to suggest that you convert all your drivers over to atomic first.
>
> I just realized that we've switched the dpms callback from void to int
> return type a while ago. So only thing you'd need to do is wire up the
> return code through the fbdev helpers, and fix up the virtual drivers
> to not allow dpms.
Hmm, as of 4.13-rc1, I see some inconsistencies:
In drm_connector.h:
struct drm_connector_funcs {
int (*dpms)(struct drm_connector *connector, int mode);
In drm_encoder_slave.h:
struct drm_encoder_slave_funcs {
void (*dpms)(struct drm_encoder *encoder, int mode);
In drm_modeset_helper_vtables.h:
struct drm_crtc_helper_funcs {
void (*dpms)(struct drm_crtc *crtc, int mode);
struct drm_encoder_helper_funcs {
void (*dpms)(struct drm_encoder *encoder, int mode);
Takashi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-11 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:53 VT console blank ignored by DRM drivers on QEMU Takashi Iwai
2017-07-10 9:27 ` Daniel Vetter
2017-07-10 9:37 ` Takashi Iwai
2017-07-10 9:49 ` Alexander Graf
2017-07-10 14:56 ` Daniel Vetter
2017-07-11 17:35 ` Daniel Vetter
2017-07-11 18:10 ` Takashi Iwai [this message]
2017-07-11 20:36 ` Daniel Vetter
2017-07-10 11:47 ` Gerd Hoffmann
2017-07-10 14:41 ` Takashi Iwai
2017-07-10 14:57 ` Daniel Vetter
2017-07-10 20:08 ` [PATCH] fbcon: Perform generic blank unconditionally kbuild test robot
2017-07-10 14:54 ` VT console blank ignored by DRM drivers on QEMU Daniel Vetter
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=s5hshi2g7za.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=agraf@suse.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.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