Fix some issues with ABI files
Subsystems (3)
cover Fix some issues with ABI files
Hi Greg,
All patches in this series are independent each other. This series is based on today's next (next-20210927).
As you know, I've been busy those days adding a new feature for get_abi.pl to identify missing documentation. While doing that, I noticed several issues at the ABI files on "make htmldocs". This series address them, and it is independent from the other patches for get_abi.pl.
Patch 1 is actually a small improvement to get_abi.pl, addressing an issue when there are multiple definitions for the same ABI symbol. While this is not allowed, and produce warnings, there are still 3 occurrences:
./scripts/get_abi.pl validate
Warning: /sys/bus/iio/devices/iio:deviceX/fault_ovuv is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856:14 Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865:0
Warning: /sys/bus/iio/devices/iio:deviceX/in_filter_notch_center_frequency is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865:12 Documentation/ABI/testing/sysfs-bus-iio:1911
Warning: /sys/bus/iio/devices/triggerX/sampling_frequency is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-timer-stm32:92 Documentation/ABI/testing/sysfs-bus-iio:91
Once those got fixed, perhaps a future patch could make get_abi.pl to generate an error causing the compilation to break, if WERROR is defined.
Anyway, it is better to to make the script more reliable anyway, specially since it is just one extra line of code.
Patches 2-7 fix random warnings introduced by new patches.
Regards,
Mauro
Mauro Carvalho Chehab (7):
scripts: get_abi.pl: create a valid ReST with duplicated tags
ABI: sysfs-platform-dell-privacy-wmi: correct ABI entries
ABI: sysfs-platform-dptf: Add tables markup to a table
ABI: configfs-usb-gadget-uac1: fix a broken table
ABI: configfs-usb-gadget-uac2: fix a broken table
ABI: sysfs-devices-removable: make a table valid as ReST markup
ABI: sysfs-platform-intel-pmc: add blank lines to make it valid for
ReST
.../ABI/testing/configfs-usb-gadget-uac1 | 42 +++++++------ .../ABI/testing/configfs-usb-gadget-uac2 | 43 +++++++------ .../ABI/testing/sysfs-devices-removable | 8 ++- .../testing/sysfs-platform-dell-privacy-wmi | 60 ++++++++++++------- Documentation/ABI/testing/sysfs-platform-dptf | 4 ++ .../ABI/testing/sysfs-platform-intel-pmc | 2 + scripts/get_abi.pl | 1 + 7 files changed, 99 insertions(+), 61 deletions(-)
Signature · 1 line
2.31.1
PATCH 1/7 scripts: get_abi.pl: create a valid ReST with duplicated tags
As warned, /sys/bus/iio/devices/iio:deviceX/fault_ovuv is defined 2 times:
Warning: /sys/bus/iio/devices/iio:deviceX/fault_ovuv is defined 2 times: ./Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856:14 ./Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865:0
The logic with joins the two entries is just places the paragraph for the second entry after the previous one. That could cause more warnings, as the produced ReST may become invalid, as in the case of this specific symbol, which ends with a table:
/new_devel/v4l/docs/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856:2: WARNING: Malformed table. No bottom table border found or no blank line after table bottom.
=== =======================================================
'1' The input voltage is negative or greater than VDD.
'0' The input voltage is positive and less than VDD (normal
state).
=== ======================================================= /new_devel/v4l/docs/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856:2: WARNING: Blank line required after table.
Address it by adding two blank lines before joining duplicated symbols.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
scripts/get_abi.pl | 1 + 1 file changed, 1 insertion(+)
scripts/get_abi.pl +1 -0
@@ -180,6 +180,7 @@ sub parse_abi { $data{$what}->{file} = $name; $data{$what}->{filepath} = $file; } else { + $data{$what}->{description} .= "\n\n" if (defined($data{$what}->{description})); if ($name ne $data{$what}->{file}) { $data{$what}->{file} .= " " . $name; $data{$what}->{filepath} .= " " . $file;
Signature · 1 line
2.31.1
PATCH 2/7 ABI: sysfs-platform-dell-privacy-wmi: correct ABI entries
In reply to Mauro Carvalho ChehabAs described at Documentation/ABI/README doesn't contain an
Attribute: field.
The way sysfs ABI is supposed to work is that each different attribute would have a separate file. So, the right way to map this would be like:
/sys/.../dell_privacy_supported_type/mic_mute /sys/.../dell_privacy_supported_type/camera_shutter
/sys/.../dell_privacy_current_state/mic_mute /sys/.../dell_privacy_current_state/camera_shutter
However, it seems to late to fix that, as this was merged already on Kernel 5.13, and a change right now would be a regression.
So, instead, let's at least fix the entry to match the expected format.
While here, fix the format of the contact, which is not a valid e-mail URL.
This should also fix the current warnings produced when building the docs:
Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi:35: WARNING: Unexpected indentation. Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi:2: WARNING: Unexpected indentation.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
.../testing/sysfs-platform-dell-privacy-wmi | 60 ++++++++++++------- 1 file changed, 38 insertions(+), 22 deletions(-)
Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi +38 -22
@@ -1,55 +1,71 @@ What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type Date: Apr 2021 KernelVersion: 5.13 -Contact: "[email protected]>" +Contact: "<[email protected]>" Description: Display which dell hardware level privacy devices are supported “Dell Privacy” is a set of HW, FW, and SW features to enhance Dell’s commitment to platform privacy for MIC, Camera, and ePrivacy screens. The supported hardware privacy devices are: -Attributes: - Microphone Mute: + + Attributes: + Microphone Mute: Identifies the local microphone can be muted by hardware, no applications is available to capture system mic sound - Camera Shutter: + Camera Shutter: Identifies camera shutter controlled by hardware, which is a micromechanical shutter assembly that is built onto the camera module to block capturing images from outside the laptop - supported: + Values: + + supported: The privacy device is supported by this system - unsupported: + unsupported: The privacy device is not supported on this system - For example to check which privacy devices are supported: + For example to check which privacy devices are supported:: - # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type - [Microphone Mute] [supported] - [Camera Shutter] [supported] - [ePrivacy Screen] [unsupported] + # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type + [Microphone Mute] [supported] + [Camera Shutter] [supported] + [ePrivacy Screen] [unsupported] What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state Date: Apr 2021 KernelVersion: 5.13 -Contact: "[email protected]>" +Contact: "<[email protected]>" Description: Allow user space to check current dell privacy device state. Describes the Device State class exposed by BIOS which can be consumed by various applications interested in knowing the Privacy feature capabilities -Attributes: - muted: - Identifies the privacy device is turned off and cannot send stream to OS applications - unmuted: - Identifies the privacy device is turned on ,audio or camera driver can get - stream from mic and camera module to OS applications + Attributes: + Microphone: + Identifies the local microphone can be muted by hardware, no applications + is available to capture system mic sound - For example to check all supported current privacy device states: + Camera Shutter: + Identifies camera shutter controlled by hardware, which is a micromechanical + shutter assembly that is built onto the camera module to block capturing images + from outside the laptop - # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state - [Microphone] [unmuted] - [Camera Shutter] [unmuted] + Values: + muted: + Identifies the privacy device is turned off + and cannot send stream to OS applications + + unmuted: + Identifies the privacy device is turned on, + audio or camera driver can get stream from mic + and camera module to OS applications + + For example to check all supported current privacy device states:: + + # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state + [Microphone] [unmuted] + [Camera Shutter] [unmuted]
Signature · 1 line
2.31.1
Re: [PATCH 2/7] ABI: sysfs-platform-dell-privacy-wmi: correct ABI entries
Hi,
Quoted 22 lines · Mauro Carvalho Chehab
As described at
Documentation/ABI/READMEdoesn't contain an
Attribute: field.The way sysfs ABI is supposed to work is that each different attribute would have a separate file. So, the right way to map this would be like:
/sys/.../dell_privacy_supported_type/mic_mute/sys/.../dell_privacy_supported_type/camera_shutter
/sys/.../dell_privacy_current_state/mic_mute/sys/.../dell_privacy_current_state/camera_shutterHowever, it seems to late to fix that, as this was merged already on Kernel 5.13, and a change right now would be a regression.
So, instead, let's at least fix the entry to match the expected format.
While here, fix the format of the contact, which is not a valid e-mail URL.
Quoted 8 lines
This should also fix the current warnings produced when building the docs:
Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi:35: WARNING: Unexpected indentation.Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi:2: WARNING: Unexpected indentation.Fixes 8af9fa37b8a3 ("platform/x86: dell-privacy: Add support for Dell hardware privacy")Signed-off-by Mauro Carvalho Chehab <[email protected]>
Thank you for your patch, I've applied this patch to my review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be added to the platform-drivers-x86/for-next branch and eventually will be included in the pdx86 pull-request to Linus for the next merge-window.
Regards,
Hans
Quoted 106 lines
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
.../testing/sysfs-platform-dell-privacy-wmi | 60 ++++++++++++------- 1 file changed, 38 insertions(+), 22 deletions(-)Documentation/ABI/testing/sysfs-platform-dell-privacy-wmi +38
-22@@ -1,55 +1,71 @@ What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type Date: Apr 2021 KernelVersion: 5.13 -Contact: "[email protected]>" +Contact: "<[email protected]>" Description: Display which dell hardware level privacy devices are supported “Dell Privacy” is a set of HW, FW, and SW features to enhance Dell’s commitment to platform privacy for MIC, Camera, and ePrivacy screens. The supported hardware privacy devices are: -Attributes: - Microphone Mute: + + Attributes: + Microphone Mute: Identifies the local microphone can be muted by hardware, no applications is available to capture system mic sound - Camera Shutter: + Camera Shutter: Identifies camera shutter controlled by hardware, which is a micromechanical shutter assembly that is built onto the camera module to block capturing images from outside the laptop - supported: + Values: + + supported: The privacy device is supported by this system - unsupported: + unsupported: The privacy device is not supported on this system - For example to check which privacy devices are supported: + For example to check which privacy devices are supported:: - # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type - [Microphone Mute] [supported] - [Camera Shutter] [supported] - [ePrivacy Screen] [unsupported] + # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type + [Microphone Mute] [supported] + [Camera Shutter] [supported] + [ePrivacy Screen] [unsupported] What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state Date: Apr 2021 KernelVersion: 5.13 -Contact: "[email protected]>" +Contact: "<[email protected]>" Description: Allow user space to check current dell privacy device state. Describes the Device State class exposed by BIOS which can be consumed by various applications interested in knowing the Privacy feature capabilities -Attributes: - muted: - Identifies the privacy device is turned off and cannot send stream to OS applications - unmuted: - Identifies the privacy device is turned on ,audio or camera driver can get - stream from mic and camera module to OS applications + Attributes: + Microphone: + Identifies the local microphone can be muted by hardware, no applications + is available to capture system mic sound - For example to check all supported current privacy device states: + Camera Shutter: + Identifies camera shutter controlled by hardware, which is a micromechanical + shutter assembly that is built onto the camera module to block capturing images + from outside the laptop - # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state - [Microphone] [unmuted] - [Camera Shutter] [unmuted] + Values: + muted: + Identifies the privacy device is turned off + and cannot send stream to OS applications + + unmuted: + Identifies the privacy device is turned on, + audio or camera driver can get stream from mic + and camera module to OS applications + + For example to check all supported current privacy device states:: + + # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state + [Microphone] [unmuted] + [Camera Shutter] [unmuted]
PATCH 3/7 ABI: sysfs-platform-dptf: Add tables markup to a table
In reply to Mauro Carvalho ChehabSolve those warnings:
Documentation/ABI/testing/sysfs-platform-dptf:130: WARNING: Unexpected indentation. Documentation/ABI/testing/sysfs-platform-dptf:130: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/ABI/testing/sysfs-platform-dptf:130: WARNING: Definition list ends without a blank line; unexpected unindent.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
Documentation/ABI/testing/sysfs-platform-dptf | 4 ++++ 1 file changed, 4 insertions(+)
Documentation/ABI/testing/sysfs-platform-dptf +4 -0
@@ -133,7 +133,10 @@ Contact: [email protected] Description: (RO) Presents SSC (spread spectrum clock) information for EMI (Electro magnetic interference) control. This is a bit mask. + + ======= ========================================== Bits Description + ======= ========================================== [7:0] Sets clock spectrum spread percentage: 0x00=0.2% , 0x3F=10% 1 LSB = 0.1% increase in spread (for
@@ -151,3 +154,4 @@ Description: [10] 0: No white noise. 1: Add white noise to spread waveform [11] When 1, future writes are ignored. + ======= ==========================================
Signature · 1 line
2.31.1
PATCH 4/7 ABI: configfs-usb-gadget-uac1: fix a broken table
In reply to Mauro Carvalho ChehabChangeset 0356e6283c71 ("usb: gadget: f_uac1: add volume and mute support") added some new elements to the table but didn't care enough to actually adjust the columns, causing the output to be broken as warned by Sphinx when producing the documentation.
Readjust it for it to be a valid ReST table.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
.../ABI/testing/configfs-usb-gadget-uac1 | 42 +++++++++++-------- 1 file changed, 24 insertions(+), 18 deletions(-)
Documentation/ABI/testing/configfs-usb-gadget-uac1 +24 -18
@@ -4,23 +4,29 @@ KernelVersion: 4.14 Description: The attributes: - ========== =================================== - c_chmask capture channel mask - c_srate capture sampling rate - c_ssize capture sample size (bytes) - c_mute_present capture mute control enable + ===================== ======================================= + c_chmask capture channel mask + c_srate capture sampling rate + c_ssize capture sample size (bytes) + c_mute_present capture mute control enable c_volume_present capture volume control enable - c_volume_min capture volume control min value (in 1/256 dB) - c_volume_max capture volume control max value (in 1/256 dB) - c_volume_res capture volume control resolution (in 1/256 dB) - p_chmask playback channel mask - p_srate playback sampling rate - p_ssize playback sample size (bytes) - p_mute_present playback mute control enable + c_volume_min capture volume control min value + (in 1/256 dB) + c_volume_max capture volume control max value + (in 1/256 dB) + c_volume_res capture volume control resolution + (in 1/256 dB) + p_chmask playback channel mask + p_srate playback sampling rate + p_ssize playback sample size (bytes) + p_mute_present playback mute control enable p_volume_present playback volume control enable - p_volume_min playback volume control min value (in 1/256 dB) - p_volume_max playback volume control max value (in 1/256 dB) - p_volume_res playback volume control resolution (in 1/256 dB) - req_number the number of pre-allocated request - for both capture and playback - ========== =================================== + p_volume_min playback volume control min value + (in 1/256 dB) + p_volume_max playback volume control max value + (in 1/256 dB) + p_volume_res playback volume control resolution + (in 1/256 dB) + req_number the number of pre-allocated request + for both capture and playback + ===================== =======================================
Signature · 1 line
2.31.1
PATCH 5/7 ABI: configfs-usb-gadget-uac2: fix a broken table
In reply to Mauro Carvalho ChehabChangeset af6cbe09920 ("usb: gadget: f_uac2: add volume and mute support") added some new elements to the table but didn't care enough to actually adjust the columns, causing the output to be broken as warned by Sphinx when producing the documentation.
Readjust it for it to be a valid ReST table.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
.../ABI/testing/configfs-usb-gadget-uac2 | 43 +++++++++++-------- 1 file changed, 25 insertions(+), 18 deletions(-)
Documentation/ABI/testing/configfs-usb-gadget-uac2 +25 -18
@@ -4,23 +4,30 @@ KernelVersion: 3.18 Description: The attributes: - ========= ============================ - c_chmask capture channel mask - c_srate capture sampling rate - c_ssize capture sample size (bytes) - c_sync capture synchronization type (async/adaptive) - c_mute_present capture mute control enable + ===================== ======================================= + c_chmask capture channel mask + c_srate capture sampling rate + c_ssize capture sample size (bytes) + c_sync capture synchronization type + (async/adaptive) + c_mute_present capture mute control enable c_volume_present capture volume control enable - c_volume_min capture volume control min value (in 1/256 dB) - c_volume_max capture volume control max value (in 1/256 dB) - c_volume_res capture volume control resolution (in 1/256 dB) - fb_max maximum extra bandwidth in async mode - p_chmask playback channel mask - p_srate playback sampling rate - p_ssize playback sample size (bytes) - p_mute_present playback mute control enable + c_volume_min capture volume control min value + (in 1/256 dB) + c_volume_max capture volume control max value + (in 1/256 dB) + c_volume_res capture volume control resolution + (in 1/256 dB) + fb_max maximum extra bandwidth in async mode + p_chmask playback channel mask + p_srate playback sampling rate + p_ssize playback sample size (bytes) + p_mute_present playback mute control enable p_volume_present playback volume control enable - p_volume_min playback volume control min value (in 1/256 dB) - p_volume_max playback volume control max value (in 1/256 dB) - p_volume_res playback volume control resolution (in 1/256 dB) - ========= ============================ + p_volume_min playback volume control min value + (in 1/256 dB) + p_volume_max playback volume control max value + (in 1/256 dB) + p_volume_res playback volume control resolution + (in 1/256 dB) + ===================== =======================================
Signature · 1 line
2.31.1
PATCH 6/7 ABI: sysfs-devices-removable: make a table valid as ReST markup
In reply to Mauro Carvalho ChehabChangeset 70f400d4d957 ("driver core: Move the "removable" attribute from USB to core") added a table to the file, but not using a valid ReST format.
Change it to avoid build issues when producing documentation with "make htmldocs".
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
Documentation/ABI/testing/sysfs-devices-removable | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
Documentation/ABI/testing/sysfs-devices-removable +5 -3
@@ -7,10 +7,12 @@ Description: bus / platform-specific way. This attribute is only present for devices that can support determining such information: - "removable": device can be removed from the platform by the user - "fixed": device is fixed to the platform / cannot be removed + =========== =================================================== + "removable" device can be removed from the platform by the user + "fixed" device is fixed to the platform / cannot be removed by the user. - "unknown": The information is unavailable / cannot be deduced. + "unknown" The information is unavailable / cannot be deduced. + =========== =================================================== Currently this is only supported by USB (which infers the information from a combination of hub descriptor bits and
Signature · 1 line
2.31.1
PATCH 7/7 ABI: sysfs-platform-intel-pmc: add blank lines to make it valid for ReST
In reply to Mauro Carvalho ChehabThe ReST format requires blank lines before/after identation changes, for it to properly detect lists.
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
Documentation/ABI/testing/sysfs-platform-intel-pmc | 2 ++ 1 file changed, 2 insertions(+)
Documentation/ABI/testing/sysfs-platform-intel-pmc +2 -0
@@ -11,8 +11,10 @@ Description: to take effect. Display global reset setting bits for PMC. + * bit 31 - global reset is locked * bit 20 - global reset is set + Writing bit 20 value to the etr3 will induce a platform "global reset" upon consequent platform reset, in case the register is not locked.
Signature · 1 line
2.31.1
RE: [PATCH 7/7] ABI: sysfs-platform-intel-pmc: add blank lines to make it valid for ReST
Quoted 7 lines
The ReST format requires blank lines before/after identation changes, for it to properly detect lists.
Fixes ee7abc105e2b ("platform/x86: intel_pmc_core: export platform globalreset bits via etr3 sysfs file")
Signed-off-by Mauro Carvalho Chehab <[email protected]>
Ack.
Quoted 27 lines
---
See [PATCH 0/7] at:
https://lore.kernel.org/all/[email protected]
rg/T/#tDocumentation/ABI/testing/sysfs-platform-intel-pmc | 2 ++ 1 file changed, 2 insertions(+)Documentation/ABI/testing/sysfs-platform-intel-pmc +2
-1@@ -11,8 +11,10 @@ Description: to take effect. Display global reset setting bits for PMC. + * bit 31 - global reset is locked * bit 20 - global reset is set + Writing bit 20 value to the etr3 will induce a platform "global reset" upon consequent platform reset, in case the register is not locked. --2.31.1
Re: [PATCH 7/7] ABI: sysfs-platform-intel-pmc: add blank lines to make it valid for ReST
In reply to Mauro Carvalho ChehabHi,
Quoted 5 lines · Mauro Carvalho Chehab
The ReST format requires blank lines before/after identation changes, for it to properly detect lists.
Fixes ee7abc105e2b ("platform/x86: intel_pmc_core: export platform global reset bits via etr3 sysfs file")Signed-off-by Mauro Carvalho Chehab <[email protected]>
Thank you for your patch, I've applied this patch to my review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be added to the platform-drivers-x86/for-next branch and eventually will be included in the pdx86 pull-request to Linus for the next merge-window.
Regards,
Hans
Quoted 23 lines
---
See [PATCH 0/7] at: https://lore.kernel.org/all/[email protected]/T/#t
Documentation/ABI/testing/sysfs-platform-intel-pmc | 2 ++ 1 file changed, 2 insertions(+)Documentation/ABI/testing/sysfs-platform-intel-pmc +2
-0@@ -11,8 +11,10 @@ Description: to take effect. Display global reset setting bits for PMC. + * bit 31 - global reset is locked * bit 20 - global reset is set + Writing bit 20 value to the etr3 will induce a platform "global reset" upon consequent platform reset, in case the register is not locked.