@@ -16,7 +16,7 @@ &backlight {
* PWM backlight circuit on this PinePhone revision was changed since
* 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
* being off is around 20%. Duty cycle for the lowest brightness level
- * also varries quite a bit between individual boards, so the lowest
+ * also varies quite a bit between individual boards, so the lowest
* value here was chosen as a safe default.
*/
brightness-levels = <
@@ -123,7 +123,7 @@ gic: interrupt-controller@78090000 {
#address-cells = <2>;
#size-cells = <2>;
interrupt-controller;
- interrupts = <1 9 0xf04>; /* GIC Maintenence IRQ */
+ interrupts = <1 9 0xf04>; /* GIC Maintenance IRQ */
ranges = <0 0 0 0x79000000 0x0 0x800000>; /* MSI Range */
reg = <0x0 0x78090000 0x0 0x10000>, /* GIC Dist */
<0x0 0x780a0000 0x0 0x20000>, /* GIC CPU */
@@ -109,7 +109,7 @@ gic: interrupt-controller@78010000 {
<0x0 0x78020000 0x0 0x1000>, /* GIC CPU */
<0x0 0x78040000 0x0 0x2000>, /* GIC VCPU Control */
<0x0 0x78060000 0x0 0x2000>; /* GIC VCPU */
- interrupts = <1 9 0xf04>; /* GIC Maintenence IRQ */
+ interrupts = <1 9 0xf04>; /* GIC Maintenance IRQ */
};
timer {
@@ -645,7 +645,7 @@ tmuctrl_0: tmu@10060000 {
ufs: ufs@15570000 {
compatible = "samsung,exynos7-ufs";
reg = <0x15570000 0x100>, /* 0: HCI standard */
- <0x15570100 0x100>, /* 1: Vendor specificed */
+ <0x15570100 0x100>, /* 1: Vendor specified */
<0x15571000 0x200>, /* 2: UNIPRO */
<0x15572000 0x300>; /* 3: UFS protector */
reg-names = "hci", "vs_hci", "unipro", "ufsp";
@@ -150,7 +150,7 @@ gic: interrupt-controller@6000000 {
its: msi-controller@6020000 {
compatible = "arm,gic-v3-its";
msi-controller;
- reg = <0x0 0x06020000 0 0x20000>;/* GIC Translater */
+ reg = <0x0 0x06020000 0 0x20000>;/* GIC Translator */
};
};
@@ -1,6 +1,6 @@
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
- * Device Tree file for Travese Ten64 (LS1088) board
+ * Device Tree file for Traverse Ten64 (LS1088) board
* Based on fsl-ls1088a-rdb.dts
* Copyright 2017-2020 NXP
* Copyright 2019-2021 Traverse Technologies
@@ -504,7 +504,7 @@ pinctrl_hog2: hog2grp {
/*
* This pin is used in the SCFW as a UART. Using it from
- * Linux would require rewritting the SCFW board file.
+ * Linux would require rewriting the SCFW board file.
*/
pinctrl_hog_scfw: hogscfwgrp {
fsl,pins = <IMX8QXP_SCU_GPIO0_00_LSIO_GPIO2_IO03 0x20>; /* SODIMM 144 */
@@ -666,12 +666,12 @@ in-ports {
/*
* Not described input ports:
- * 0 - connected to Resource and Power Manger CPU ETM
+ * 0 - connected to Resource and Power Manager CPU ETM
* 1 - not-connected
* 2 - connected to Modem CPU ETM
* 3 - not-connected
* 5 - not-connected
- * 6 - connected trought funnel to Wireless CPU ETM
+ * 6 - connected through funnel to Wireless CPU ETM
* 7 - connected to STM component
*/
@@ -857,7 +857,7 @@ &sdhc1 {
status = "okay";
/*
- * This device is shipped with HS400 capabable eMMCs
+ * This device is shipped with HS400 capable eMMCs
* However various brands have been used in various product batches,
* including a Samsung eMMC (BGND3R) which features a quirk with HS400.
* Set the speed to HS200 as a safety measure.
@@ -4,7 +4,7 @@
*
* SA8155P is an automotive variant of SM8150, with some minor changes.
* Most notably, the RPMhPD setup differs: MMCX and LCX/LMX rails are gone,
- * though the cmd-db doesn't reflect that and access attemps result in a bite.
+ * though the cmd-db doesn't reflect that and access attempts result in a bite.
*/
#include "sm8150.dtsi"
@@ -563,8 +563,8 @@ &sdc1_rclk {
*
* This has entries that are defined by Qcard even if they go to the main
* board. In cases where the pulls may be board dependent we defer those
- * settings to the board device tree. Drive strengths tend to be assinged here
- * but could conceivably be overwridden by board device trees.
+ * settings to the board device tree. Drive strengths tend to be assigned here
+ * but could conceivably be overridden by board device trees.
*/
&pm8350c_gpios {
@@ -168,7 +168,7 @@ vph_pwr: vph-pwr-regulator {
* Supply map from xiaomi-lavender specifies this as the supply for
* ldob1, ldob9, ldob10, ldoa2, and ldoa3, while downstream specifies
* this as a power domain. Set this as a fixed regulator with the same
- * voltage as lavender until display is needed to avoid unneccessarily
+ * voltage as lavender until display is needed to avoid unnecessarily
* using a deprecated binding (regulator-fixed-domain).
*/
vreg_s2b_1p05: vreg-s2b-regulator {
@@ -305,7 +305,7 @@ vreg_l19a_2p7: ldo19 {
regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
/*
- * The driver *really* doesn't want this regualtor to exist,
+ * The driver *really* doesn't want this regulator to exist,
* saying that it could not get the current voltage (-ENOTRECOVERABLE)
* even though it surely is used on these devices (as a voltage
* source for camera autofocus)
@@ -226,7 +226,7 @@ &audio_clk_b {
/*
* X11 is connected to VI4_FIELD/SCIF_CLK/AUDIO_CLKB,
* and R-Car Sound uses AUDIO_CLKB.
- * Note is that schematic indicates VI4_FIELD conection only
+ * Note is that schematic indicates VI4_FIELD connection only
* not AUDIO_CLKB at SoC page.
* And this VI4_FIELD/SCIF_CLK/AUDIO_CLKB is connected to SW60.
* SW60 should be 1-2.
@@ -9,7 +9,7 @@
/*
* Notice:
* 1. rk3399-roc-pc-plus is powered by dc_12v directly.
- * 2. rk3399-roc-pc-plus has only vcc_bus_typec0 in schematic, which is coresponding
+ * 2. rk3399-roc-pc-plus has only vcc_bus_typec0 in schematic, which is corresponding
* to vcc_vbus_typec1 in rk3399-roc-pc.
* For simplicity, reserve the node name of vcc_vbus_typec1.
* 3. vcc5v0_host is actually 2 regulators (host0, 1) controlled by the same gpio.
@@ -1415,7 +1415,7 @@ &usbss0 {
status = "disabled";
};
-/* TODO: role swich using ID pin */
+/* TODO: role switch using ID pin */
&usb0 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usb0>, <&pinctrl_usb0_id>;