From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 01/12] drm/xe: Remove shutdown
Date: Wed, 8 Nov 2023 17:38:25 +0200 [thread overview]
Message-ID: <ZUurcSAL5alOdjto@intel.com> (raw)
In-Reply-To: <20231108003344.1169016-2-michal.winiarski@intel.com>
On Wed, Nov 08, 2023 at 01:33:33AM +0100, Michał Winiarski wrote:
> It's not a required callback,
That doesn't seem right. Display should be turned off, all DMA
should be stopped, etc. here.
> and Xe implementation is empty
That is certainly true.
> - remove
> it.
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device.c | 4 ----
> drivers/gpu/drm/xe/xe_device.h | 1 -
> drivers/gpu/drm/xe/xe_pci.c | 6 ------
> 3 files changed, 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 515cdf599fab3..078c92576062a 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -476,10 +476,6 @@ void xe_device_remove(struct xe_device *xe)
> xe_irq_shutdown(xe);
> }
>
> -void xe_device_shutdown(struct xe_device *xe)
> -{
> -}
> -
> void xe_device_add_persistent_exec_queues(struct xe_device *xe, struct xe_exec_queue *q)
> {
> mutex_lock(&xe->persistent_engines.lock);
> diff --git a/drivers/gpu/drm/xe/xe_device.h b/drivers/gpu/drm/xe/xe_device.h
> index c4232de40ae08..ee89af6b1ea9c 100644
> --- a/drivers/gpu/drm/xe/xe_device.h
> +++ b/drivers/gpu/drm/xe/xe_device.h
> @@ -39,7 +39,6 @@ struct xe_device *xe_device_create(struct pci_dev *pdev,
> const struct pci_device_id *ent);
> int xe_device_probe(struct xe_device *xe);
> void xe_device_remove(struct xe_device *xe);
> -void xe_device_shutdown(struct xe_device *xe);
>
> void xe_device_add_persistent_exec_queues(struct xe_device *xe, struct xe_exec_queue *q);
> void xe_device_remove_persistent_exec_queues(struct xe_device *xe,
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 2fae45b9d88e1..007e272d2758f 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -748,11 +748,6 @@ static int xe_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> return err;
> }
>
> -static void xe_pci_shutdown(struct pci_dev *pdev)
> -{
> - xe_device_shutdown(pdev_to_xe_device(pdev));
> -}
> -
> #ifdef CONFIG_PM_SLEEP
> static void d3cold_toggle(struct pci_dev *pdev, enum toggle_d3cold toggle)
> {
> @@ -892,7 +887,6 @@ static struct pci_driver xe_pci_driver = {
> .id_table = pciidlist,
> .probe = xe_pci_probe,
> .remove = xe_pci_remove,
> - .shutdown = xe_pci_shutdown,
> #ifdef CONFIG_PM_SLEEP
> .driver.pm = &xe_pm_ops,
> #endif
> --
> 2.42.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-11-08 15:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 0:33 [Intel-xe] [PATCH 00/12] drm/xe: Probe tweaks and reordering (part 1) Michał Winiarski
2023-11-08 0:33 ` [Intel-xe] [PATCH 01/12] drm/xe: Remove shutdown Michał Winiarski
2023-11-08 15:38 ` Ville Syrjälä [this message]
2023-11-08 18:22 ` Michał Winiarski
2023-11-08 0:33 ` [Intel-xe] [PATCH 02/12] drm/xe: Skip calling drm_dev_put on probe error Michał Winiarski
2023-11-08 9:33 ` Matthew Brost
2023-11-08 17:18 ` Michał Winiarski
2023-11-08 10:23 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 03/12] drm/xe: Use managed pci_enable_device Michał Winiarski
2023-11-08 0:33 ` [Intel-xe] [PATCH 04/12] drm/xe/irq: Don't call pci_free_irq_vectors Michał Winiarski
2023-11-08 0:33 ` [Intel-xe] [PATCH 05/12] drm/xe/mmio: Move memory training check to probe vram Michał Winiarski
2023-11-08 9:38 ` Matthew Brost
2023-11-09 21:57 ` Matt Roper
2023-11-14 9:48 ` Michał Winiarski
2023-11-08 0:33 ` [Intel-xe] [PATCH 06/12] drm/xe: Move xe_set_dma_info outside of MMIO setup Michał Winiarski
2023-11-08 10:14 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 07/12] drm/xe: Move xe_mmio_probe_tiles " Michał Winiarski
2023-11-08 10:18 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 08/12] drm/xe: Split xe_info_init Michał Winiarski
2023-11-08 10:21 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 09/12] drm/xe: Introduce xe_tile_init_early and use at earlier point in probe Michał Winiarski
2023-11-08 10:25 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 10/12] drm/xe: Map the entire BAR0 and hold onto the initial mapping Michał Winiarski
2023-11-08 10:57 ` Matthew Brost
2023-11-08 0:33 ` [Intel-xe] [PATCH 11/12] drm/xe/device: Introduce xe_device_probe_early Michał Winiarski
2023-11-08 15:15 ` Matthew Brost
2023-11-14 9:46 ` Michał Winiarski
2023-11-13 15:11 ` Lucas De Marchi
2023-11-14 10:02 ` Michał Winiarski
2023-11-14 14:18 ` Lucas De Marchi
2023-11-08 0:33 ` [Intel-xe] [PATCH 12/12] drm/xe: Don't "peek" into GMD_ID Michał Winiarski
2023-11-08 0:38 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Probe tweaks and reordering (part 1) Patchwork
2023-11-08 0:38 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-08 0:39 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-08 0:47 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-08 0:47 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-11-08 0:48 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-11-08 1:20 ` [Intel-xe] ✓ CI.BAT: " 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=ZUurcSAL5alOdjto@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.winiarski@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox