From: Philipp Stanner <phasta@mailbox.org>
To: Philipp Stanner <phasta@kernel.org>,
Zack Rusin <zack.rusin@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/vmgfx: Use non-hybrid PCI devres API
Date: Thu, 08 May 2025 12:40:44 +0200 [thread overview]
Message-ID: <e40cf04283e281e2d4a912ff75bce3c6cb8bcf97.camel@mailbox.org> (raw)
In-Reply-To: <20250423120643.66814-2-phasta@kernel.org>
On Wed, 2025-04-23 at 14:06 +0200, Philipp Stanner wrote:
> vmgfx enables its PCI device with pcim_enable_device(). This,
> implicitly, switches the function pci_request_regions() into managed
> mode, where it becomes a devres function.
>
> The PCI subsystem wants to remove this hybrid nature from its
> interfaces. To do so, users of the aforementioned combination of
> functions must be ported to non-hybrid functions.
>
> Moreover, since both functions are already managed in this driver,
> the
> calls to pci_release_regions() are unnecessary.
>
> Remove the calls to pci_release_regions().
>
> Replace the call to sometimes-managed pci_request_regions() with one
> to
> the always-managed pcim_request_all_regions().
>
> Signed-off-by: Philipp Stanner <phasta@kernel.org>
*PING*
> ---
> Changes in v2:
> - Fix unused variable error.
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 14 +++-----------
> 1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> index 0f32471c8533..1e3ebace32ae 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> @@ -733,7 +733,7 @@ static int vmw_setup_pci_resources(struct
> vmw_private *dev,
>
> pci_set_master(pdev);
>
> - ret = pci_request_regions(pdev, "vmwgfx probe");
> + ret = pcim_request_all_regions(pdev, "vmwgfx probe");
> if (ret)
> return ret;
>
> @@ -753,7 +753,6 @@ static int vmw_setup_pci_resources(struct
> vmw_private *dev,
> if (!dev->rmmio) {
> drm_err(&dev->drm,
> "Failed mapping registers mmio
> memory.\n");
> - pci_release_regions(pdev);
> return -ENOMEM;
> }
> } else if (pci_id == VMWGFX_PCI_ID_SVGA2) {
> @@ -774,11 +773,9 @@ static int vmw_setup_pci_resources(struct
> vmw_private *dev,
> if (IS_ERR(dev->fifo_mem)) {
> drm_err(&dev->drm,
> "Failed mapping FIFO memory.\n");
> - pci_release_regions(pdev);
> return PTR_ERR(dev->fifo_mem);
> }
> } else {
> - pci_release_regions(pdev);
> return -EINVAL;
> }
>
> @@ -856,7 +853,6 @@ static int vmw_driver_load(struct vmw_private
> *dev_priv, u32 pci_id)
> int ret;
> enum vmw_res_type i;
> bool refuse_dma = false;
> - struct pci_dev *pdev = to_pci_dev(dev_priv->drm.dev);
>
> vmw_sw_context_init(dev_priv);
>
> @@ -872,7 +868,7 @@ static int vmw_driver_load(struct vmw_private
> *dev_priv, u32 pci_id)
> return ret;
> ret = vmw_detect_version(dev_priv);
> if (ret)
> - goto out_no_pci_or_version;
> + return ret;
>
>
> for (i = vmw_res_context; i < vmw_res_max; ++i) {
> @@ -1172,15 +1168,13 @@ static int vmw_driver_load(struct vmw_private
> *dev_priv, u32 pci_id)
>
> if (dev_priv->ctx.staged_bindings)
> vmw_binding_state_free(dev_priv-
> >ctx.staged_bindings);
> -out_no_pci_or_version:
> - pci_release_regions(pdev);
> +
> return ret;
> }
>
> static void vmw_driver_unload(struct drm_device *dev)
> {
> struct vmw_private *dev_priv = vmw_priv(dev);
> - struct pci_dev *pdev = to_pci_dev(dev->dev);
> enum vmw_res_type i;
>
> unregister_pm_notifier(&dev_priv->pm_nb);
> @@ -1216,8 +1210,6 @@ static void vmw_driver_unload(struct drm_device
> *dev)
> idr_destroy(&dev_priv->res_idr[i]);
>
> vmw_mksstat_remove_all(dev_priv);
> -
> - pci_release_regions(pdev);
> }
>
> static void vmw_postclose(struct drm_device *dev,
next prev parent reply other threads:[~2025-05-08 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:06 Philipp Stanner
2025-05-08 10:40 ` Philipp Stanner [this message]
2025-05-08 15:39 ` Zack Rusin
2025-05-09 6:47 ` Philipp Stanner
2025-05-09 9:23 ` Philipp Stanner
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=e40cf04283e281e2d4a912ff75bce3c6cb8bcf97.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@broadcom.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
all inboxes | Powered by JetHome®