On 11/1/2022 3:34 PM, Sohil Mehta wrote:
> On 10/21/2022 1:34 PM, Jithu Joseph wrote:
>> -What: /sys/devices/virtual/misc/intel_ifs_<N>/reload
>> -Date: April 21 2022
>> -KernelVersion: 5.19
>> +What: /sys/devices/virtual/misc/intel_ifs_<N>/current_batch
>> +Date: Sept 30 2022
>> +KernelVersion: 6.2
>> Contact: "Jithu Joseph" <jithu.joseph@xxxxxxxxx>
>> -Description: Write "1" (or "y" or "Y") to reload the IFS image from
>> - /lib/firmware/intel/ifs/ff-mm-ss.scan.
>> +Description: Write a number less than or equal to 0xff to load an IFS test image.
>> + The number written treated as the 2 digit suffix in the following file name:
>> + /lib/firmware/intel/ifs_<N>/ff-mm-ss-02x.scan
>> + Reading the file will provide the suffix of the currently loaded IFS test image.
>
> A few places in the code use the following string: family-model-stepping-02x.{testname}
>
> Does that mean that the in future there might be other extensions apart from .scan?
yes as when when support for additional tests are added
>
> If so, current_batch would let the user identify the 2 digit suffix but how would they identify which testname is current loaded?
The testname would be inferred based the sysfs file context (the<N> in /sys/devices/virtual/misc/intel_ifs_<N>/current_batch) from which the operation is triggered.
Meaning if the user writes to /sys/devices/virtual/misc/intel_ifs_0/current_batch it would look for ff-mm-ss.scan and if they write to
/sys/devices/virtual/misc/intel_ifs_2/current_batch it would look for ff-mm-ss.<test_type_2>
Jithu
