diff options
| author | Frederic Bonnard <frediz@linux.vnet.ibm.com> | 2016-06-13 11:37:09 +0200 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2016-06-20 15:08:05 +1000 |
| commit | 4c95b5e04e3c4f72e4005574f67cd6e365d3276f (patch) | |
| tree | 60763919c97d73efba7a6ffbb2afa3efa05502d4 /doc/opal-api | |
| parent | 3aeb50189d4d88528c627e099c76b00e28e5c432 (diff) | |
| download | skiboot-4c95b5e04e3c4f72e4005574f67cd6e365d3276f.zip skiboot-4c95b5e04e3c4f72e4005574f67cd6e365d3276f.tar.gz skiboot-4c95b5e04e3c4f72e4005574f67cd6e365d3276f.tar.bz2 | |
Fix for typos
While reviewing the Debian packaging, codespell found those.
Most proposed fixes are based on codespell's default dictionnary.
Signed-off-by: Frederic Bonnard <frediz@linux.vnet.ibm.com>
Reviewed-by: Mukesh Ojha <mukesh02@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc/opal-api')
| -rw-r--r-- | doc/opal-api/opal-pci-phb-mmio-enable-27.txt | 2 | ||||
| -rw-r--r-- | doc/opal-api/opal-rtc-read-3.txt | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/opal-api/opal-pci-phb-mmio-enable-27.txt b/doc/opal-api/opal-pci-phb-mmio-enable-27.txt index c5b08f4..9bff057 100644 --- a/doc/opal-api/opal-pci-phb-mmio-enable-27.txt +++ b/doc/opal-api/opal-pci-phb-mmio-enable-27.txt @@ -13,7 +13,7 @@ used as a starting point for full documentation. The host calls this function to enable or disable PHB decode of the PCI IO and Memory address spaces below that PHB. Window_num selects an mmio window -within that addres space. Enable set to '1' enables the PHB to decode and +within that address space. Enable set to '1' enables the PHB to decode and forward system real addresses to PCI memory, while enable set to '0' disables PHB decode and forwarding for the address range defined in a particular MMIO window. diff --git a/doc/opal-api/opal-rtc-read-3.txt b/doc/opal-api/opal-rtc-read-3.txt index 70f9520..13a0655 100644 --- a/doc/opal-api/opal-rtc-read-3.txt +++ b/doc/opal-api/opal-rtc-read-3.txt @@ -20,10 +20,10 @@ Calling: Since RTC calls can be pretty slow, OPAL_RTC_READ is likely to first return OPAL_BUSY_EVENT, requiring the caller to wait until the OPAL_EVENT_RTC event -has been signaled. Once the event has been signalled, a subsequent -OPAL_RTC_READ call will retreive the time. Since the OPAL_EVENT_RTC event is +has been signaled. Once the event has been signaled, a subsequent +OPAL_RTC_READ call will retrieve the time. Since the OPAL_EVENT_RTC event is used for both reading and writing the RTC, callers must be able to handle -the event being signalled for a concurrent in flight OPAL_RTC_WRITE rather +the event being signaled for a concurrent in flight OPAL_RTC_WRITE rather than this read request. The following code is one way to correctly issue and then wait for a response: |