[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <397249ba-eefc-ff44-5391-90a81a42ce45@intel.com>
Date: Thu, 3 Nov 2022 00:49:07 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: "Joseph, Jithu" <jithu.joseph@...el.com>
CC: <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<gregkh@...uxfoundation.org>, <ashok.raj@...el.com>,
<tony.luck@...el.com>, <linux-kernel@...r.kernel.org>,
<platform-driver-x86@...r.kernel.org>, <patches@...ts.linux.dev>,
<ravi.v.shankar@...el.com>, <thiago.macieira@...el.com>,
<athenas.jimenez.gonzalez@...el.com>, <hdegoede@...hat.com>,
<markgross@...nel.org>
Subject: Re: [PATCH 13/14] Documentation/ABI: Update IFS ABI doc
On 11/2/2022 3:10 PM, Joseph, Jithu wrote:
>
> There is a mapping based on the device number, for e.g if the user tries to use the below sysfs file for loading
> /sys/devices/virtual/misc/intel_ifs_<N>/current_batch
>
> The driver will look for the below test image for loading
> /lib/firmware/intel/ifs_<N>/ff-mm-ss-02x.<test_type>
>
> The number<N> is same in both the above path.
I guess that is OK. Adding the test name to the device path could
potentially make the interface more restrictive.
Sohil
Powered by blists - more mailing lists