Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Amit Pundir <amit.pundir@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Caleb Connolly <caleb.connolly@linaro.org>
Subject: Re: [PATCH v9 4/5] PCI/pwrctl: Add PCI power control core code
Date: Tue, 17 Jun 2025 18:35:39 -0500	[thread overview]
Message-ID: <20250617233539.GA1177120@bhelgaas> (raw)
In-Reply-To: <20240612082019.19161-5-brgl@bgdev.pl>

On Wed, Jun 12, 2024 at 10:20:17AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> Some PCI devices must be powered-on before they can be detected on the
> bus. Introduce a simple framework reusing the existing PCI OF
> infrastructure.

> +/**
> + * struct pci_pwrctl - PCI device power control context.
> + * @dev: Address of the power controlling device.
> + *
> + * An object of this type must be allocated by the PCI power control device and
> + * passed to the pwrctl subsystem to trigger a bus rescan and setup a device
> + * link with the device once it's up.
> + */
> +struct pci_pwrctl {
> +	struct device *dev;
> +
> +	/* Private: don't use. */
> +	struct notifier_block nb;
> +	struct device_link *link;
> +};

This is old and I should have noticed before, but we have partial
kernel-doc for this struct:

  $ find include -name \*pci\* | xargs scripts/kernel-doc -none
  Warning: include/linux/pci-pwrctrl.h:45 struct member 'nb' not described in 'pci_pwrctrl'
  Warning: include/linux/pci-pwrctrl.h:45 struct member 'link' not described in 'pci_pwrctrl'
  Warning: include/linux/pci-pwrctrl.h:45 struct member 'work' not described in 'pci_pwrctrl'


  reply	other threads:[~2025-06-17 23:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  8:20 [PATCH v9 0/5] PCI/pwrctl: initial implementation and first user Bartosz Golaszewski
2024-06-12  8:20 ` [PATCH v9 1/5] PCI: Hold the rescan mutex when scanning for the first time Bartosz Golaszewski
2024-06-12  8:20 ` [PATCH v9 2/5] PCI/pwrctl: Reuse the OF node for power controlled devices Bartosz Golaszewski
2024-06-12  8:20 ` [PATCH v9 3/5] PCI/pwrctl: Create platform devices for child OF nodes of the port node Bartosz Golaszewski
2024-06-12  8:20 ` [PATCH v9 4/5] PCI/pwrctl: Add PCI power control core code Bartosz Golaszewski
2025-06-17 23:35   ` Bjorn Helgaas [this message]
2025-06-18  7:56     ` Bartosz Golaszewski
2024-06-12  8:20 ` [PATCH v9 5/5] PCI/pwrctl: Add a PCI power control driver for power sequenced devices Bartosz Golaszewski
2024-06-12 11:21 ` [PATCH v9 0/5] PCI/pwrctl: initial implementation and first user Bartosz Golaszewski

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=20250617233539.GA1177120@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=brgl@bgdev.pl \
    --cc=caleb.connolly@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    /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