From: Daniel Vetter <daniel.vetter@ffwll.ch> To: Thomas Zimmermann <tzimmermann@suse.de> Cc: "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>, "DRI Development" <dri-devel@lists.freedesktop.org>, "Gerd Hoffmann" <kraxel@redhat.com>, "Dave Airlie" <airlied@redhat.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Sam Ravnborg" <sam@ravnborg.org>, "Christian König" <christian.koenig@amd.com>, "Emil Velikov" <emil.velikov@collabora.com> Subject: Re: [PATCH 57/59] drm/ast: Use managed pci functions Date: Wed, 15 Apr 2020 10:17:42 +0200 [thread overview] Message-ID: <CAKMK7uEiA0SxSWBWkyfTJpo0BBr9aekzc6fa3P-HQqEjmuB8TQ@mail.gmail.com> (raw) In-Reply-To: <CAKMK7uHxN62MUJrFtWJ7oKjYPnrrMHPLZgSNVZX21BAsM=8P2w@mail.gmail.com> On Wed, Apr 15, 2020 at 10:09 AM Daniel Vetter <daniel.vetter@ffwll.ch> wrote: > > On Wed, Apr 15, 2020 at 9:52 AM Thomas Zimmermann <tzimmermann@suse.de> wrote: > > > > Hi Daniel > > > > Am 15.04.20 um 09:40 schrieb Daniel Vetter: > > > Allows us to remove a bit of cleanup code. > > > > > > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> > > > Cc: Dave Airlie <airlied@redhat.com> > > > Cc: Thomas Zimmermann <tzimmermann@suse.de> > > > Cc: Gerd Hoffmann <kraxel@redhat.com> > > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > > > Cc: Emil Velikov <emil.velikov@collabora.com> > > > Cc: "Noralf Trønnes" <noralf@tronnes.org> > > > Cc: Sam Ravnborg <sam@ravnborg.org> > > > Cc: "Christian König" <christian.koenig@amd.com> > > > Cc: "Y.C. Chen" <yc_chen@aspeedtech.com> > > > --- > > > drivers/gpu/drm/ast/ast_drv.c | 10 +++------- > > > drivers/gpu/drm/ast/ast_main.c | 3 --- > > > 2 files changed, 3 insertions(+), 10 deletions(-) > > > > > > diff --git a/drivers/gpu/drm/ast/ast_drv.c b/drivers/gpu/drm/ast/ast_drv.c > > > index b7ba22dddcad..48a9cc4e080a 100644 > > > --- a/drivers/gpu/drm/ast/ast_drv.c > > > +++ b/drivers/gpu/drm/ast/ast_drv.c > > > @@ -91,15 +91,13 @@ static int ast_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > > > > > ast_kick_out_firmware_fb(pdev); > > > > > > - ret = pci_enable_device(pdev); > > > + ret = pcim_enable_device(pdev); > > > if (ret) > > > return ret; > > > > > > dev = drm_dev_alloc(&driver, &pdev->dev); > > > - if (IS_ERR(dev)) { > > > - ret = PTR_ERR(dev); > > > - goto err_pci_disable_device; > > > - } > > > + if (IS_ERR(dev)) > > > + return PTR_ERR(dev); > > > > > > dev->pdev = pdev; > > > pci_set_drvdata(pdev, dev); > > > @@ -120,8 +118,6 @@ static int ast_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > > ast_driver_unload(dev); > > > err_drm_dev_put: > > > drm_dev_put(dev); > > > -err_pci_disable_device: > > > - pci_disable_device(pdev); > > > return ret; > > > > > > } > > > diff --git a/drivers/gpu/drm/ast/ast_main.c b/drivers/gpu/drm/ast/ast_main.c > > > index e5398e3dabe7..1b35728ad871 100644 > > > --- a/drivers/gpu/drm/ast/ast_main.c > > > +++ b/drivers/gpu/drm/ast/ast_main.c > > > @@ -531,8 +531,5 @@ void ast_driver_unload(struct drm_device *dev) > > > drm_mode_config_cleanup(dev); > > > > > > ast_mm_fini(ast); > > > - if (ast->ioregs != ast->regs + AST_IO_MM_OFFSET) > > > - pci_iounmap(dev->pdev, ast->ioregs); > > > - pci_iounmap(dev->pdev, ast->regs); > > > > This gets unmapped as part of the automatic pci_disable_device(), I guess? > > Yup, once you go with pcim_enable_device all pci_ functions on that > device become manged and auto-cleanup. > > > Do we need drm_dev_enter()/_exit() to make I/O work reliably? > > That does nothing without drm_dev_unplug(), which has the annoying > side effect that it also shuts up stuff like > drm_atomic_helper_shutdown for module unload. And developers really > want their devices to be shut off on driver unload. So yeah > unfortunately we currently can decide between "correct for hotunplug" > and "convenient for driver unload for driver authors". I'm not sure > what to best do here, since all options are kinda not great for one > use-case or the other. So if we'd split up drm_dev_unplug into drm_dev_unregister + drm_dev_mark_unplugged or whatever the options would be: drm_atomic_helper_shutdown(); /* and other hw shut down */ drm_dev_unregister(); drm_dev_mark_unplugged(); Kinda annoying since userspace might race with us, so we might still have an active fb (in sw tracking at least) that we need to clean up again later on. Plus shutting down hw before we unregister is going to make the hotunplug confusion for userspace even more a mess. Next option: drm_dev_unregster(); /* shut down hw */ drm_dev_mark_unplugged(); This just wastes time since if we're really unplugged we'll do lots of io attempts that go nowhere because the device is gone already. They'll all time out (if the bus subsystem/hw for our driver works correctly at least). Plus userspace can still sneak in and do stupid stuff I think while we're not looking. Next up: drm_dev_unregister(); drm_dev_mark_unplugged(); drm_atomic_helper_shutdown(); This is a bit silly since all the shutdown code now does is shut down sw state, and never touches hw (if the driver is fully annotated with drm_dev_enter/exit). One option might be that we slap a lot more drm_dev_enter/exit around the top-level ioctls (to at least stop the userspace races with driver unload), and allow drivers to still shut down stuff internally. tldr; it's all still a bit a mess. -Daniel > -Daniel > > > Best regards > > Thomas > > > > > kfree(ast); > > > } > > > > > > > -- > > Thomas Zimmermann > > Graphics Driver Developer > > SUSE Software Solutions Germany GmbH > > Maxfeldstr. 5, 90409 Nürnberg, Germany > > (HRB 36809, AG Nürnberg) > > Geschäftsführer: Felix Imendörffer > > > > > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch> To: Thomas Zimmermann <tzimmermann@suse.de> Cc: "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>, "DRI Development" <dri-devel@lists.freedesktop.org>, "Gerd Hoffmann" <kraxel@redhat.com>, "Dave Airlie" <airlied@redhat.com>, "Daniel Vetter" <daniel.vetter@intel.com>, "Sam Ravnborg" <sam@ravnborg.org>, "Christian König" <christian.koenig@amd.com>, "Emil Velikov" <emil.velikov@collabora.com> Subject: Re: [Intel-gfx] [PATCH 57/59] drm/ast: Use managed pci functions Date: Wed, 15 Apr 2020 10:17:42 +0200 [thread overview] Message-ID: <CAKMK7uEiA0SxSWBWkyfTJpo0BBr9aekzc6fa3P-HQqEjmuB8TQ@mail.gmail.com> (raw) In-Reply-To: <CAKMK7uHxN62MUJrFtWJ7oKjYPnrrMHPLZgSNVZX21BAsM=8P2w@mail.gmail.com> On Wed, Apr 15, 2020 at 10:09 AM Daniel Vetter <daniel.vetter@ffwll.ch> wrote: > > On Wed, Apr 15, 2020 at 9:52 AM Thomas Zimmermann <tzimmermann@suse.de> wrote: > > > > Hi Daniel > > > > Am 15.04.20 um 09:40 schrieb Daniel Vetter: > > > Allows us to remove a bit of cleanup code. > > > > > > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> > > > Cc: Dave Airlie <airlied@redhat.com> > > > Cc: Thomas Zimmermann <tzimmermann@suse.de> > > > Cc: Gerd Hoffmann <kraxel@redhat.com> > > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > > > Cc: Emil Velikov <emil.velikov@collabora.com> > > > Cc: "Noralf Trønnes" <noralf@tronnes.org> > > > Cc: Sam Ravnborg <sam@ravnborg.org> > > > Cc: "Christian König" <christian.koenig@amd.com> > > > Cc: "Y.C. Chen" <yc_chen@aspeedtech.com> > > > --- > > > drivers/gpu/drm/ast/ast_drv.c | 10 +++------- > > > drivers/gpu/drm/ast/ast_main.c | 3 --- > > > 2 files changed, 3 insertions(+), 10 deletions(-) > > > > > > diff --git a/drivers/gpu/drm/ast/ast_drv.c b/drivers/gpu/drm/ast/ast_drv.c > > > index b7ba22dddcad..48a9cc4e080a 100644 > > > --- a/drivers/gpu/drm/ast/ast_drv.c > > > +++ b/drivers/gpu/drm/ast/ast_drv.c > > > @@ -91,15 +91,13 @@ static int ast_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > > > > > ast_kick_out_firmware_fb(pdev); > > > > > > - ret = pci_enable_device(pdev); > > > + ret = pcim_enable_device(pdev); > > > if (ret) > > > return ret; > > > > > > dev = drm_dev_alloc(&driver, &pdev->dev); > > > - if (IS_ERR(dev)) { > > > - ret = PTR_ERR(dev); > > > - goto err_pci_disable_device; > > > - } > > > + if (IS_ERR(dev)) > > > + return PTR_ERR(dev); > > > > > > dev->pdev = pdev; > > > pci_set_drvdata(pdev, dev); > > > @@ -120,8 +118,6 @@ static int ast_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > > ast_driver_unload(dev); > > > err_drm_dev_put: > > > drm_dev_put(dev); > > > -err_pci_disable_device: > > > - pci_disable_device(pdev); > > > return ret; > > > > > > } > > > diff --git a/drivers/gpu/drm/ast/ast_main.c b/drivers/gpu/drm/ast/ast_main.c > > > index e5398e3dabe7..1b35728ad871 100644 > > > --- a/drivers/gpu/drm/ast/ast_main.c > > > +++ b/drivers/gpu/drm/ast/ast_main.c > > > @@ -531,8 +531,5 @@ void ast_driver_unload(struct drm_device *dev) > > > drm_mode_config_cleanup(dev); > > > > > > ast_mm_fini(ast); > > > - if (ast->ioregs != ast->regs + AST_IO_MM_OFFSET) > > > - pci_iounmap(dev->pdev, ast->ioregs); > > > - pci_iounmap(dev->pdev, ast->regs); > > > > This gets unmapped as part of the automatic pci_disable_device(), I guess? > > Yup, once you go with pcim_enable_device all pci_ functions on that > device become manged and auto-cleanup. > > > Do we need drm_dev_enter()/_exit() to make I/O work reliably? > > That does nothing without drm_dev_unplug(), which has the annoying > side effect that it also shuts up stuff like > drm_atomic_helper_shutdown for module unload. And developers really > want their devices to be shut off on driver unload. So yeah > unfortunately we currently can decide between "correct for hotunplug" > and "convenient for driver unload for driver authors". I'm not sure > what to best do here, since all options are kinda not great for one > use-case or the other. So if we'd split up drm_dev_unplug into drm_dev_unregister + drm_dev_mark_unplugged or whatever the options would be: drm_atomic_helper_shutdown(); /* and other hw shut down */ drm_dev_unregister(); drm_dev_mark_unplugged(); Kinda annoying since userspace might race with us, so we might still have an active fb (in sw tracking at least) that we need to clean up again later on. Plus shutting down hw before we unregister is going to make the hotunplug confusion for userspace even more a mess. Next option: drm_dev_unregster(); /* shut down hw */ drm_dev_mark_unplugged(); This just wastes time since if we're really unplugged we'll do lots of io attempts that go nowhere because the device is gone already. They'll all time out (if the bus subsystem/hw for our driver works correctly at least). Plus userspace can still sneak in and do stupid stuff I think while we're not looking. Next up: drm_dev_unregister(); drm_dev_mark_unplugged(); drm_atomic_helper_shutdown(); This is a bit silly since all the shutdown code now does is shut down sw state, and never touches hw (if the driver is fully annotated with drm_dev_enter/exit). One option might be that we slap a lot more drm_dev_enter/exit around the top-level ioctls (to at least stop the userspace races with driver unload), and allow drivers to still shut down stuff internally. tldr; it's all still a bit a mess. -Daniel > -Daniel > > > Best regards > > Thomas > > > > > kfree(ast); > > > } > > > > > > > -- > > Thomas Zimmermann > > Graphics Driver Developer > > SUSE Software Solutions Germany GmbH > > Maxfeldstr. 5, 90409 Nürnberg, Germany > > (HRB 36809, AG Nürnberg) > > Geschäftsführer: Felix Imendörffer > > > > > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-15 8:17 UTC|newest] Thread overview: 317+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-15 7:39 [PATCH 00/59] devm_drm_dev_alloc, v2 Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 01/59] drm: Add devm_drm_dev_alloc macro Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-20 13:36 ` Thomas Zimmermann 2020-04-20 13:36 ` [Intel-gfx] " Thomas Zimmermann 2020-04-21 10:45 ` Daniel Vetter 2020-04-21 10:45 ` [Intel-gfx] " Daniel Vetter 2020-04-21 14:03 ` Thomas Zimmermann 2020-04-21 14:03 ` [Intel-gfx] " Thomas Zimmermann 2020-04-21 20:32 ` Sam Ravnborg 2020-04-21 20:32 ` [Intel-gfx] " Sam Ravnborg 2020-04-28 13:06 ` Daniel Vetter 2020-04-28 13:06 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 02/59] drm/vboxvideo: drop DRM_MTRR_WC #define Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:01 ` Hans de Goede 2020-04-15 15:01 ` [Intel-gfx] " Hans de Goede 2020-04-15 7:39 ` [PATCH 03/59] drm/vboxvideo: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:02 ` Hans de Goede 2020-04-15 15:02 ` [Intel-gfx] " Hans de Goede 2020-04-24 16:33 ` Sam Ravnborg 2020-04-24 16:33 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:39 ` [PATCH 04/59] drm/vboxvideo: Stop using drm_device->dev_private Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:02 ` Hans de Goede 2020-04-15 15:02 ` [Intel-gfx] " Hans de Goede 2020-04-15 7:39 ` [PATCH 05/59] drm/vboxvidoe: use managed pci functions Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:03 ` Hans de Goede 2020-04-15 15:03 ` [Intel-gfx] " Hans de Goede 2020-04-15 17:44 ` Daniel Vetter 2020-04-15 17:44 ` [Intel-gfx] " Daniel Vetter 2020-04-20 13:16 ` Hans de Goede 2020-04-20 13:16 ` [Intel-gfx] " Hans de Goede 2020-04-15 17:32 ` Thomas Zimmermann 2020-04-15 17:32 ` [Intel-gfx] " Thomas Zimmermann 2020-04-15 7:39 ` [PATCH 06/59] drm/vboxvideo: Use devm_gen_pool_create Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:04 ` Hans de Goede 2020-04-15 15:04 ` [Intel-gfx] " Hans de Goede 2020-04-15 7:39 ` [PATCH 07/59] drm/v3d: Don't set drm_device->dev_private Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 08/59] drm/v3d: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 09/59] drm/v3d: Delete v3d_dev->dev Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 10/59] drm/v3d: Delete v3d_dev->pdev Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 11/59] drm/udl: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:55 ` Thomas Zimmermann 2020-04-15 7:55 ` [Intel-gfx] " Thomas Zimmermann 2020-04-24 14:55 ` Sam Ravnborg 2020-04-24 14:55 ` [Intel-gfx] " Sam Ravnborg 2020-04-28 13:18 ` Daniel Vetter 2020-04-28 13:18 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 12/59] drm/udl: don't set drm_device->dev_private Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 13/59] drm/st7735r: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 14/59] drm/st7586: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 15/59] drm/repaper: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 16/59] drm/mi0283qt: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 17/59] drm/ili9486: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 18/59] drm/ili9341: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 19/59] drm/ili9225: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 20/59] drm/hx8357d: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:39 ` [PATCH 21/59] drm/gm12u320: " Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:04 ` Hans de Goede 2020-04-15 15:04 ` [Intel-gfx] " Hans de Goede 2020-04-15 7:39 ` [PATCH 22/59] drm/gm12u320: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-15 15:05 ` Hans de Goede 2020-04-15 15:05 ` [Intel-gfx] " Hans de Goede 2020-04-15 7:39 ` [PATCH 23/59] drm/tidss: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-21 11:03 ` Tomi Valkeinen 2020-04-21 11:03 ` [Intel-gfx] " Tomi Valkeinen 2020-04-15 7:39 ` [PATCH 24/59] drm/tidss: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:39 ` [Intel-gfx] " Daniel Vetter 2020-04-21 11:05 ` Tomi Valkeinen 2020-04-21 11:05 ` [Intel-gfx] " Tomi Valkeinen 2020-04-15 7:40 ` [PATCH 25/59] drm/tidss: Delete tidss->saved_state Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-21 11:05 ` Tomi Valkeinen 2020-04-21 11:05 ` [Intel-gfx] " Tomi Valkeinen 2020-04-15 7:40 ` [PATCH 26/59] drm/qxl: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-24 15:09 ` Sam Ravnborg 2020-04-24 15:09 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 15:09 ` Sam Ravnborg 2020-04-28 14:00 ` Daniel Vetter 2020-04-28 14:00 ` [Intel-gfx] " Daniel Vetter 2020-04-28 14:00 ` Daniel Vetter 2020-04-28 17:00 ` Sam Ravnborg 2020-04-28 17:00 ` [Intel-gfx] " Sam Ravnborg 2020-04-28 17:00 ` Sam Ravnborg 2020-04-28 18:04 ` Daniel Vetter 2020-04-28 18:04 ` [Intel-gfx] " Daniel Vetter 2020-04-28 18:04 ` Daniel Vetter 2020-04-15 7:40 ` [PATCH 27/59] drm/qxl: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-24 15:12 ` Sam Ravnborg 2020-04-24 15:12 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 15:12 ` Sam Ravnborg 2020-04-15 7:40 ` [PATCH 28/59] drm/mcde: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 12:20 ` Linus Walleij 2020-04-15 12:20 ` [Intel-gfx] " Linus Walleij 2020-04-15 7:40 ` [PATCH 29/59] drm/mcde: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 30/59] drm/ingenic: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 31/59] drm/ingenic: Don't set drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 32/59] drm/komeda: use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 33/59] drm/armada: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 34/59] drm/armada: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 35/59] drm/cirrus: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-15 7:40 ` [PATCH 36/59] drm/cirrus: Don't use drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-15 7:40 ` [PATCH 37/59] drm/cirrus: Move to drm/tiny Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-15 8:01 ` Thomas Zimmermann 2020-04-15 8:01 ` [Intel-gfx] " Thomas Zimmermann 2020-04-15 8:01 ` Thomas Zimmermann 2020-04-15 8:19 ` Daniel Vetter 2020-04-15 8:19 ` [Intel-gfx] " Daniel Vetter 2020-04-15 8:19 ` Daniel Vetter 2020-04-15 8:46 ` Thomas Zimmermann 2020-04-15 8:46 ` [Intel-gfx] " Thomas Zimmermann 2020-04-15 8:46 ` Thomas Zimmermann 2020-04-15 9:31 ` Daniel Vetter 2020-04-15 9:31 ` [Intel-gfx] " Daniel Vetter 2020-04-15 9:31 ` Daniel Vetter 2020-04-21 7:37 ` Gerd Hoffmann 2020-04-21 7:37 ` [Intel-gfx] " Gerd Hoffmann 2020-04-21 7:37 ` Gerd Hoffmann 2020-04-24 16:37 ` Sam Ravnborg 2020-04-24 16:37 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 16:37 ` Sam Ravnborg 2020-04-15 7:40 ` [PATCH 38/59] drm/i915: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-28 18:52 ` Daniel Vetter 2020-04-28 18:52 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 39/59] drm/arcpgu: Switch to devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 16:43 ` Sam Ravnborg 2020-04-24 16:43 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 40/59] drm/arcpgu: Stop using drm_device->dev_private Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 16:46 ` Sam Ravnborg 2020-04-24 16:46 ` [Intel-gfx] " Sam Ravnborg 2020-09-04 13:42 ` Daniel Vetter 2020-09-04 13:42 ` [Intel-gfx] " Daniel Vetter 2020-09-04 14:42 ` Sam Ravnborg 2020-09-04 14:42 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 41/59] drm/arcpgu: Delete arcpgu_priv->fb Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 16:47 ` Sam Ravnborg 2020-04-24 16:47 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 42/59] drm/arc: Embedded a drm_simple_display_pipe Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:34 ` Sam Ravnborg 2020-04-24 17:34 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 43/59] drm/arc: Embedd a drm_connector for sim case Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:34 ` Sam Ravnborg 2020-04-24 17:34 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 44/59] drm/arc: Drop surplus connector registration Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 16:51 ` Sam Ravnborg 2020-04-24 16:51 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 45/59] drm/arc: Use drmm_mode_config_cleanup Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:36 ` Sam Ravnborg 2020-04-24 17:36 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 46/59] drm/arc: Align with simple pipe helpers Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-25 12:24 ` Sam Ravnborg 2020-04-25 12:24 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 47/59] drm/arc: Convert to drm_simple_kms_pipe_helper Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:40 ` Sam Ravnborg 2020-04-24 17:40 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 48/59] drm/arc: Drop fb/crtc check in arc_pgu_update Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:45 ` Sam Ravnborg 2020-04-24 17:45 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 49/59] drm/arc: Inline arcpgu_crtc.c Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:51 ` Sam Ravnborg 2020-04-24 17:51 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 50/59] drm/arc: Inline arcpgu_drm_hdmi_init Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:54 ` Sam Ravnborg 2020-04-24 17:54 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 51/59] drm/arc: Inline remaining files Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:56 ` Sam Ravnborg 2020-04-24 17:56 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 52/59] drm/arc: Initialize sim connector before display pipe Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-24 17:58 ` Sam Ravnborg 2020-04-24 17:58 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 53/59] drm/arc: Move to drm/tiny Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 8:04 ` Thomas Zimmermann 2020-04-15 8:04 ` [Intel-gfx] " Thomas Zimmermann 2020-04-15 8:22 ` Daniel Vetter 2020-04-15 8:22 ` [Intel-gfx] " Daniel Vetter 2020-04-15 9:45 ` Sam Ravnborg 2020-04-15 9:45 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 12:02 ` Alexey Brodkin 2020-04-15 12:02 ` [Intel-gfx] " Alexey Brodkin 2020-04-15 12:20 ` Daniel Vetter 2020-04-15 12:20 ` [Intel-gfx] " Daniel Vetter 2020-04-28 14:08 ` Daniel Vetter 2020-04-28 14:08 ` [Intel-gfx] " Daniel Vetter 2020-05-08 13:56 ` Alexey Brodkin 2020-05-08 13:56 ` [Intel-gfx] " Alexey Brodkin 2020-05-08 18:07 ` Daniel Vetter 2020-05-08 18:07 ` [Intel-gfx] " Daniel Vetter 2020-06-04 8:05 ` Daniel Vetter 2020-06-04 8:05 ` [Intel-gfx] " Daniel Vetter 2020-06-04 10:38 ` Eugeniy Paltsev 2020-06-04 10:38 ` [Intel-gfx] " Eugeniy Paltsev 2020-06-04 11:19 ` Daniel Vetter 2020-06-04 11:19 ` [Intel-gfx] " Daniel Vetter 2020-06-04 19:00 ` Eugeniy Paltsev 2020-06-04 19:00 ` [Intel-gfx] " Eugeniy Paltsev 2020-06-05 19:55 ` Daniel Vetter 2020-06-05 19:55 ` [Intel-gfx] " Daniel Vetter 2020-06-09 12:08 ` Eugeniy Paltsev 2020-06-09 12:08 ` [Intel-gfx] " Eugeniy Paltsev 2020-06-09 13:02 ` Daniel Vetter 2020-06-09 13:02 ` [Intel-gfx] " Daniel Vetter 2020-07-17 9:04 ` Daniel Vetter 2020-07-17 9:04 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 54/59] drm/aspeed: Drop aspeed_gfx->fbdev Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-24 18:00 ` Sam Ravnborg 2020-04-24 18:00 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 18:00 ` Sam Ravnborg 2020-04-15 7:40 ` [PATCH 55/59] drm/aspeed: Use devm_drm_dev_alloc Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-24 18:02 ` Sam Ravnborg 2020-04-24 18:02 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 18:02 ` Sam Ravnborg 2020-04-15 7:40 ` [PATCH 56/59] drm/aspeed: Use managed drmm_mode_config_cleanup Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-24 18:10 ` Sam Ravnborg 2020-04-24 18:10 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 18:10 ` Sam Ravnborg 2020-04-28 14:12 ` Daniel Vetter 2020-04-28 14:12 ` [Intel-gfx] " Daniel Vetter 2020-04-28 14:12 ` Daniel Vetter 2020-04-28 17:03 ` Sam Ravnborg 2020-04-28 17:03 ` [Intel-gfx] " Sam Ravnborg 2020-04-28 17:03 ` Sam Ravnborg 2020-04-15 7:40 ` [PATCH 57/59] drm/ast: Use managed pci functions Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:52 ` Thomas Zimmermann 2020-04-15 7:52 ` [Intel-gfx] " Thomas Zimmermann 2020-04-15 8:09 ` Daniel Vetter 2020-04-15 8:09 ` [Intel-gfx] " Daniel Vetter 2020-04-15 8:17 ` Daniel Vetter [this message] 2020-04-15 8:17 ` Daniel Vetter 2020-04-15 12:23 ` Daniel Vetter 2020-04-15 12:23 ` [Intel-gfx] " Daniel Vetter 2020-06-11 12:04 ` Thomas Zimmermann 2020-06-11 12:04 ` [Intel-gfx] " Thomas Zimmermann 2020-06-16 11:55 ` Daniel Vetter 2020-06-16 11:55 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` [PATCH 58/59] drm/ast: Drop explicit connector register/unregister Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:53 ` Thomas Zimmermann 2020-04-15 7:53 ` [Intel-gfx] " Thomas Zimmermann 2020-04-24 18:11 ` Sam Ravnborg 2020-04-24 18:11 ` [Intel-gfx] " Sam Ravnborg 2020-04-15 7:40 ` [PATCH 59/59] drm/bochs: Remove explicit drm_connector_register Daniel Vetter 2020-04-15 7:40 ` [Intel-gfx] " Daniel Vetter 2020-04-15 7:40 ` Daniel Vetter 2020-04-21 7:39 ` Gerd Hoffmann 2020-04-21 7:39 ` [Intel-gfx] " Gerd Hoffmann 2020-04-21 7:39 ` Gerd Hoffmann 2020-04-24 18:11 ` Sam Ravnborg 2020-04-24 18:11 ` [Intel-gfx] " Sam Ravnborg 2020-04-24 18:11 ` Sam Ravnborg 2020-04-15 8:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for devm_drm_dev_alloc, v2 Patchwork 2020-04-15 8:23 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork 2020-04-15 8:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2020-04-15 23:45 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2020-06-04 11:58 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for devm_drm_dev_alloc, v2 (rev2) Patchwork 2020-06-04 19:36 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for devm_drm_dev_alloc, v2 (rev3) Patchwork
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=CAKMK7uEiA0SxSWBWkyfTJpo0BBr9aekzc6fa3P-HQqEjmuB8TQ@mail.gmail.com \ --to=daniel.vetter@ffwll.ch \ --cc=airlied@redhat.com \ --cc=christian.koenig@amd.com \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=emil.velikov@collabora.com \ --cc=intel-gfx@lists.freedesktop.org \ --cc=kraxel@redhat.com \ --cc=sam@ravnborg.org \ --cc=tzimmermann@suse.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.