Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f4baccde authored by Tamara Diaconita's avatar Tamara Diaconita Committed by Jonathan Corbet
Browse files

Documentation: acpi: Fix typos 



Fix typos in acpi directory to make documentation grammatically correct.

Signed-off-by: default avatarTamara Diaconita <diaconita.tamara@gmail.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 9f02a486

Documentation/acpi/aml-debugger.txt

+1 −1
Original line number Diff line number Diff line
@@ -15,7 +15,7 @@ kernel. 
   CONFIG_ACPI_DEBUGGER=y

   CONFIG_ACPI_DEBUGGER_USER=m



   The userspace utlities can be built from the kernel source tree using

   The userspace utilities can be built from the kernel source tree using

   the following commands:



   $ cd tools

Documentation/acpi/enumeration.txt

+3 −3
Original line number Diff line number Diff line
@@ -367,10 +367,10 @@ resulting child platform device. 


Device Tree namespace link device ID

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Device Tree protocol uses device indentification based on the "compatible"

The Device Tree protocol uses device identification based on the "compatible"

property whose value is a string or an array of strings recognized as device

identifiers by drivers and the driver core.  The set of all those strings may be

regarded as a device indentification namespace analogous to the ACPI/PNP device

regarded as a device identification namespace analogous to the ACPI/PNP device

ID namespace.  Consequently, in principle it should not be necessary to allocate

a new (and arguably redundant) ACPI/PNP device ID for a devices with an existing

identification string in the Device Tree (DT) namespace, especially if that ID
@@ -381,7 +381,7 @@ In ACPI, the device identification object called _CID (Compatible ID) is used to 
list the IDs of devices the given one is compatible with, but those IDs must

belong to one of the namespaces prescribed by the ACPI specification (see

Section 6.1.2 of ACPI 6.0 for details) and the DT namespace is not one of them.

Moreover, the specification mandates that either a _HID or an _ADR identificaion

Moreover, the specification mandates that either a _HID or an _ADR identification

object be present for all ACPI objects representing devices (Section 6.1 of ACPI

6.0).  For non-enumerable bus types that object must be _HID and its value must

be a device ID from one of the namespaces prescribed by the specification too.

Documentation/acpi/linuxized-acpica.txt

+3 −3
Original line number Diff line number Diff line
@@ -110,7 +110,7 @@ upstream. 
   Linux patches.  The patches generated by this process are referred to as

   "linuxized ACPICA patches".  The release process is carried out on a local

   copy the ACPICA git repository.  Each commit in the monthly release is

   converted into a linuxized ACPICA patch.  Together, they form the montly

   converted into a linuxized ACPICA patch.  Together, they form the monthly

   ACPICA release patchset for the Linux ACPI community.  This process is

   illustrated in the following figure:
@@ -195,12 +195,12 @@ upstream. 
      release utilities (please refer to Section 4 below for the details).

   3. Linux specific features - Sometimes it's impossible to use the

      current ACPICA APIs to implement features required by the Linux kernel,

      so Linux developers occasionaly have to change ACPICA code directly.

      so Linux developers occasionally have to change ACPICA code directly.

      Those changes may not be acceptable by ACPICA upstream and in such cases

      they are left as committed ACPICA divergences unless the ACPICA side can

      implement new mechanisms as replacements for them.

   4. ACPICA release fixups - ACPICA only tests commits using a set of the

      user space simulation utilies, thus the linuxized ACPICA patches may

      user space simulation utilities, thus the linuxized ACPICA patches may

      break the Linux kernel, leaving us build/boot failures.  In order to

      avoid breaking Linux bisection, fixes are applied directly to the

      linuxized ACPICA patches during the release process.  When the release