platform/x86: msi-wmi-platform: Fix spelling mistakes
There were a few instances of typos that lead could to confusion when reading. The following words have been corrected: Binay -> Binary singe -> single chaged -> changed Signed-off-by: Luis Felipe Hernandez <luis.hernandez093@gmail.com> Reviewed-by: Armin Wolf <W_Armin@gmx.de> Acked-by: Randy Dunlap <rdunlap@infradead.org> Link: https://lore.kernel.org/r/20240731001602.259338-1-luis.hernandez093@gmail.com Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
This commit is contained in:
parent
942810c0e8
commit
6e73c49044
1 changed files with 3 additions and 3 deletions
|
@ -130,12 +130,12 @@ data using the `bmfdec <https://github.com/pali/bmfdec>`_ utility:
|
||||||
|
|
||||||
Due to a peculiarity in how Windows handles the ``CreateByteField()`` ACPI operator (errors only
|
Due to a peculiarity in how Windows handles the ``CreateByteField()`` ACPI operator (errors only
|
||||||
happen when a invalid byte field is ultimately accessed), all methods require a 32 byte input
|
happen when a invalid byte field is ultimately accessed), all methods require a 32 byte input
|
||||||
buffer, even if the Binay MOF says otherwise.
|
buffer, even if the Binary MOF says otherwise.
|
||||||
|
|
||||||
The input buffer contains a single byte to select the subfeature to be accessed and 31 bytes of
|
The input buffer contains a single byte to select the subfeature to be accessed and 31 bytes of
|
||||||
input data, the meaning of which depends on the subfeature being accessed.
|
input data, the meaning of which depends on the subfeature being accessed.
|
||||||
|
|
||||||
The output buffer contains a singe byte which signals success or failure (``0x00`` on failure)
|
The output buffer contains a single byte which signals success or failure (``0x00`` on failure)
|
||||||
and 31 bytes of output data, the meaning if which depends on the subfeature being accessed.
|
and 31 bytes of output data, the meaning if which depends on the subfeature being accessed.
|
||||||
|
|
||||||
WMI method Get_EC()
|
WMI method Get_EC()
|
||||||
|
@ -147,7 +147,7 @@ data contains a flag byte and a 28 byte controller firmware version string.
|
||||||
The first 4 bits of the flag byte contain the minor version of the embedded controller interface,
|
The first 4 bits of the flag byte contain the minor version of the embedded controller interface,
|
||||||
with the next 2 bits containing the major version of the embedded controller interface.
|
with the next 2 bits containing the major version of the embedded controller interface.
|
||||||
|
|
||||||
The 7th bit signals if the embedded controller page chaged (exact meaning is unknown), and the
|
The 7th bit signals if the embedded controller page changed (exact meaning is unknown), and the
|
||||||
last bit signals if the platform is a Tigerlake platform.
|
last bit signals if the platform is a Tigerlake platform.
|
||||||
|
|
||||||
The MSI software seems to only use this interface when the last bit is set.
|
The MSI software seems to only use this interface when the last bit is set.
|
||||||
|
|
Loading…
Add table
Reference in a new issue