* [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times
@ 2023-09-01 23:39 Douglas Anderson
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
2023-09-13 18:31 ` [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Doug Anderson
0 siblings, 2 replies; 10+ messages in thread
From: Douglas Anderson @ 2023-09-01 23:39 UTC (permalink / raw)
To: dri-devel, Maxime Ripard
Cc: Douglas Anderson, airlied, airlied, alain.volmat,
alexander.deucher, alexandre.belloni, alexandre.torgue,
alison.wang, andrew, bbrezillon, christian.koenig, claudiu.beznea,
daniel, drawat.floss, emma, hdegoede, javierm, jernej.skrabec,
jfalempe, joel, jstultz, jyri.sarha, kong.kongxinwei, kraxel,
linus.walleij, linux-arm-kernel, linux-aspeed, linux-hyperv,
linux-kernel, linux-stm32, linux-sunxi, liviu.dudau,
maarten.lankhorst, mcoquelin.stm32, nicolas.ferre,
paul.kocialkowski, philippe.cornu, raphael.gallais-pou, robh, sam,
samuel, spice-devel, stefan, steven.price, suijingfeng,
sumit.semwal, tiantao6, tomi.valkeinen, tzimmermann,
u.kleine-koenig, virtualization, wens, xinliang.liu,
yannick.fertre, yongqin.liu, zackr
NOTE: in order to avoid email sending limits on the cover letter, I've
split this patch series in two. Patches that target drm-misc and ones
that don't. The cover letter of the two is identical other than this note.
This patch series came about after a _long_ discussion between me and
Maxime Ripard in response to a different patch I sent out [1]. As part
of that discussion, we realized that it would be good if DRM drivers
consistently called drm_atomic_helper_shutdown() properly at shutdown
and driver remove time as it's documented that they should do. The
eventual goal of this would be to enable removing some hacky code from
panel drivers where they had to hook into shutdown themselves because
the DRM driver wasn't calling them.
It turns out that quite a lot of drivers seemed to be missing
drm_atomic_helper_shutdown() in one or both places that it was
supposed to be. This patch series attempts to fix all the drivers that
I was able to identify.
NOTE: fixing this wasn't exactly cookie cutter. Each driver has its
own unique way of setting itself up and tearing itself down. Some
drivers also use the component model, which adds extra fun. I've made
my best guess at solving this and I've run a bunch of compile tests
(specifically, allmodconfig for amd64, arm64, and powerpc). That being
said, these code changes are not totally trivial and I've done zero
real testing on them. Making these patches was also a little mind
numbing and I'm certain my eyes glazed over at several points when
writing them. What I'm trying to say is to please double-check that I
didn't do anything too silly, like cast your driver's drvdata to the
wrong type. Even better, test these patches!
I've organized this series like this:
1. One patch for all simple cases of just needing a call at shutdown
time for drivers that go through drm-misc.
2. A separate patch for "drm/vc4", even though it goes through
drm-misc, since I wanted to leave an extra note for that one.
3. Patches for drivers that just needed a call at shutdown time for
drivers that _don't_ go through drm-misc.
4. Patches for the few drivers that had the call at shutdown time but
lacked it at remove time.
5. One patch for all simple cases of needing a call at shutdown and
remove (or unbind) time for drivers that go through drm-misc.
6. A separate patch for "drm/hisilicon/kirin", even though it goes
through drm-misc, since I wanted to leave an extra note for that
one.
7. Patches for drivers that needed a call at shutdown and remove (or
unbind) time for drivers that _don't_ go through drm-misc.
I've labeled this patch series as RFT (request for testing) to help
call attention to the fact that I didn't personally test any of these
patches.
If you're a maintainer of one of these drivers and you think that the
patch for your driver looks fabulous, you've tested it, and you'd like
to land it right away then please do. For non-drm-misc drivers there
are no dependencies here. Some of the drm-misc drivers depend on the
first patch, AKA ("drm/atomic-helper: drm_atomic_helper_shutdown(NULL)
should be a noop"). I've tried to call this out but it also should be
obvious once you know to look for it.
I'd like to call out a few drivers that I _didn't_ fix in this series
and why. If any of these drivers should be fixed then please yell.
- DRM driers backed by usb_driver (like gud, gm12u320, udl): I didn't
add the call to drm_atomic_helper_shutdown() at shutdown time
because there's no ".shutdown" callback for them USB drivers. Given
that USB is hotpluggable, I'm assuming that they are robust against
this and the special shutdown callback isn't needed.
- ofdrm and simpledrm: These didn't have drm_atomic_helper_shutdown()
in either shutdown or remove, but I didn't add it. I think that's OK
since they're sorta special and not really directly controlling
hardware power sequencing.
- virtio, vkms, vmwgfx, xen: I believe these are all virtual (thus
they wouldn't directly drive a panel) and adding the shutdown
didn't look straightforward, so I skipped them.
I've let each patch in the series get CCed straight from
get_maintainer. That means not everyone will have received every patch
but everyone should be on the cover letter. I know some people dislike
this but when touching this many drivers there's not much
choice. dri-devel and lkml have been CCed and lore/lei exist, so
hopefully that's enough for folks. I'm happy to add people to the
whole series for future posts.
[1] https://lore.kernel.org/lkml/20230804140605.RFC.4.I930069a32baab6faf46d6b234f89613b5cec0f14@changeid
Douglas Anderson (6):
drm/atomic-helper: drm_atomic_helper_shutdown(NULL) should be a noop
drm: Call drm_atomic_helper_shutdown() at shutdown time for misc
drivers
drm/vc4: Call drm_atomic_helper_shutdown() at shutdown time
drm/ssd130x: Call drm_atomic_helper_shutdown() at remove time
drm: Call drm_atomic_helper_shutdown() at shutdown/remove time for
misc drivers
drm/hisilicon/kirin: Call drm_atomic_helper_shutdown() at
shutdown/unbind time
.../gpu/drm/arm/display/komeda/komeda_drv.c | 9 +++++
.../gpu/drm/arm/display/komeda/komeda_kms.c | 7 ++++
.../gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
drivers/gpu/drm/arm/hdlcd_drv.c | 6 ++++
drivers/gpu/drm/arm/malidp_drv.c | 6 ++++
drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 7 ++++
drivers/gpu/drm/ast/ast_drv.c | 6 ++++
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 6 ++++
drivers/gpu/drm/drm_atomic_helper.c | 3 ++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 +++++
.../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++++
.../gpu/drm/hisilicon/kirin/kirin_drm_drv.c | 9 +++++
drivers/gpu/drm/hyperv/hyperv_drm_drv.c | 6 ++++
drivers/gpu/drm/logicvc/logicvc_drm.c | 9 +++++
drivers/gpu/drm/loongson/lsdc_drv.c | 6 ++++
drivers/gpu/drm/mcde/mcde_drv.c | 9 +++++
drivers/gpu/drm/mgag200/mgag200_drv.c | 8 +++++
drivers/gpu/drm/omapdrm/omap_drv.c | 8 +++++
drivers/gpu/drm/pl111/pl111_drv.c | 7 ++++
drivers/gpu/drm/qxl/qxl_drv.c | 7 ++++
drivers/gpu/drm/solomon/ssd130x.c | 1 +
drivers/gpu/drm/sti/sti_drv.c | 7 ++++
drivers/gpu/drm/stm/drv.c | 7 ++++
drivers/gpu/drm/sun4i/sun4i_drv.c | 6 ++++
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 11 +++++-
drivers/gpu/drm/tiny/bochs.c | 6 ++++
drivers/gpu/drm/tiny/cirrus.c | 6 ++++
drivers/gpu/drm/tve200/tve200_drv.c | 7 ++++
drivers/gpu/drm/vboxvideo/vbox_drv.c | 10 ++++++
drivers/gpu/drm/vc4/vc4_drv.c | 36 ++++++++++++-------
30 files changed, 217 insertions(+), 14 deletions(-)
--
2.42.0.283.g2d96d420d3-goog
^ permalink raw reply [flat|nested] 10+ messages in thread
* [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Douglas Anderson
@ 2023-09-01 23:39 ` Douglas Anderson
2023-09-04 7:58 ` Maxime Ripard
` (4 more replies)
2023-09-13 18:31 ` [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Doug Anderson
1 sibling, 5 replies; 10+ messages in thread
From: Douglas Anderson @ 2023-09-01 23:39 UTC (permalink / raw)
To: dri-devel, Maxime Ripard
Cc: Douglas Anderson, airlied, airlied, alain.volmat,
alexander.deucher, alexandre.belloni, alison.wang, bbrezillon,
christian.koenig, claudiu.beznea, daniel, drawat.floss, javierm,
jernej.skrabec, jfalempe, jstultz, kong.kongxinwei, kraxel,
linus.walleij, linux-arm-kernel, linux-hyperv, linux-kernel,
linux-sunxi, liviu.dudau, nicolas.ferre, paul.kocialkowski, sam,
samuel, spice-devel, stefan, suijingfeng, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr
Based on grepping through the source code these drivers appear to be
missing a call to drm_atomic_helper_shutdown() at system shutdown
time. Among other things, this means that if a panel is in use that it
won't be cleanly powered off at system shutdown time.
The fact that we should call drm_atomic_helper_shutdown() in the case
of OS shutdown/restart comes straight out of the kernel doc "driver
instance overview" in drm_drv.c.
All of the drivers in this patch were fairly straightforward to fix
since they already had a call to drm_atomic_helper_shutdown() at
remove/unbind time but were just lacking one at system shutdown. The
only hitch is that some of these drivers use the component model to
register/unregister their DRM devices. The shutdown callback is part
of the original device. The typical solution here, based on how other
DRM drivers do this, is to keep track of whether the device is bound
based on drvdata. In most cases the drvdata is the drm_device, so we
can just make sure it is NULL when the device is not bound. In some
drivers, this required minor code changes. To make things simpler,
drm_atomic_helper_shutdown() has been modified to consider a NULL
drm_device as a noop in the patch ("drm/atomic-helper:
drm_atomic_helper_shutdown(NULL) should be a noop").
Suggested-by: Maxime Ripard <mripard@kernel.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
This commit is only compile-time tested.
Note that checkpatch yells that "drivers/gpu/drm/tiny/cirrus.c" is
marked as 'obsolete', but it seems silly not to include the fix if
it's already been written. If someone wants me to take that out,
though, I can.
drivers/gpu/drm/arm/display/komeda/komeda_drv.c | 9 +++++++++
drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 7 +++++++
drivers/gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
drivers/gpu/drm/arm/hdlcd_drv.c | 6 ++++++
drivers/gpu/drm/arm/malidp_drv.c | 6 ++++++
drivers/gpu/drm/ast/ast_drv.c | 6 ++++++
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 6 ++++++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 ++++++++
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++++++
drivers/gpu/drm/hyperv/hyperv_drm_drv.c | 6 ++++++
drivers/gpu/drm/logicvc/logicvc_drm.c | 9 +++++++++
drivers/gpu/drm/loongson/lsdc_drv.c | 6 ++++++
drivers/gpu/drm/mcde/mcde_drv.c | 9 +++++++++
drivers/gpu/drm/omapdrm/omap_drv.c | 8 ++++++++
drivers/gpu/drm/qxl/qxl_drv.c | 7 +++++++
drivers/gpu/drm/sti/sti_drv.c | 7 +++++++
drivers/gpu/drm/sun4i/sun4i_drv.c | 6 ++++++
drivers/gpu/drm/tiny/bochs.c | 6 ++++++
drivers/gpu/drm/tiny/cirrus.c | 6 ++++++
19 files changed, 125 insertions(+)
diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_drv.c b/drivers/gpu/drm/arm/display/komeda/komeda_drv.c
index cb2a2be24c5f..cc57ea4e13ae 100644
--- a/drivers/gpu/drm/arm/display/komeda/komeda_drv.c
+++ b/drivers/gpu/drm/arm/display/komeda/komeda_drv.c
@@ -45,6 +45,14 @@ static void komeda_platform_remove(struct platform_device *pdev)
devm_kfree(dev, mdrv);
}
+static void komeda_platform_shutdown(struct platform_device *pdev)
+{
+ struct device *dev = &pdev->dev;
+ struct komeda_drv *mdrv = dev_get_drvdata(dev);
+
+ komeda_kms_shutdown(mdrv->kms);
+}
+
static int komeda_platform_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
@@ -142,6 +150,7 @@ static const struct dev_pm_ops komeda_pm_ops = {
static struct platform_driver komeda_platform_driver = {
.probe = komeda_platform_probe,
.remove_new = komeda_platform_remove,
+ .shutdown = komeda_platform_shutdown,
.driver = {
.name = "komeda",
.of_match_table = komeda_of_match,
diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
index 9299026701f3..fe46b0ebefea 100644
--- a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
+++ b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
@@ -340,3 +340,10 @@ void komeda_kms_detach(struct komeda_kms_dev *kms)
komeda_kms_cleanup_private_objs(kms);
drm->dev_private = NULL;
}
+
+void komeda_kms_shutdown(struct komeda_kms_dev *kms)
+{
+ struct drm_device *drm = &kms->base;
+
+ drm_atomic_helper_shutdown(drm);
+}
diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_kms.h b/drivers/gpu/drm/arm/display/komeda/komeda_kms.h
index 6ef655326357..a4048724564d 100644
--- a/drivers/gpu/drm/arm/display/komeda/komeda_kms.h
+++ b/drivers/gpu/drm/arm/display/komeda/komeda_kms.h
@@ -190,5 +190,6 @@ void komeda_crtc_flush_and_wait_for_flip_done(struct komeda_crtc *kcrtc,
struct komeda_kms_dev *komeda_kms_attach(struct komeda_dev *mdev);
void komeda_kms_detach(struct komeda_kms_dev *kms);
+void komeda_kms_shutdown(struct komeda_kms_dev *kms);
#endif /*_KOMEDA_KMS_H_*/
diff --git a/drivers/gpu/drm/arm/hdlcd_drv.c b/drivers/gpu/drm/arm/hdlcd_drv.c
index aa06f9838015..32be9e370049 100644
--- a/drivers/gpu/drm/arm/hdlcd_drv.c
+++ b/drivers/gpu/drm/arm/hdlcd_drv.c
@@ -372,6 +372,11 @@ static void hdlcd_remove(struct platform_device *pdev)
component_master_del(&pdev->dev, &hdlcd_master_ops);
}
+static void hdlcd_shutdown(struct platform_device *pdev)
+{
+ drm_atomic_helper_shutdown(platform_get_drvdata(pdev));
+}
+
static const struct of_device_id hdlcd_of_match[] = {
{ .compatible = "arm,hdlcd" },
{},
@@ -399,6 +404,7 @@ static SIMPLE_DEV_PM_OPS(hdlcd_pm_ops, hdlcd_pm_suspend, hdlcd_pm_resume);
static struct platform_driver hdlcd_platform_driver = {
.probe = hdlcd_probe,
.remove_new = hdlcd_remove,
+ .shutdown = hdlcd_shutdown,
.driver = {
.name = "hdlcd",
.pm = &hdlcd_pm_ops,
diff --git a/drivers/gpu/drm/arm/malidp_drv.c b/drivers/gpu/drm/arm/malidp_drv.c
index 62329d5dd992..6682131d2910 100644
--- a/drivers/gpu/drm/arm/malidp_drv.c
+++ b/drivers/gpu/drm/arm/malidp_drv.c
@@ -941,6 +941,11 @@ static void malidp_platform_remove(struct platform_device *pdev)
component_master_del(&pdev->dev, &malidp_master_ops);
}
+static void malidp_platform_shutdown(struct platform_device *pdev)
+{
+ drm_atomic_helper_shutdown(platform_get_drvdata(pdev));
+}
+
static int __maybe_unused malidp_pm_suspend(struct device *dev)
{
struct drm_device *drm = dev_get_drvdata(dev);
@@ -982,6 +987,7 @@ static const struct dev_pm_ops malidp_pm_ops = {
static struct platform_driver malidp_platform_driver = {
.probe = malidp_platform_probe,
.remove_new = malidp_platform_remove,
+ .shutdown = malidp_platform_shutdown,
.driver = {
.name = "mali-dp",
.pm = &malidp_pm_ops,
diff --git a/drivers/gpu/drm/ast/ast_drv.c b/drivers/gpu/drm/ast/ast_drv.c
index e1224ef4ad83..cf5b754f044c 100644
--- a/drivers/gpu/drm/ast/ast_drv.c
+++ b/drivers/gpu/drm/ast/ast_drv.c
@@ -125,6 +125,11 @@ static void ast_pci_remove(struct pci_dev *pdev)
drm_atomic_helper_shutdown(dev);
}
+static void ast_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
static int ast_drm_freeze(struct drm_device *dev)
{
int error;
@@ -209,6 +214,7 @@ static struct pci_driver ast_pci_driver = {
.id_table = ast_pciidlist,
.probe = ast_pci_probe,
.remove = ast_pci_remove,
+ .shutdown = ast_pci_shutdown,
.driver.pm = &ast_pm_ops,
};
diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c
index fa0f9a93d50d..84c54e8622d1 100644
--- a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c
+++ b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c
@@ -782,6 +782,11 @@ static void atmel_hlcdc_dc_drm_remove(struct platform_device *pdev)
drm_dev_put(ddev);
}
+static void atmel_hlcdc_dc_drm_shutdown(struct platform_device *pdev)
+{
+ drm_atomic_helper_shutdown(platform_get_drvdata(pdev));
+}
+
static int atmel_hlcdc_dc_drm_suspend(struct device *dev)
{
struct drm_device *drm_dev = dev_get_drvdata(dev);
@@ -825,6 +830,7 @@ static const struct of_device_id atmel_hlcdc_dc_of_match[] = {
static struct platform_driver atmel_hlcdc_dc_platform_driver = {
.probe = atmel_hlcdc_dc_drm_probe,
.remove_new = atmel_hlcdc_dc_drm_remove,
+ .shutdown = atmel_hlcdc_dc_drm_shutdown,
.driver = {
.name = "atmel-hlcdc-display-controller",
.pm = pm_sleep_ptr(&atmel_hlcdc_dc_drm_pm_ops),
diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c
index a395f93449f3..ab6c0c6cd0e2 100644
--- a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c
+++ b/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c
@@ -356,9 +356,17 @@ static void fsl_dcu_drm_remove(struct platform_device *pdev)
clk_unregister(fsl_dev->pix_clk);
}
+static void fsl_dcu_drm_shutdown(struct platform_device *pdev)
+{
+ struct fsl_dcu_drm_device *fsl_dev = platform_get_drvdata(pdev);
+
+ drm_atomic_helper_shutdown(fsl_dev->drm);
+}
+
static struct platform_driver fsl_dcu_drm_platform_driver = {
.probe = fsl_dcu_drm_probe,
.remove_new = fsl_dcu_drm_remove,
+ .shutdown = fsl_dcu_drm_shutdown,
.driver = {
.name = "fsl-dcu",
.pm = &fsl_dcu_drm_pm_ops,
diff --git a/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c b/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c
index 8a98fa276e8a..57c21ec452b7 100644
--- a/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c
+++ b/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c
@@ -357,6 +357,11 @@ static void hibmc_pci_remove(struct pci_dev *pdev)
hibmc_unload(dev);
}
+static void hibmc_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
static const struct pci_device_id hibmc_pci_table[] = {
{ PCI_VDEVICE(HUAWEI, 0x1711) },
{0,}
@@ -367,6 +372,7 @@ static struct pci_driver hibmc_pci_driver = {
.id_table = hibmc_pci_table,
.probe = hibmc_pci_probe,
.remove = hibmc_pci_remove,
+ .shutdown = hibmc_pci_shutdown,
.driver.pm = &hibmc_pm_ops,
};
diff --git a/drivers/gpu/drm/hyperv/hyperv_drm_drv.c b/drivers/gpu/drm/hyperv/hyperv_drm_drv.c
index 8026118c6e03..58b0b46a21e6 100644
--- a/drivers/gpu/drm/hyperv/hyperv_drm_drv.c
+++ b/drivers/gpu/drm/hyperv/hyperv_drm_drv.c
@@ -178,6 +178,11 @@ static void hyperv_vmbus_remove(struct hv_device *hdev)
vmbus_free_mmio(hv->mem->start, hv->fb_size);
}
+static void hyperv_vmbus_shutdown(struct hv_device *hdev)
+{
+ drm_atomic_helper_shutdown(hv_get_drvdata(hdev));
+}
+
static int hyperv_vmbus_suspend(struct hv_device *hdev)
{
struct drm_device *dev = hv_get_drvdata(hdev);
@@ -220,6 +225,7 @@ static struct hv_driver hyperv_hv_driver = {
.id_table = hyperv_vmbus_tbl,
.probe = hyperv_vmbus_probe,
.remove = hyperv_vmbus_remove,
+ .shutdown = hyperv_vmbus_shutdown,
.suspend = hyperv_vmbus_suspend,
.resume = hyperv_vmbus_resume,
.driver = {
diff --git a/drivers/gpu/drm/logicvc/logicvc_drm.c b/drivers/gpu/drm/logicvc/logicvc_drm.c
index 749debd3d6a5..01a37e28c080 100644
--- a/drivers/gpu/drm/logicvc/logicvc_drm.c
+++ b/drivers/gpu/drm/logicvc/logicvc_drm.c
@@ -482,6 +482,14 @@ static void logicvc_drm_remove(struct platform_device *pdev)
of_reserved_mem_device_release(dev);
}
+static void logicvc_drm_shutdown(struct platform_device *pdev)
+{
+ struct logicvc_drm *logicvc = platform_get_drvdata(pdev);
+ struct drm_device *drm_dev = &logicvc->drm_dev;
+
+ drm_atomic_helper_shutdown(drm_dev);
+}
+
static const struct of_device_id logicvc_drm_of_table[] = {
{ .compatible = "xylon,logicvc-3.02.a-display" },
{ .compatible = "xylon,logicvc-4.01.a-display" },
@@ -492,6 +500,7 @@ MODULE_DEVICE_TABLE(of, logicvc_drm_of_table);
static struct platform_driver logicvc_drm_platform_driver = {
.probe = logicvc_drm_probe,
.remove_new = logicvc_drm_remove,
+ .shutdown = logicvc_drm_shutdown,
.driver = {
.name = "logicvc-drm",
.of_match_table = logicvc_drm_of_table,
diff --git a/drivers/gpu/drm/loongson/lsdc_drv.c b/drivers/gpu/drm/loongson/lsdc_drv.c
index 188ec82afcfb..89ccc0c43169 100644
--- a/drivers/gpu/drm/loongson/lsdc_drv.c
+++ b/drivers/gpu/drm/loongson/lsdc_drv.c
@@ -327,6 +327,11 @@ static void lsdc_pci_remove(struct pci_dev *pdev)
drm_atomic_helper_shutdown(ddev);
}
+static void lsdc_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
static int lsdc_drm_freeze(struct drm_device *ddev)
{
struct lsdc_device *ldev = to_lsdc(ddev);
@@ -447,6 +452,7 @@ struct pci_driver lsdc_pci_driver = {
.id_table = lsdc_pciid_list,
.probe = lsdc_pci_probe,
.remove = lsdc_pci_remove,
+ .shutdown = lsdc_pci_shutdown,
.driver.pm = &lsdc_pm_ops,
};
diff --git a/drivers/gpu/drm/mcde/mcde_drv.c b/drivers/gpu/drm/mcde/mcde_drv.c
index a2572fb311f0..10c06440c7e7 100644
--- a/drivers/gpu/drm/mcde/mcde_drv.c
+++ b/drivers/gpu/drm/mcde/mcde_drv.c
@@ -459,6 +459,14 @@ static void mcde_remove(struct platform_device *pdev)
regulator_disable(mcde->epod);
}
+static void mcde_shutdown(struct platform_device *pdev)
+{
+ struct drm_device *drm = platform_get_drvdata(pdev);
+
+ if (drm->registered)
+ drm_atomic_helper_shutdown(drm);
+}
+
static const struct of_device_id mcde_of_match[] = {
{
.compatible = "ste,mcde",
@@ -473,6 +481,7 @@ static struct platform_driver mcde_driver = {
},
.probe = mcde_probe,
.remove_new = mcde_remove,
+ .shutdown = mcde_shutdown,
};
static struct platform_driver *const component_drivers[] = {
diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c b/drivers/gpu/drm/omapdrm/omap_drv.c
index afeeb7737552..b2835b3ea6f5 100644
--- a/drivers/gpu/drm/omapdrm/omap_drv.c
+++ b/drivers/gpu/drm/omapdrm/omap_drv.c
@@ -817,6 +817,13 @@ static void pdev_remove(struct platform_device *pdev)
kfree(priv);
}
+static void pdev_shutdown(struct platform_device *pdev)
+{
+ struct omap_drm_private *priv = platform_get_drvdata(pdev);
+
+ drm_atomic_helper_shutdown(priv->ddev);
+}
+
#ifdef CONFIG_PM_SLEEP
static int omap_drm_suspend(struct device *dev)
{
@@ -846,6 +853,7 @@ static struct platform_driver pdev = {
},
.probe = pdev_probe,
.remove_new = pdev_remove,
+ .shutdown = pdev_shutdown,
};
static struct platform_driver * const drivers[] = {
diff --git a/drivers/gpu/drm/qxl/qxl_drv.c b/drivers/gpu/drm/qxl/qxl_drv.c
index b30ede1cf62d..a4144c62ca93 100644
--- a/drivers/gpu/drm/qxl/qxl_drv.c
+++ b/drivers/gpu/drm/qxl/qxl_drv.c
@@ -163,6 +163,12 @@ qxl_pci_remove(struct pci_dev *pdev)
vga_put(pdev, VGA_RSRC_LEGACY_IO);
}
+static void
+qxl_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
DEFINE_DRM_GEM_FOPS(qxl_fops);
static int qxl_drm_freeze(struct drm_device *dev)
@@ -269,6 +275,7 @@ static struct pci_driver qxl_pci_driver = {
.id_table = pciidlist,
.probe = qxl_pci_probe,
.remove = qxl_pci_remove,
+ .shutdown = qxl_pci_shutdown,
.driver.pm = &qxl_pm_ops,
};
diff --git a/drivers/gpu/drm/sti/sti_drv.c b/drivers/gpu/drm/sti/sti_drv.c
index 2390c1bb6596..4bab93c4fefd 100644
--- a/drivers/gpu/drm/sti/sti_drv.c
+++ b/drivers/gpu/drm/sti/sti_drv.c
@@ -174,6 +174,7 @@ static void sti_cleanup(struct drm_device *ddev)
drm_atomic_helper_shutdown(ddev);
drm_mode_config_cleanup(ddev);
component_unbind_all(ddev->dev, ddev);
+ dev_set_drvdata(ddev->dev, NULL);
kfree(private);
ddev->dev_private = NULL;
}
@@ -253,6 +254,11 @@ static void sti_platform_remove(struct platform_device *pdev)
component_master_del(&pdev->dev, &sti_ops);
}
+static void sti_platform_shutdown(struct platform_device *pdev)
+{
+ drm_atomic_helper_shutdown(platform_get_drvdata(pdev));
+}
+
static const struct of_device_id sti_dt_ids[] = {
{ .compatible = "st,sti-display-subsystem", },
{ /* end node */ },
@@ -262,6 +268,7 @@ MODULE_DEVICE_TABLE(of, sti_dt_ids);
static struct platform_driver sti_platform_driver = {
.probe = sti_platform_probe,
.remove_new = sti_platform_remove,
+ .shutdown = sti_platform_shutdown,
.driver = {
.name = DRIVER_NAME,
.of_match_table = sti_dt_ids,
diff --git a/drivers/gpu/drm/sun4i/sun4i_drv.c b/drivers/gpu/drm/sun4i/sun4i_drv.c
index 6a8dfc022d3c..35d7a7ffd208 100644
--- a/drivers/gpu/drm/sun4i/sun4i_drv.c
+++ b/drivers/gpu/drm/sun4i/sun4i_drv.c
@@ -413,6 +413,11 @@ static void sun4i_drv_remove(struct platform_device *pdev)
component_master_del(&pdev->dev, &sun4i_drv_master_ops);
}
+static void sun4i_drv_shutdown(struct platform_device *pdev)
+{
+ drm_atomic_helper_shutdown(platform_get_drvdata(pdev));
+}
+
static const struct of_device_id sun4i_drv_of_table[] = {
{ .compatible = "allwinner,sun4i-a10-display-engine" },
{ .compatible = "allwinner,sun5i-a10s-display-engine" },
@@ -437,6 +442,7 @@ MODULE_DEVICE_TABLE(of, sun4i_drv_of_table);
static struct platform_driver sun4i_drv_platform_driver = {
.probe = sun4i_drv_probe,
.remove_new = sun4i_drv_remove,
+ .shutdown = sun4i_drv_shutdown,
.driver = {
.name = "sun4i-drm",
.of_match_table = sun4i_drv_of_table,
diff --git a/drivers/gpu/drm/tiny/bochs.c b/drivers/gpu/drm/tiny/bochs.c
index d254679a136e..c23c9f0cf49c 100644
--- a/drivers/gpu/drm/tiny/bochs.c
+++ b/drivers/gpu/drm/tiny/bochs.c
@@ -690,6 +690,11 @@ static void bochs_pci_remove(struct pci_dev *pdev)
drm_dev_put(dev);
}
+static void bochs_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
static const struct pci_device_id bochs_pci_tbl[] = {
{
.vendor = 0x1234,
@@ -720,6 +725,7 @@ static struct pci_driver bochs_pci_driver = {
.id_table = bochs_pci_tbl,
.probe = bochs_pci_probe,
.remove = bochs_pci_remove,
+ .shutdown = bochs_pci_shutdown,
.driver.pm = &bochs_pm_ops,
};
diff --git a/drivers/gpu/drm/tiny/cirrus.c b/drivers/gpu/drm/tiny/cirrus.c
index 594bc472862f..c5c34cd2edc1 100644
--- a/drivers/gpu/drm/tiny/cirrus.c
+++ b/drivers/gpu/drm/tiny/cirrus.c
@@ -727,6 +727,11 @@ static void cirrus_pci_remove(struct pci_dev *pdev)
drm_atomic_helper_shutdown(dev);
}
+static void cirrus_pci_shutdown(struct pci_dev *pdev)
+{
+ drm_atomic_helper_shutdown(pci_get_drvdata(pdev));
+}
+
static const struct pci_device_id pciidlist[] = {
{
.vendor = PCI_VENDOR_ID_CIRRUS,
@@ -748,6 +753,7 @@ static struct pci_driver cirrus_pci_driver = {
.id_table = pciidlist,
.probe = cirrus_pci_probe,
.remove = cirrus_pci_remove,
+ .shutdown = cirrus_pci_shutdown,
};
drm_module_pci_driver(cirrus_pci_driver)
--
2.42.0.283.g2d96d420d3-goog
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
@ 2023-09-04 7:58 ` Maxime Ripard
2023-09-05 21:06 ` Jernej Škrabec
` (3 subsequent siblings)
4 siblings, 0 replies; 10+ messages in thread
From: Maxime Ripard @ 2023-09-04 7:58 UTC (permalink / raw)
To: Douglas Anderson
Cc: airlied, airlied, alain.volmat, alexander.deucher,
alexandre.belloni, alison.wang, bbrezillon, christian.koenig,
claudiu.beznea, daniel, drawat.floss, dri-devel, javierm,
jernej.skrabec, jfalempe, jstultz, kong.kongxinwei, kraxel,
linus.walleij, linux-arm-kernel, linux-hyperv, linux-kernel,
linux-sunxi, liviu.dudau, nicolas.ferre, paul.kocialkowski, sam,
samuel, spice-devel, stefan, suijingfeng, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr, Maxime Ripard
On Fri, 1 Sep 2023 16:39:53 -0700, Douglas Anderson wrote:
> Based on grepping through the source code these drivers appear to be
> missing a call to drm_atomic_helper_shutdown() at system shutdown
> time. Among other things, this means that if a panel is in use that it
> won't be cleanly powered off at system shutdown time.
>
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
2023-09-04 7:58 ` Maxime Ripard
@ 2023-09-05 21:06 ` Jernej Škrabec
2023-09-15 9:11 ` suijingfeng
` (2 subsequent siblings)
4 siblings, 0 replies; 10+ messages in thread
From: Jernej Škrabec @ 2023-09-05 21:06 UTC (permalink / raw)
To: dri-devel, Maxime Ripard, Douglas Anderson
Cc: Douglas Anderson, airlied, airlied, alain.volmat,
alexander.deucher, alexandre.belloni, alison.wang, bbrezillon,
christian.koenig, claudiu.beznea, daniel, drawat.floss, javierm,
jfalempe, jstultz, kong.kongxinwei, kraxel, linus.walleij,
linux-arm-kernel, linux-hyperv, linux-kernel, linux-sunxi,
liviu.dudau, nicolas.ferre, paul.kocialkowski, sam, samuel,
spice-devel, stefan, suijingfeng, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr
Dne sobota, 02. september 2023 ob 01:39:53 CEST je Douglas Anderson
napisal(a):
> Based on grepping through the source code these drivers appear to be
> missing a call to drm_atomic_helper_shutdown() at system shutdown
> time. Among other things, this means that if a panel is in use that it
> won't be cleanly powered off at system shutdown time.
>
> The fact that we should call drm_atomic_helper_shutdown() in the case
> of OS shutdown/restart comes straight out of the kernel doc "driver
> instance overview" in drm_drv.c.
>
> All of the drivers in this patch were fairly straightforward to fix
> since they already had a call to drm_atomic_helper_shutdown() at
> remove/unbind time but were just lacking one at system shutdown. The
> only hitch is that some of these drivers use the component model to
> register/unregister their DRM devices. The shutdown callback is part
> of the original device. The typical solution here, based on how other
> DRM drivers do this, is to keep track of whether the device is bound
> based on drvdata. In most cases the drvdata is the drm_device, so we
> can just make sure it is NULL when the device is not bound. In some
> drivers, this required minor code changes. To make things simpler,
> drm_atomic_helper_shutdown() has been modified to consider a NULL
> drm_device as a noop in the patch ("drm/atomic-helper:
> drm_atomic_helper_shutdown(NULL) should be a noop").
>
> Suggested-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
> This commit is only compile-time tested.
>
> Note that checkpatch yells that "drivers/gpu/drm/tiny/cirrus.c" is
> marked as 'obsolete', but it seems silly not to include the fix if
> it's already been written. If someone wants me to take that out,
> though, I can.
>
> drivers/gpu/drm/arm/display/komeda/komeda_drv.c | 9 +++++++++
> drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 7 +++++++
> drivers/gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
> drivers/gpu/drm/arm/hdlcd_drv.c | 6 ++++++
> drivers/gpu/drm/arm/malidp_drv.c | 6 ++++++
> drivers/gpu/drm/ast/ast_drv.c | 6 ++++++
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 6 ++++++
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 ++++++++
> drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++++++
> drivers/gpu/drm/hyperv/hyperv_drm_drv.c | 6 ++++++
> drivers/gpu/drm/logicvc/logicvc_drm.c | 9 +++++++++
> drivers/gpu/drm/loongson/lsdc_drv.c | 6 ++++++
> drivers/gpu/drm/mcde/mcde_drv.c | 9 +++++++++
> drivers/gpu/drm/omapdrm/omap_drv.c | 8 ++++++++
> drivers/gpu/drm/qxl/qxl_drv.c | 7 +++++++
> drivers/gpu/drm/sti/sti_drv.c | 7 +++++++
> drivers/gpu/drm/sun4i/sun4i_drv.c | 6 ++++++
For sun4i:
Tested-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> drivers/gpu/drm/tiny/bochs.c | 6 ++++++
> drivers/gpu/drm/tiny/cirrus.c | 6 ++++++
> 19 files changed, 125 insertions(+)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times
2023-09-01 23:39 [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Douglas Anderson
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
@ 2023-09-13 18:31 ` Doug Anderson
1 sibling, 0 replies; 10+ messages in thread
From: Doug Anderson @ 2023-09-13 18:31 UTC (permalink / raw)
To: dri-devel, Maxime Ripard
Cc: airlied, airlied, alain.volmat, alexander.deucher,
alexandre.belloni, alexandre.torgue, alison.wang, andrew,
bbrezillon, christian.koenig, claudiu.beznea, daniel,
drawat.floss, emma, hdegoede, javierm, jernej.skrabec, jfalempe,
joel, jstultz, jyri.sarha, kong.kongxinwei, kraxel, linus.walleij,
linux-arm-kernel, linux-aspeed, linux-hyperv, linux-kernel,
linux-stm32, linux-sunxi, liviu.dudau, maarten.lankhorst,
mcoquelin.stm32, nicolas.ferre, paul.kocialkowski, philippe.cornu,
raphael.gallais-pou, robh, sam, samuel, spice-devel, stefan,
steven.price, suijingfeng, sumit.semwal, tiantao6, tomi.valkeinen,
tzimmermann, u.kleine-koenig, virtualization, wens, xinliang.liu,
yannick.fertre, yongqin.liu, zackr
Hi,
On Fri, Sep 1, 2023 at 4:40 PM Douglas Anderson <dianders@chromium.org> wrote:
>
>
> NOTE: in order to avoid email sending limits on the cover letter, I've
> split this patch series in two. Patches that target drm-misc and ones
> that don't. The cover letter of the two is identical other than this note.
>
> This patch series came about after a _long_ discussion between me and
> Maxime Ripard in response to a different patch I sent out [1]. As part
> of that discussion, we realized that it would be good if DRM drivers
> consistently called drm_atomic_helper_shutdown() properly at shutdown
> and driver remove time as it's documented that they should do. The
> eventual goal of this would be to enable removing some hacky code from
> panel drivers where they had to hook into shutdown themselves because
> the DRM driver wasn't calling them.
>
> It turns out that quite a lot of drivers seemed to be missing
> drm_atomic_helper_shutdown() in one or both places that it was
> supposed to be. This patch series attempts to fix all the drivers that
> I was able to identify.
>
> NOTE: fixing this wasn't exactly cookie cutter. Each driver has its
> own unique way of setting itself up and tearing itself down. Some
> drivers also use the component model, which adds extra fun. I've made
> my best guess at solving this and I've run a bunch of compile tests
> (specifically, allmodconfig for amd64, arm64, and powerpc). That being
> said, these code changes are not totally trivial and I've done zero
> real testing on them. Making these patches was also a little mind
> numbing and I'm certain my eyes glazed over at several points when
> writing them. What I'm trying to say is to please double-check that I
> didn't do anything too silly, like cast your driver's drvdata to the
> wrong type. Even better, test these patches!
>
> I've organized this series like this:
> 1. One patch for all simple cases of just needing a call at shutdown
> time for drivers that go through drm-misc.
> 2. A separate patch for "drm/vc4", even though it goes through
> drm-misc, since I wanted to leave an extra note for that one.
> 3. Patches for drivers that just needed a call at shutdown time for
> drivers that _don't_ go through drm-misc.
> 4. Patches for the few drivers that had the call at shutdown time but
> lacked it at remove time.
> 5. One patch for all simple cases of needing a call at shutdown and
> remove (or unbind) time for drivers that go through drm-misc.
> 6. A separate patch for "drm/hisilicon/kirin", even though it goes
> through drm-misc, since I wanted to leave an extra note for that
> one.
> 7. Patches for drivers that needed a call at shutdown and remove (or
> unbind) time for drivers that _don't_ go through drm-misc.
>
> I've labeled this patch series as RFT (request for testing) to help
> call attention to the fact that I didn't personally test any of these
> patches.
>
> If you're a maintainer of one of these drivers and you think that the
> patch for your driver looks fabulous, you've tested it, and you'd like
> to land it right away then please do. For non-drm-misc drivers there
> are no dependencies here. Some of the drm-misc drivers depend on the
> first patch, AKA ("drm/atomic-helper: drm_atomic_helper_shutdown(NULL)
> should be a noop"). I've tried to call this out but it also should be
> obvious once you know to look for it.
>
> I'd like to call out a few drivers that I _didn't_ fix in this series
> and why. If any of these drivers should be fixed then please yell.
> - DRM driers backed by usb_driver (like gud, gm12u320, udl): I didn't
> add the call to drm_atomic_helper_shutdown() at shutdown time
> because there's no ".shutdown" callback for them USB drivers. Given
> that USB is hotpluggable, I'm assuming that they are robust against
> this and the special shutdown callback isn't needed.
> - ofdrm and simpledrm: These didn't have drm_atomic_helper_shutdown()
> in either shutdown or remove, but I didn't add it. I think that's OK
> since they're sorta special and not really directly controlling
> hardware power sequencing.
> - virtio, vkms, vmwgfx, xen: I believe these are all virtual (thus
> they wouldn't directly drive a panel) and adding the shutdown
> didn't look straightforward, so I skipped them.
>
> I've let each patch in the series get CCed straight from
> get_maintainer. That means not everyone will have received every patch
> but everyone should be on the cover letter. I know some people dislike
> this but when touching this many drivers there's not much
> choice. dri-devel and lkml have been CCed and lore/lei exist, so
> hopefully that's enough for folks. I'm happy to add people to the
> whole series for future posts.
>
> [1] https://lore.kernel.org/lkml/20230804140605.RFC.4.I930069a32baab6faf46d6b234f89613b5cec0f14@changeid
>
>
> Douglas Anderson (6):
> drm/atomic-helper: drm_atomic_helper_shutdown(NULL) should be a noop
> drm: Call drm_atomic_helper_shutdown() at shutdown time for misc
> drivers
> drm/vc4: Call drm_atomic_helper_shutdown() at shutdown time
> drm/ssd130x: Call drm_atomic_helper_shutdown() at remove time
> drm: Call drm_atomic_helper_shutdown() at shutdown/remove time for
> misc drivers
> drm/hisilicon/kirin: Call drm_atomic_helper_shutdown() at
> shutdown/unbind time
>
> .../gpu/drm/arm/display/komeda/komeda_drv.c | 9 +++++
> .../gpu/drm/arm/display/komeda/komeda_kms.c | 7 ++++
> .../gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
> drivers/gpu/drm/arm/hdlcd_drv.c | 6 ++++
> drivers/gpu/drm/arm/malidp_drv.c | 6 ++++
> drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 7 ++++
> drivers/gpu/drm/ast/ast_drv.c | 6 ++++
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 6 ++++
> drivers/gpu/drm/drm_atomic_helper.c | 3 ++
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 +++++
> .../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++++
> .../gpu/drm/hisilicon/kirin/kirin_drm_drv.c | 9 +++++
> drivers/gpu/drm/hyperv/hyperv_drm_drv.c | 6 ++++
> drivers/gpu/drm/logicvc/logicvc_drm.c | 9 +++++
> drivers/gpu/drm/loongson/lsdc_drv.c | 6 ++++
> drivers/gpu/drm/mcde/mcde_drv.c | 9 +++++
> drivers/gpu/drm/mgag200/mgag200_drv.c | 8 +++++
> drivers/gpu/drm/omapdrm/omap_drv.c | 8 +++++
> drivers/gpu/drm/pl111/pl111_drv.c | 7 ++++
> drivers/gpu/drm/qxl/qxl_drv.c | 7 ++++
> drivers/gpu/drm/solomon/ssd130x.c | 1 +
> drivers/gpu/drm/sti/sti_drv.c | 7 ++++
> drivers/gpu/drm/stm/drv.c | 7 ++++
> drivers/gpu/drm/sun4i/sun4i_drv.c | 6 ++++
> drivers/gpu/drm/tilcdc/tilcdc_drv.c | 11 +++++-
> drivers/gpu/drm/tiny/bochs.c | 6 ++++
> drivers/gpu/drm/tiny/cirrus.c | 6 ++++
> drivers/gpu/drm/tve200/tve200_drv.c | 7 ++++
> drivers/gpu/drm/vboxvideo/vbox_drv.c | 10 ++++++
> drivers/gpu/drm/vc4/vc4_drv.c | 36 ++++++++++++-------
> 30 files changed, 217 insertions(+), 14 deletions(-)
Just a heads up to keep folks in the loop: I've landed the first patch
in the drm-misc series, AKA ("drm/atomic-helper:
drm_atomic_helper_shutdown(NULL) should be a noop"), but I haven't
landed any of the others yet. I'm going to give them another ~week
just to be sure there are no objections.
-Doug
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
2023-09-04 7:58 ` Maxime Ripard
2023-09-05 21:06 ` Jernej Škrabec
@ 2023-09-15 9:11 ` suijingfeng
2023-09-15 13:44 ` Doug Anderson
2023-09-19 7:31 ` Tomi Valkeinen
2023-09-21 18:46 ` Doug Anderson
4 siblings, 1 reply; 10+ messages in thread
From: suijingfeng @ 2023-09-15 9:11 UTC (permalink / raw)
To: Douglas Anderson, dri-devel, Maxime Ripard
Cc: airlied, airlied, alain.volmat, alexander.deucher,
alexandre.belloni, alison.wang, bbrezillon, christian.koenig,
claudiu.beznea, daniel, drawat.floss, javierm, jernej.skrabec,
jfalempe, jstultz, kong.kongxinwei, kraxel, linus.walleij,
linux-arm-kernel, linux-hyperv, linux-kernel, linux-sunxi,
liviu.dudau, nicolas.ferre, paul.kocialkowski, sam, samuel,
spice-devel, stefan, sumit.semwal, tiantao6, tomi.valkeinen,
tzimmermann, virtualization, wens, xinliang.liu, yongqin.liu,
zackr
Hi,
On 2023/9/2 07:39, Douglas Anderson wrote:
> Based on grepping through the source code these drivers appear to be
> missing a call to drm_atomic_helper_shutdown() at system shutdown
> time. Among other things, this means that if a panel is in use that it
> won't be cleanly powered off at system shutdown time.
>
> The fact that we should call drm_atomic_helper_shutdown() in the case
> of OS shutdown/restart comes straight out of the kernel doc "driver
> instance overview" in drm_drv.c.
>
> All of the drivers in this patch were fairly straightforward to fix
> since they already had a call to drm_atomic_helper_shutdown() at
> remove/unbind time but were just lacking one at system shutdown. The
> only hitch is that some of these drivers use the component model to
> register/unregister their DRM devices. The shutdown callback is part
> of the original device. The typical solution here, based on how other
> DRM drivers do this, is to keep track of whether the device is bound
> based on drvdata. In most cases the drvdata is the drm_device, so we
> can just make sure it is NULL when the device is not bound. In some
> drivers, this required minor code changes. To make things simpler,
> drm_atomic_helper_shutdown() has been modified to consider a NULL
> drm_device as a noop in the patch ("drm/atomic-helper:
> drm_atomic_helper_shutdown(NULL) should be a noop").
>
> Suggested-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
I have just tested the whole series, thanks for the patch. For drm/loongson only:
Reviewed-by: Sui Jingfeng <suijingfeng@loongson.cn>
Tested-by: Sui Jingfeng <suijingfeng@loongson.cn>
By the way, I add 'pr_info("lsdc_pci_shutdown\n");' into the lsdc_pci_shutdown() function,
And seeing that lsdc_pci_shutdown() will be called when reboot and shutdown the machine.
I did not witness something weird happen at present. As you have said, this is useful for
drm panels drivers. But for the rest(drm/hibmc, drm/ast, drm/mgag200 and drm/loongson etc)
drivers, you didn't mention what's the benefit for those drivers. Probably, you can
mention it with at least one sentence at the next version. I also prefer to alter the
lsdc_pci_shutdown() function as the following pattern:
static void lsdc_pci_shutdown(struct pci_dev *pdev)
{
struct drm_device *ddev = pci_get_drvdata(pdev);
drm_atomic_helper_shutdown(ddev);
}
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-15 9:11 ` suijingfeng
@ 2023-09-15 13:44 ` Doug Anderson
2023-09-15 14:02 ` suijingfeng
0 siblings, 1 reply; 10+ messages in thread
From: Doug Anderson @ 2023-09-15 13:44 UTC (permalink / raw)
To: suijingfeng
Cc: dri-devel, Maxime Ripard, airlied, airlied, alain.volmat,
alexander.deucher, alexandre.belloni, alison.wang, bbrezillon,
christian.koenig, claudiu.beznea, daniel, drawat.floss, javierm,
jernej.skrabec, jfalempe, jstultz, kong.kongxinwei, kraxel,
linus.walleij, linux-arm-kernel, linux-hyperv, linux-kernel,
linux-sunxi, liviu.dudau, nicolas.ferre, paul.kocialkowski, sam,
samuel, spice-devel, stefan, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr
Hi,
On Fri, Sep 15, 2023 at 2:11 AM suijingfeng <suijingfeng@loongson.cn> wrote:
>
> Hi,
>
>
> On 2023/9/2 07:39, Douglas Anderson wrote:
> > Based on grepping through the source code these drivers appear to be
> > missing a call to drm_atomic_helper_shutdown() at system shutdown
> > time. Among other things, this means that if a panel is in use that it
> > won't be cleanly powered off at system shutdown time.
> >
> > The fact that we should call drm_atomic_helper_shutdown() in the case
> > of OS shutdown/restart comes straight out of the kernel doc "driver
> > instance overview" in drm_drv.c.
> >
> > All of the drivers in this patch were fairly straightforward to fix
> > since they already had a call to drm_atomic_helper_shutdown() at
> > remove/unbind time but were just lacking one at system shutdown. The
> > only hitch is that some of these drivers use the component model to
> > register/unregister their DRM devices. The shutdown callback is part
> > of the original device. The typical solution here, based on how other
> > DRM drivers do this, is to keep track of whether the device is bound
> > based on drvdata. In most cases the drvdata is the drm_device, so we
> > can just make sure it is NULL when the device is not bound. In some
> > drivers, this required minor code changes. To make things simpler,
> > drm_atomic_helper_shutdown() has been modified to consider a NULL
> > drm_device as a noop in the patch ("drm/atomic-helper:
> > drm_atomic_helper_shutdown(NULL) should be a noop").
> >
> > Suggested-by: Maxime Ripard <mripard@kernel.org>
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > ---
>
>
> I have just tested the whole series, thanks for the patch. For drm/loongson only:
>
>
> Reviewed-by: Sui Jingfeng <suijingfeng@loongson.cn>
> Tested-by: Sui Jingfeng <suijingfeng@loongson.cn>
Thanks!
> By the way, I add 'pr_info("lsdc_pci_shutdown\n");' into the lsdc_pci_shutdown() function,
> And seeing that lsdc_pci_shutdown() will be called when reboot and shutdown the machine.
> I did not witness something weird happen at present. As you have said, this is useful for
> drm panels drivers. But for the rest(drm/hibmc, drm/ast, drm/mgag200 and drm/loongson etc)
> drivers, you didn't mention what's the benefit for those drivers.
I didn't mention it because I have no idea! I presume that for
non-drm_panel use cases it's not a huge deal, otherwise it wouldn't
have been missing from so many drivers. Thus, my "one sentence" reason
for the non-drm_panel case is just "we should do this because the
documentation of the API says we should", which is already in the
commit message. ;-)
If you have a specific other benefit you'd like me to list then I'm happy to.
> Probably, you can
> mention it with at least one sentence at the next version. I also prefer to alter the
> lsdc_pci_shutdown() function as the following pattern:
>
>
> static void lsdc_pci_shutdown(struct pci_dev *pdev)
> {
>
> struct drm_device *ddev = pci_get_drvdata(pdev);
>
> drm_atomic_helper_shutdown(ddev);
> }
I was hoping to land this patch without spinning it unless there's a
good reason. How strongly do you feel about needing to change the
above? I will note that I coded it the way I did specifically to try
to follow the style in the documentation in "drm_drv.c". In the
example "driver_shutdown()" function you can see that they combined it
into one line and so I followed that style. ;-) That being said, I
have no problem changing this if I spin the patch.
-Doug
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-15 13:44 ` Doug Anderson
@ 2023-09-15 14:02 ` suijingfeng
0 siblings, 0 replies; 10+ messages in thread
From: suijingfeng @ 2023-09-15 14:02 UTC (permalink / raw)
To: Doug Anderson
Cc: dri-devel, Maxime Ripard, airlied, airlied, alain.volmat,
alexander.deucher, alexandre.belloni, alison.wang, bbrezillon,
christian.koenig, claudiu.beznea, daniel, drawat.floss, javierm,
jernej.skrabec, jfalempe, jstultz, kong.kongxinwei, kraxel,
linus.walleij, linux-arm-kernel, linux-hyperv, linux-kernel,
linux-sunxi, liviu.dudau, nicolas.ferre, paul.kocialkowski, sam,
samuel, spice-devel, stefan, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr
Hi,
On 2023/9/15 21:44, Doug Anderson wrote:
> Hi,
>
> On Fri, Sep 15, 2023 at 2:11 AM suijingfeng <suijingfeng@loongson.cn> wrote:
>> Hi,
>>
>>
>> On 2023/9/2 07:39, Douglas Anderson wrote:
>>> Based on grepping through the source code these drivers appear to be
>>> missing a call to drm_atomic_helper_shutdown() at system shutdown
>>> time. Among other things, this means that if a panel is in use that it
>>> won't be cleanly powered off at system shutdown time.
>>>
>>> The fact that we should call drm_atomic_helper_shutdown() in the case
>>> of OS shutdown/restart comes straight out of the kernel doc "driver
>>> instance overview" in drm_drv.c.
>>>
>>> All of the drivers in this patch were fairly straightforward to fix
>>> since they already had a call to drm_atomic_helper_shutdown() at
>>> remove/unbind time but were just lacking one at system shutdown. The
>>> only hitch is that some of these drivers use the component model to
>>> register/unregister their DRM devices. The shutdown callback is part
>>> of the original device. The typical solution here, based on how other
>>> DRM drivers do this, is to keep track of whether the device is bound
>>> based on drvdata. In most cases the drvdata is the drm_device, so we
>>> can just make sure it is NULL when the device is not bound. In some
>>> drivers, this required minor code changes. To make things simpler,
>>> drm_atomic_helper_shutdown() has been modified to consider a NULL
>>> drm_device as a noop in the patch ("drm/atomic-helper:
>>> drm_atomic_helper_shutdown(NULL) should be a noop").
>>>
>>> Suggested-by: Maxime Ripard <mripard@kernel.org>
>>> Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>> ---
>>
>> I have just tested the whole series, thanks for the patch. For drm/loongson only:
>>
>>
>> Reviewed-by: Sui Jingfeng <suijingfeng@loongson.cn>
>> Tested-by: Sui Jingfeng <suijingfeng@loongson.cn>
> Thanks!
>
>
>> By the way, I add 'pr_info("lsdc_pci_shutdown\n");' into the lsdc_pci_shutdown() function,
>> And seeing that lsdc_pci_shutdown() will be called when reboot and shutdown the machine.
>> I did not witness something weird happen at present. As you have said, this is useful for
>> drm panels drivers. But for the rest(drm/hibmc, drm/ast, drm/mgag200 and drm/loongson etc)
>> drivers, you didn't mention what's the benefit for those drivers.
> I didn't mention it because I have no idea! I presume that for
> non-drm_panel use cases it's not a huge deal, otherwise it wouldn't
> have been missing from so many drivers. Thus, my "one sentence" reason
> for the non-drm_panel case is just "we should do this because the
> documentation of the API says we should", which is already in the
> commit message. ;-)
>
OK, this sound fine.
> If you have a specific other benefit you'd like me to list then I'm happy to.
You should think about the answer of this question yourself.
But I will not object if you can't find one. OK. :-)
>
>> Probably, you can
>> mention it with at least one sentence at the next version. I also prefer to alter the
>> lsdc_pci_shutdown() function as the following pattern:
>>
>>
>> static void lsdc_pci_shutdown(struct pci_dev *pdev)
>> {
>>
>> struct drm_device *ddev = pci_get_drvdata(pdev);
>>
>> drm_atomic_helper_shutdown(ddev);
>> }
> I was hoping to land this patch without spinning it unless there's a
> good reason. How strongly do you feel about needing to change the
> above?
Not very strong, this version looks just fine.
I will not object if you keep it as is.
But I will also hear what the others reviewers say.
Thanks for the patch.
>
> -Doug
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
` (2 preceding siblings ...)
2023-09-15 9:11 ` suijingfeng
@ 2023-09-19 7:31 ` Tomi Valkeinen
2023-09-21 18:46 ` Doug Anderson
4 siblings, 0 replies; 10+ messages in thread
From: Tomi Valkeinen @ 2023-09-19 7:31 UTC (permalink / raw)
To: Douglas Anderson, dri-devel, Maxime Ripard
Cc: airlied, airlied, alain.volmat, alexander.deucher,
alexandre.belloni, alison.wang, bbrezillon, christian.koenig,
claudiu.beznea, daniel, drawat.floss, javierm, jernej.skrabec,
jfalempe, jstultz, kong.kongxinwei, kraxel, linus.walleij,
linux-arm-kernel, linux-hyperv, linux-kernel, linux-sunxi,
liviu.dudau, nicolas.ferre, paul.kocialkowski, sam, samuel,
spice-devel, stefan, suijingfeng, sumit.semwal, tiantao6,
tzimmermann, virtualization, wens, xinliang.liu, yongqin.liu,
zackr
On 02/09/2023 02:39, Douglas Anderson wrote:
> Based on grepping through the source code these drivers appear to be
> missing a call to drm_atomic_helper_shutdown() at system shutdown
> time. Among other things, this means that if a panel is in use that it
> won't be cleanly powered off at system shutdown time.
>
> The fact that we should call drm_atomic_helper_shutdown() in the case
> of OS shutdown/restart comes straight out of the kernel doc "driver
> instance overview" in drm_drv.c.
>
> All of the drivers in this patch were fairly straightforward to fix
> since they already had a call to drm_atomic_helper_shutdown() at
> remove/unbind time but were just lacking one at system shutdown. The
> only hitch is that some of these drivers use the component model to
> register/unregister their DRM devices. The shutdown callback is part
> of the original device. The typical solution here, based on how other
> DRM drivers do this, is to keep track of whether the device is bound
> based on drvdata. In most cases the drvdata is the drm_device, so we
> can just make sure it is NULL when the device is not bound. In some
> drivers, this required minor code changes. To make things simpler,
> drm_atomic_helper_shutdown() has been modified to consider a NULL
> drm_device as a noop in the patch ("drm/atomic-helper:
> drm_atomic_helper_shutdown(NULL) should be a noop").
>
> Suggested-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
For omapdrm:
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Tested-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Tomi
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
` (3 preceding siblings ...)
2023-09-19 7:31 ` Tomi Valkeinen
@ 2023-09-21 18:46 ` Doug Anderson
4 siblings, 0 replies; 10+ messages in thread
From: Doug Anderson @ 2023-09-21 18:46 UTC (permalink / raw)
To: dri-devel, Maxime Ripard
Cc: airlied, airlied, alain.volmat, alexander.deucher,
alexandre.belloni, alison.wang, bbrezillon, christian.koenig,
claudiu.beznea, daniel, drawat.floss, javierm, jernej.skrabec,
jfalempe, jstultz, kong.kongxinwei, kraxel, linus.walleij,
linux-arm-kernel, linux-hyperv, linux-kernel, linux-sunxi,
liviu.dudau, nicolas.ferre, paul.kocialkowski, sam, samuel,
spice-devel, stefan, suijingfeng, sumit.semwal, tiantao6,
tomi.valkeinen, tzimmermann, virtualization, wens, xinliang.liu,
yongqin.liu, zackr
Hi,
On Fri, Sep 1, 2023 at 4:40 PM Douglas Anderson <dianders@chromium.org> wrote:
>
> Based on grepping through the source code these drivers appear to be
> missing a call to drm_atomic_helper_shutdown() at system shutdown
> time. Among other things, this means that if a panel is in use that it
> won't be cleanly powered off at system shutdown time.
>
> The fact that we should call drm_atomic_helper_shutdown() in the case
> of OS shutdown/restart comes straight out of the kernel doc "driver
> instance overview" in drm_drv.c.
>
> All of the drivers in this patch were fairly straightforward to fix
> since they already had a call to drm_atomic_helper_shutdown() at
> remove/unbind time but were just lacking one at system shutdown. The
> only hitch is that some of these drivers use the component model to
> register/unregister their DRM devices. The shutdown callback is part
> of the original device. The typical solution here, based on how other
> DRM drivers do this, is to keep track of whether the device is bound
> based on drvdata. In most cases the drvdata is the drm_device, so we
> can just make sure it is NULL when the device is not bound. In some
> drivers, this required minor code changes. To make things simpler,
> drm_atomic_helper_shutdown() has been modified to consider a NULL
> drm_device as a noop in the patch ("drm/atomic-helper:
> drm_atomic_helper_shutdown(NULL) should be a noop").
>
> Suggested-by: Maxime Ripard <mripard@kernel.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
> This commit is only compile-time tested.
>
> Note that checkpatch yells that "drivers/gpu/drm/tiny/cirrus.c" is
> marked as 'obsolete', but it seems silly not to include the fix if
> it's already been written. If someone wants me to take that out,
> though, I can.
>
> drivers/gpu/drm/arm/display/komeda/komeda_drv.c | 9 +++++++++
> drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 7 +++++++
> drivers/gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
> drivers/gpu/drm/arm/hdlcd_drv.c | 6 ++++++
> drivers/gpu/drm/arm/malidp_drv.c | 6 ++++++
> drivers/gpu/drm/ast/ast_drv.c | 6 ++++++
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 6 ++++++
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 8 ++++++++
> drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++++++
> drivers/gpu/drm/hyperv/hyperv_drm_drv.c | 6 ++++++
> drivers/gpu/drm/logicvc/logicvc_drm.c | 9 +++++++++
> drivers/gpu/drm/loongson/lsdc_drv.c | 6 ++++++
> drivers/gpu/drm/mcde/mcde_drv.c | 9 +++++++++
> drivers/gpu/drm/omapdrm/omap_drv.c | 8 ++++++++
> drivers/gpu/drm/qxl/qxl_drv.c | 7 +++++++
> drivers/gpu/drm/sti/sti_drv.c | 7 +++++++
> drivers/gpu/drm/sun4i/sun4i_drv.c | 6 ++++++
> drivers/gpu/drm/tiny/bochs.c | 6 ++++++
> drivers/gpu/drm/tiny/cirrus.c | 6 ++++++
> 19 files changed, 125 insertions(+)
This has been about 3 weeks now and it feels like that's enough bake
time and several people have managed to test it (thanks!). Landing in
drm-misc-next:
ce3d99c83495 drm: Call drm_atomic_helper_shutdown() at shutdown time
for misc drivers
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-09-21 18:47 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-01 23:39 [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Douglas Anderson
2023-09-01 23:39 ` [RFT PATCH 2/6] drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers Douglas Anderson
2023-09-04 7:58 ` Maxime Ripard
2023-09-05 21:06 ` Jernej Škrabec
2023-09-15 9:11 ` suijingfeng
2023-09-15 13:44 ` Doug Anderson
2023-09-15 14:02 ` suijingfeng
2023-09-19 7:31 ` Tomi Valkeinen
2023-09-21 18:46 ` Doug Anderson
2023-09-13 18:31 ` [RFT PATCH 0/6] drm: drm-misc drivers call drm_atomic_helper_shutdown() at the right times Doug Anderson
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).