Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Philipp Stanner <pstanner@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	 Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	dakr@redhat.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	 linux-pci@vger.kernel.org
Subject: Re: [PATCH v8 08/13] PCI: Move pinned status bit to struct pci_dev
Date: Mon, 10 Jun 2024 12:19:58 +0200	[thread overview]
Message-ID: <bae495cf171db1415cf14c44fb450b81148a6e0d.camel@redhat.com> (raw)
In-Reply-To: <20240610093149.20640-9-pstanner@redhat.com>

On Mon, 2024-06-10 at 11:31 +0200, Philipp Stanner wrote:
> The bit describing whether the PCI device is currently pinned is stored
> in struct pci_devres. To clean up and simplify the PCI devres API, it's
> better if this information is stored in struct pci_dev.
> 
> This will later permit simplifying pcim_enable_device().
> 
> Move the 'pinned' boolean bit to struct pci_dev.
> 
> Restructure bits in struct pci_dev so the pm / pme fields are next to
> each other.
> 
> Signed-off-by: Philipp Stanner <pstanner@redhat.com>
> ---
>  drivers/pci/devres.c | 14 ++++----------
>  drivers/pci/pci.h    |  1 -
>  include/linux/pci.h  |  4 +++-
>  3 files changed, 7 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/pci/devres.c b/drivers/pci/devres.c
> index 9d25940ce260..2696baef5c2c 100644
> --- a/drivers/pci/devres.c
> +++ b/drivers/pci/devres.c
> @@ -403,7 +403,7 @@ static void pcim_release(struct device *gendev, void *res)
>         if (this->restore_intx)
>                 pci_intx(dev, this->orig_intx);
>  
> -       if (pci_is_enabled(dev) && !this->pinned)
> +       if (pci_is_enabled(dev) && !dev->pinned)
>                 pci_disable_device(dev);
>  }
>  
> @@ -459,18 +459,12 @@ EXPORT_SYMBOL(pcim_enable_device);
>   * pcim_pin_device - Pin managed PCI device
>   * @pdev: PCI device to pin
>   *
> - * Pin managed PCI device @pdev.  Pinned device won't be disabled on
> - * driver detach.  @pdev must have been enabled with
> - * pcim_enable_device().
> + * Pin managed PCI device @pdev. Pinned device won't be disabled on driver
> + * detach. @pdev must have been enabled with pcim_enable_device().
>   */
>  void pcim_pin_device(struct pci_dev *pdev)
>  {
> -       struct pci_devres *dr;
> -
> -       dr = find_pci_dr(pdev);
> -       WARN_ON(!dr || !pci_is_enabled(pdev));
> -       if (dr)
> -               dr->pinned = 1;
> +       pdev->pinned = true;
>  }
>  EXPORT_SYMBOL(pcim_pin_device);
>  
> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
> index d7f00b43b098..6e02ba1b5947 100644
> --- a/drivers/pci/pci.h
> +++ b/drivers/pci/pci.h
> @@ -821,7 +821,6 @@ static inline pci_power_t mid_pci_get_power_state(struct pci_dev *pdev)
>   * then remove them from here.
>   */
>  struct pci_devres {
> -       unsigned int pinned:1;
>         unsigned int orig_intx:1;
>         unsigned int restore_intx:1;
>         unsigned int mwi:1;
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index fb004fd4e889..cc9247f78158 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -367,10 +367,12 @@ struct pci_dev {
>                                            this is D0-D3, D0 being fully
>                                            functional, and D3 being off. */
>         u8              pm_cap;         /* PM capability offset */
> -       unsigned int    imm_ready:1;    /* Supports Immediate Readiness */
>         unsigned int    pme_support:5;  /* Bitmask of states from which PME#
>                                            can be generated */
>         unsigned int    pme_poll:1;     /* Poll device's PME status bit */
> +       unsigned int    enabled:1;      /* Whether this dev is enabled */

Ah crap, here it survived for some reason...

Should just be dead code and not have any effect. In any case, we
should remove it.

@Bjorn: Feel free to remove it yourself. Otherwise I could provide a v9
together with potential further feedback taken into account in a few
days

Thx,
P.

> +       unsigned int    pinned:1;       /* Whether this dev is pinned */
> +       unsigned int    imm_ready:1;    /* Supports Immediate Readiness */
>         unsigned int    d1_support:1;   /* Low power state D1 is supported */
>         unsigned int    d2_support:1;   /* Low power state D2 is supported */
>         unsigned int    no_d1d2:1;      /* D1 and D2 are forbidden */


  reply	other threads:[~2024-06-10 10:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  9:31 [PATCH v8 00/13] Make PCI's devres API more consistent Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 01/13] PCI: Add and use devres helper for bit masks Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 02/13] PCI: Add devres helpers for iomap table Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 03/13] PCI: Reimplement plural devres functions Philipp Stanner
2024-06-11 21:44   ` Bjorn Helgaas
2024-06-12  8:51     ` Philipp Stanner
2024-06-12 20:42       ` Bjorn Helgaas
2024-06-13  6:51         ` Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 04/13] PCI: Deprecate two surplus " Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 05/13] PCI: Make devres region requests consistent Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 06/13] PCI: Warn users about complicated devres nature Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 07/13] PCI: Remove enabled status bit from pci_devres Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 08/13] PCI: Move pinned status bit to struct pci_dev Philipp Stanner
2024-06-10 10:19   ` Philipp Stanner [this message]
2024-06-10  9:31 ` [PATCH v8 09/13] PCI: Give pcim_set_mwi() its own devres callback Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 10/13] PCI: Give pci_intx() " Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 11/13] PCI: Remove legacy pcim_release() Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 12/13] PCI: Add pcim_iomap_range() Philipp Stanner
2024-06-10  9:31 ` [PATCH v8 13/13] drm/vboxvideo: fix mapping leaks 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=bae495cf171db1415cf14c44fb450b81148a6e0d.camel@redhat.com \
    --to=pstanner@redhat.com \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --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: 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