mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	 srinivas.pandruvada@linux.intel.com,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	tony.luck@intel.com,  xi.pardee@linux.intel.com,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH V2 03/15] platform/x86/intel/vsec: Create wrapper to walk PCI config space
Date: Mon, 30 Jun 2025 15:02:33 +0300 (EEST)	[thread overview]
Message-ID: <1b2fc196-fc27-f782-e7d6-86b72d950fe7@linux.intel.com> (raw)
In-Reply-To: <20250617014041.2861032-4-david.e.box@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2798 bytes --]

On Mon, 16 Jun 2025, David E. Box wrote:

> Combine three PCI config space walkers — intel_vsec_walk_dvsec(),
> intel_vsec_walk_vsec(), and intel_vsec_walk_header() — into a new wrapper
> function, intel_vsec_feature_walk().  This refactoring simplifies the probe
> logic and lays the groundwork for future patches that will loop over these
> calls. No functional changes.
> 
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> ---
> 
> Changes in v2:
>   - No changes
> 
>  drivers/platform/x86/intel/vsec.c | 31 ++++++++++++++++++++++---------
>  1 file changed, 22 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/platform/x86/intel/vsec.c b/drivers/platform/x86/intel/vsec.c
> index 59fb6568a855..f01651f498ca 100644
> --- a/drivers/platform/x86/intel/vsec.c
> +++ b/drivers/platform/x86/intel/vsec.c
> @@ -349,6 +349,27 @@ int intel_vsec_register(struct pci_dev *pdev,
>  }
>  EXPORT_SYMBOL_NS_GPL(intel_vsec_register, "INTEL_VSEC");
>  
> +static void intel_vsec_feature_walk(struct pci_dev *pdev, bool *have_devices,
> +				    struct intel_vsec_platform_info *info)
> +{
> +	/*
> +	 * Both DVSEC and VSEC capabilities can exist on the same device,
> +	 * so both intel_vsec_walk_dvsec() and intel_vsec_walk_vsec() must be
> +	 * called independently. Additionally, intel_vsec_walk_header() is
> +	 * needed for devices that do not have VSEC/DVSEC but provide the
> +	 * information via device_data.
> +	 */
> +	if (intel_vsec_walk_dvsec(pdev, info))
> +		*have_devices = true;
> +
> +	if (intel_vsec_walk_vsec(pdev, info))
> +		*have_devices = true;
> +
> +	if (info && (info->quirks & VSEC_QUIRK_NO_DVSEC) &&
> +	    intel_vsec_walk_header(pdev, info))
> +		*have_devices = true;

Should have_devices be named something more specific in this function or 
perhaps be simply the return value for this function?

IMO, the name of the function could be better too, having "walk" in the 
name feels unnecessary internal detail compared to what this function 
tries to do on a more abstract level.

> +}
> +
>  static int intel_vsec_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>  {
>  	struct intel_vsec_platform_info *info;
> @@ -372,15 +393,7 @@ static int intel_vsec_pci_probe(struct pci_dev *pdev, const struct pci_device_id
>  	priv->info = info;
>  	pci_set_drvdata(pdev, priv);
>  
> -	if (intel_vsec_walk_dvsec(pdev, info))
> -		have_devices = true;
> -
> -	if (intel_vsec_walk_vsec(pdev, info))
> -		have_devices = true;
> -
> -	if (info && (info->quirks & VSEC_QUIRK_NO_DVSEC) &&
> -	    intel_vsec_walk_header(pdev, info))
> -		have_devices = true;
> +	intel_vsec_feature_walk(pdev, &have_devices, info);
>  
>  	if (!have_devices)
>  		return -ENODEV;
> 

-- 
 i.

  reply	other threads:[~2025-06-30 12:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  1:40 [PATCH V2 00/15] Intel VSEC/PMT: Introduce Discovery Driver David E. Box
2025-06-17  1:40 ` [PATCH V2 01/15] MAINTAINERS: Add link to documentation of Intel PMT ABI David E. Box
2025-06-17  1:40 ` [PATCH V2 02/15] platform/x86/intel/vsec: Add private data for per-device data David E. Box
2025-06-17  1:40 ` [PATCH V2 03/15] platform/x86/intel/vsec: Create wrapper to walk PCI config space David E. Box
2025-06-30 12:02   ` Ilpo Järvinen [this message]
2025-06-30 20:51     ` David Box
2025-06-17  1:40 ` [PATCH V2 04/15] platform/x86/intel/vsec: Add device links to enforce dependencies David E. Box
2025-06-30 12:06   ` Ilpo Järvinen
2025-06-30 20:47     ` David Box
2025-06-17  1:40 ` [PATCH V2 05/15] platform/x86/intel/vsec: Skip absent features during initialization David E. Box
2025-06-17  1:40 ` [PATCH V2 06/15] platform/x86/intel/vsec: Skip driverless features David E. Box
2025-06-17  1:40 ` [PATCH V2 07/15] platform/x86/intel/vsec: Add new Discovery feature David E. Box
2025-06-17  1:40 ` [PATCH V2 08/15] platform/x86/intel/pmt: Add PMT Discovery driver David E. Box
2025-06-17  1:40 ` [PATCH V2 09/15] docs: Add ABI documentation for intel_pmt feature directories David E. Box
2025-06-17  1:40 ` [PATCH V2 10/15] platform/x86/intel/tpmi: Relocate platform info to intel_vsec.h David E. Box
2025-06-17  1:40 ` [PATCH V2 11/15] platform/x86/intel/vsec: Set OOBMSM to CPU mapping David E. Box
2025-06-30 11:55   ` Ilpo Järvinen
2025-06-30 20:56     ` David Box
2025-06-17  1:40 ` [PATCH V2 12/15] platform/x86/intel/tpmi: Get OOBMSM CPU mapping from TPMI David E. Box
2025-06-17  1:40 ` [PATCH V2 13/15] platform/x86/intel/pmt/discovery: Get telemetry attributes David E. Box
2025-06-17  1:40 ` [PATCH V2] platform/x86/intel/pmt/telemetry: Add API to retrieve telemetry regions by feature David E. Box
2025-06-30 12:08   ` Ilpo Järvinen
2025-06-17  1:40 ` [PATCH V2 15/15] platform/x86/intel/pmt: KUNIT test for PMT Enhanced Discovery API David E. Box
2025-06-25 20:22 ` [PATCH V2 00/15] Intel VSEC/PMT: Introduce Discovery Driver Luck, Tony
2025-06-27 19:08   ` David Box

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=1b2fc196-fc27-f782-e7d6-86b72d950fe7@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=xi.pardee@linux.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

all inboxes | Powered by JetHome®