From: Lyude Paul <lyude@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Nouveau Dev <nouveau@lists.freedesktop.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH 1/2] drm/nouveau: Disable atomic support on a per-device basis
Date: Mon, 17 Sep 2018 13:34:42 -0400 [thread overview]
Message-ID: <0e4daed3142fb0c1ceca5ea6af1754f319d62cc3.camel@redhat.com> (raw)
In-Reply-To: <CAKMK7uF9RadM916KwZum6GeKpXaHbi_mhWqkq3M+08Bf_LRS+w@mail.gmail.com>
On Fri, 2018-09-14 at 10:11 +0200, Daniel Vetter wrote:
> On Thu, Sep 13, 2018 at 11:02 PM, Lyude Paul <lyude@redhat.com> wrote:
> > Hm, one nitpick here. Since /sys/kernel/debug/dri/*/state creation depends
> > on
> > the driver supporting atomic, maybe it would be good to make it so that we
> > set
> > DRIVER_ATOMIC in the driver_stub structure, then disable it per-device
> > depending
> > on the nouveau_atomic setting + hw support. That way we can always have the
> > state debugfs file while maintaining nouveau's current behavior with
> > exposing
> > atomic ioctls. Assuming that wouldn't have any unintended side-effects of
> > course
>
> dri/*/state only works with atomic drivers. There's no explicit state
> with legacy drivers at all, it's all just implicit in hw and some
> random driver structures.
>
> We should make sure though that the debugfs stuff looks at
> drm_drv_uses_atomic_modsetting(), and not DRIVER_ATOMIC. Former is
> about the internals (i915 is internally atomic everywhere), latter
> about the uapi (some old platforms aren't properly validated for full
> atomic features, hence why it's disabled).
> -Daniel
Makes sense, it seems doing that results in exactly what I wanted with nouveau!
As for this patch:
Reviewed-by: Lyude Paul <lyude@redhat.com>
>
> > On Thu, 2018-09-13 at 19:31 +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > We now have per-device driver_features, so let's use that
> > > to disable atomic only for pre-nv50.
> > >
> > > Cc: Ben Skeggs <bskeggs@redhat.com>
> > > Cc: Lyude Paul <lyude@redhat.com>
> > > Cc: nouveau@lists.freedesktop.org
> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > ---
> > > drivers/gpu/drm/nouveau/dispnv04/disp.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/nouveau/dispnv04/disp.c
> > > b/drivers/gpu/drm/nouveau/dispnv04/disp.c
> > > index 70dce544984e..670535a68d3b 100644
> > > --- a/drivers/gpu/drm/nouveau/dispnv04/disp.c
> > > +++ b/drivers/gpu/drm/nouveau/dispnv04/disp.c
> > > @@ -56,7 +56,7 @@ nv04_display_create(struct drm_device *dev)
> > > nouveau_display(dev)->fini = nv04_display_fini;
> > >
> > > /* Pre-nv50 doesn't support atomic, so don't expose the ioctls */
> > > - dev->driver->driver_features &= ~DRIVER_ATOMIC;
> > > + dev->driver_features &= ~DRIVER_ATOMIC;
> > >
> > > nouveau_hw_save_vga_fonts(dev, 1);
> > >
>
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-17 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 16:31 [PATCH 1/2] drm/nouveau: Disable atomic support on a per-device basis Ville Syrjala
2018-09-13 16:31 ` [PATCH 2/2] drm/amdgpu: Use per-device driver_features to disable atomic Ville Syrjala
2018-09-13 16:38 ` Michel Dänzer
2018-09-13 16:40 ` Alex Deucher
2018-09-13 18:29 ` Ville Syrjälä
2018-09-20 18:55 ` Harry Wentland
[not found] ` <20180913163147.27900-1-ville.syrjala-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-09-13 21:02 ` [PATCH 1/2] drm/nouveau: Disable atomic support on a per-device basis Lyude Paul
2018-09-14 8:11 ` Daniel Vetter
2018-09-17 17:34 ` Lyude Paul [this message]
[not found] ` <9df77326cf0ed944e52091230df129a06872696d.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-14 15:04 ` Ville Syrjälä
2018-09-14 7:45 ` kbuild test robot
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=0e4daed3142fb0c1ceca5ea6af1754f319d62cc3.camel@redhat.com \
--to=lyude@redhat.com \
--cc=bskeggs@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
/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).