public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: Anisse Astier <anisse@astier.eu>
Cc: <ashok.raj.linux@gmail.com>, <hdegoede@redhat.com>,
	<ilpo.jarvinen@linux.intel.com>, <linux-kernel@vger.kernel.org>,
	<platform-driver-x86@vger.kernel.org>, <tony.luck@intel.com>,
	"Joseph, Jithu" <jithu.joseph@intel.com>
Subject: Re: [PATCH v2] platform/x86/intel/ifs: Update documentation to match current availability of firmware images
Date: Tue, 21 Jan 2025 12:06:31 -0800	[thread overview]
Message-ID: <15f502ef-ed41-4b9a-90fe-a7af4591f0db@intel.com> (raw)
In-Reply-To: <20250121183930.182315-1-anisse@astier.eu>



On 1/21/2025 10:39 AM, Anisse Astier wrote:
> Firmware images necessary for certain tests in the In-field scan[1] test
> suite are not available at the moment[2], and require having access to
> at least an Intel customer account[3].
> 
> Update documentation to match current state, it can be updated again
> when the images are finally published.
> 
> [1] https://www.intel.com/content/www/us/en/support/articles/000099537/processors/intel-xeon-processors.html
> [2] https://cdrdv2.intel.com/v1/dl/getContent/826383?explicitVersion=true
> [3] https://www.intel.com/content/www/us/en/secure/design/confidential/software-kits/kit-details.html?kitId=815180
> 
> Signed-off-by: Anisse Astier <anisse@astier.eu>
> ---
> Changes since v1:
>  - update commit message to clarify that only some tests need the firmware
>    images, thanks Jithu for the suggestion!
> 
> Regards,
> 
> Anisse
> ---
>  drivers/platform/x86/intel/ifs/ifs.h | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)

Looks good to me.

Reviewed-by: Jithu Joseph <jithu.joseph@intel.com>

> 
> diff --git a/drivers/platform/x86/intel/ifs/ifs.h b/drivers/platform/x86/intel/ifs/ifs.h
> index 5c3c0dfa1bf8..9a7ad9cc9d08 100644
> --- a/drivers/platform/x86/intel/ifs/ifs.h
> +++ b/drivers/platform/x86/intel/ifs/ifs.h
> @@ -23,9 +23,11 @@
>   * IFS Image
>   * ---------
>   *
> - * Intel provides a firmware file containing the scan tests via
> - * github [#f1]_.  Similar to microcode there is a separate file for each
> - * family-model-stepping. IFS Images are not applicable for some test types.
> + * As of early 2025, Intel provides the firmware files containing the scan tests
> + * to select customers [#f1]_. When this driver was merged in 2022, it was
> + * announced that firmware files would be available via github [#f2]_. Similar
> + * to microcode there is a separate file for each family-model-stepping. IFS
> + * Images are not applicable for some test types.
>   * Wherever applicable the sysfs directory would provide a "current_batch" file
>   * (see below) for loading the image.
>   *
> @@ -125,7 +127,8 @@
>   * 2) Hardware allows for some number of cores to be tested in parallel.
>   * The driver does not make use of this, it only tests one core at a time.
>   *
> - * .. [#f1] https://github.com/intel/TBD
> + * .. [#f1] https://www.intel.com/content/www/us/en/support/articles/000099537/processors/intel-xeon-processors.html
> + * .. [#f2] https://github.com/intel/TBD
>   *
>   *
>   * Structural Based Functional Test at Field (SBAF):

Thanks
Jithu

  reply	other threads:[~2025-01-21 20:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 19:43 [PATCH] platform/x86/intel/ifs: Update documentation to match current availability of firmware images Anisse Astier
2025-01-02 21:40 ` Joseph, Jithu
2025-01-20 20:20   ` Anisse Astier
2025-01-20 20:47     ` Joseph, Jithu
2025-01-20 20:59 ` Joseph, Jithu
2025-01-21 18:39   ` [PATCH v2] " Anisse Astier
2025-01-21 20:06     ` Joseph, Jithu [this message]
2025-01-22 13:42     ` Ilpo Järvinen
2025-01-31 21:00       ` Joseph, Jithu

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=15f502ef-ed41-4b9a-90fe-a7af4591f0db@intel.com \
    --to=jithu.joseph@intel.com \
    --cc=anisse@astier.eu \
    --cc=ashok.raj.linux@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tony.luck@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