arch to drivers/intel: Fix misspellings & capitalization issues
Signed-off-by: Martin Roth <gaumless@gmail.com>
Change-Id: Ic52f01d1d5d86334e0fd639b968b5eed43a35f1d
Reviewed-on: https://review.coreboot.org/c/coreboot/+/77633
Reviewed-by: Eric Lai <eric_lai@quanta.corp-partner.google.com>
Reviewed-by: Elyes Haouas <ehaouas@noos.fr>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
diff --git a/src/drivers/i2c/rtd2132/chip.h b/src/drivers/i2c/rtd2132/chip.h
index b65182f..50ea7d5 100644
--- a/src/drivers/i2c/rtd2132/chip.h
+++ b/src/drivers/i2c/rtd2132/chip.h
@@ -11,7 +11,7 @@
u16 t4; /* Delay from backlight output disable to PWM output disable. */
u16 t5; /* Delay from PWM output disable to LVDS output disable. */
u16 t6; /* Delay from LVDS output disable to panel Vcc disable. */
- u16 t7; /* Delay between tweo panel power on/off sequence. */
+ u16 t7; /* Delay between two panel power on/off sequence. */
/*
* LVDS swap.
diff --git a/src/drivers/i2c/tpm/cr50.c b/src/drivers/i2c/tpm/cr50.c
index 7c0c488..ff1b3a0 100644
--- a/src/drivers/i2c/tpm/cr50.c
+++ b/src/drivers/i2c/tpm/cr50.c
@@ -123,7 +123,7 @@
}
/*
- * Cr50 processes reset requests asynchronously and consceivably could be busy
+ * Cr50 processes reset requests asynchronously and conceivably could be busy
* executing a long command and not reacting to the reset pulse for a while.
*
* This function will make sure that the AP does not proceed with boot until
diff --git a/src/drivers/i2c/ww_ring/ww_ring.c b/src/drivers/i2c/ww_ring/ww_ring.c
index 98c162b..3956a19 100644
--- a/src/drivers/i2c/ww_ring/ww_ring.c
+++ b/src/drivers/i2c/ww_ring/ww_ring.c
@@ -310,7 +310,7 @@
}
/*
- * Signal Depthcharge that the controller has been initiazed by
+ * Signal Depthcharge that the controller has been initialized by
* coreboot.
*/
data = LP55231_VARIABLE_COOKIE;
@@ -340,7 +340,7 @@
/*
* First stop all running programs to avoid
- * inerference between the controllers.
+ * interference between the controllers.
*/
for (j = 0; j < WW_RING_NUM_LED_CONTROLLERS; j++) {
if (!lp55231s[j].dev_addr)
diff --git a/src/drivers/i2c/ww_ring/ww_ring.h b/src/drivers/i2c/ww_ring/ww_ring.h
index db724d3..b43b9b8 100644
--- a/src/drivers/i2c/ww_ring/ww_ring.h
+++ b/src/drivers/i2c/ww_ring/ww_ring.h
@@ -5,12 +5,12 @@
/*
* Different types of display patterns to be shown by the LED ring while
- * contrlled by coreboot.
+ * controlled by coreboot.
*/
enum display_pattern {
WWR_ALL_OFF, /* Turn the LEDs off. */
WWR_RECOVERY_PUSHED, /* Recovery button push detected on start up. */
- WWR_WIPEOUT_REQUEST, /* Held long enough for wipout request. */
+ WWR_WIPEOUT_REQUEST, /* Held long enough for wipeout request. */
WWR_RECOVERY_REQUEST, /* Held long enough for recovery request. */
WWR_NORMAL_BOOT /* No buttons pressed, normal boot sequence. */
};
diff --git a/src/drivers/i2c/ww_ring/ww_ring_programs.c b/src/drivers/i2c/ww_ring/ww_ring_programs.c
index 73dd4da..da7cafc 100644
--- a/src/drivers/i2c/ww_ring/ww_ring_programs.c
+++ b/src/drivers/i2c/ww_ring/ww_ring_programs.c
@@ -89,7 +89,7 @@
* The three internal engines seem to be competing for resources and get out
* of sync in seconds if left running asynchronously.
*
- * When solid patterns are deployed with instanteneous color intensity
+ * When solid patterns are deployed with instantaneous color intensity
* changes, all three LEDs can be controlled by one engine in sequential
* accesses. But the controllers still need to be synchronized.
*