From nobody Wed Oct 1 22:31:19 2025 Received: from mx08-007fc201.pphosted.com (mx08-007fc201.pphosted.com [91.207.212.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D51BA1A0728; Fri, 26 Sep 2025 10:58:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.207.212.40 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884295; cv=none; b=JIY57dTFQ+zLGFbTM5qw+8BpFzw1Hvca+v837yytUTPo1PzM0nBbgLb/qHAJq+w3cHzCbPpi4Ts9YkdNO5tBtzOVZAwsY9FPjLlwnvdxqXaHML4kaztuN3Z86wUjIMSa1pWna52/YsYvfaYSKktiHYtt6k5ALG8Sop2WVlsdcNk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884295; c=relaxed/simple; bh=OlwSIEhC6piVzlola9oc9MYitobW9lQy0i2CACSYXoo=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=NvZX9D9jhBHaeJRXDdsLU7747zCJMxdhah7f+ZK8X8+tDKnsf3ddCOVHcuadCJMvB8Uh4ciOidBhjZJ+iJNKCV1IR6iMPPuOOqiPLrXOD+CkiW2ImCcHw98+ua8T8zCeQLauiSQzwmCKn8GM+kP//3TI6qEHfkcIXVgnEO7iOQ0= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de; spf=pass smtp.mailfrom=cab.de; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b=xfqFhOlj; arc=none smtp.client-ip=91.207.212.40 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cab.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b="xfqFhOlj" Received: from pps.filterd (m0456229.ppops.net [127.0.0.1]) by mx08-007fc201.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 58QAlYfk1885731; Fri, 26 Sep 2025 12:58:05 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cab.de; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=pp-2025; bh=py tvRdTcmloiBeFxyTpL2fDC7wHne6PunwfFuQabaO8=; b=xfqFhOljlpuA0B7kuQ j2k1W18lyVlw9Z7nLsFg640mtnDKBBTLon/pElfNPK+FQ7pa5vn/3yTKK5YUFMc+ xLZ8j0josmFOP39sNMOTV5B/W0U6U16hjfYxYrkPVK+eZ/3CinimQM02W6M9Hj3r PY7PpCShKED1Fm/+g3AZvaTBCVRbx9AtWqlFpQLmZ6/AMlA7u+SEo89+Gd2URoKr vB6VLQpDNRSrG2hJam3ZaROsgjPvwyTQCwr4pZVgHI6af5sJmeLNmDE6frWta0Vp n3T2kh4ls6fBfYvXHjxt2pVb0UCerNYF+rT5XhWZk/itTpLuxggD8V8XlUsYXJb9 IO4g== Received: from adranos.cab.de (adranos.cab.de [46.232.229.107]) by mx08-007fc201.pphosted.com (PPS) with ESMTPS id 49dbt4g848-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 26 Sep 2025 12:58:05 +0200 (MEST) Received: from KAN23-025.cab.de (10.10.3.180) by Adranos.cab.de (10.10.1.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.36; Fri, 26 Sep 2025 12:58:21 +0200 From: Markus Heidelberg To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Saravana Kannan CC: , , Markus Heidelberg Subject: [PATCH 1/3] docs: dt: fix grammar and spelling Date: Fri, 26 Sep 2025 12:57:47 +0200 Message-ID: <20250926105749.209674-2-m.heidelberg@cab.de> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250926105749.209674-1-m.heidelberg@cab.de> References: <20250926105749.209674-1-m.heidelberg@cab.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: Adranos.cab.de (10.10.1.54) To Adranos.cab.de (10.10.1.54) X-Proofpoint-GUID: bjw4cfpp92Ppwy3qS5EPA8W0v-g9bAkI X-Authority-Analysis: v=2.4 cv=XdWEDY55 c=1 sm=1 tr=0 ts=68d671bd cx=c_pps a=LmW7qmVeM6tFdl5svFU9Cg==:117 a=LmW7qmVeM6tFdl5svFU9Cg==:17 a=kldc_9v1VKEA:10 a=yJojWOMRYYMA:10 a=4qyJXJ5HrNyFQtBNG3wA:9 a=cPQSjfK2_nFv0Q5t_7PE:22 X-Proofpoint-ORIG-GUID: bjw4cfpp92Ppwy3qS5EPA8W0v-g9bAkI X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwOTI2MDEwMCBTYWx0ZWRfX1aN6Dc3KD9pS dvvQ8HZWI8jBkhuLtsRuMXnfrMhk3yIMoK9baLWYIIgM/FUqDeAbW6VF5EMRkfu8tQOGNP4M8hH HdcKcHhuAFdbaCvUuMBic+kS+GH2g02H3jViZAzuyPOhI02HhEhgrbBXz1xmJlDvNLTmVxhyyYh 03ScHYa+dl6P1wpE0ZTJ3zZtuNglwTfO3HKedBkgUaB6ukEYHNFaJVSIVRdZKRQtLKXoGqwtiTy hl8Q4bln5kKH5M4SOvkZTT2GIhno9YYlzzxQg+Cdz4qeDE+z3TiBs7QX3TGAz59AiFtyEf0FFrD +GXIOHGuY5s4vhc0gSvcSELWKSQ+kh8WSijU+8hLPs1zgTIDVfIbeY+h8ArwP+Vfu3oQo7Vu+XG +OHzeSoIxN6+ZS/8e/AmwtGESg5lXw== Content-Type: text/plain; charset="utf-8" Signed-off-by: Markus Heidelberg --- Documentation/devicetree/of_unittest.rst | 4 ++-- Documentation/devicetree/overlay-notes.rst | 6 +++--- Documentation/devicetree/usage-model.rst | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Documentation/devicetree/of_unittest.rst b/Documentation/devic= etree/of_unittest.rst index a6c05962add3..8b557acd29d1 100644 --- a/Documentation/devicetree/of_unittest.rst +++ b/Documentation/devicetree/of_unittest.rst @@ -56,7 +56,7 @@ drivers/of/unittest.c. See the content of the folder:: =20 for the Device Tree Source Include files (.dtsi) included in testcases.dts. =20 -When the kernel is build with CONFIG_OF_UNITTEST enabled, then the followi= ng make +When the kernel is built with CONFIG_OF_UNITTEST enabled, then the followi= ng make rule:: =20 $(obj)/%.dtb: $(src)/%.dts FORCE @@ -133,7 +133,7 @@ via the following kernel symbols:: __dtb_testcases_end - address marking the end of test data blob =20 Secondly, it calls of_fdt_unflatten_tree() to unflatten the flattened -blob. And finally, if the machine's device tree (i.e live tree) is present, +blob. And finally, if the machine's device tree (i.e. live tree) is presen= t, then it attaches the unflattened test data tree to the live tree, else it attaches itself as a live device tree. =20 diff --git a/Documentation/devicetree/overlay-notes.rst b/Documentation/dev= icetree/overlay-notes.rst index 35e79242af9a..ba401ef850e7 100644 --- a/Documentation/devicetree/overlay-notes.rst +++ b/Documentation/devicetree/overlay-notes.rst @@ -14,11 +14,11 @@ How overlays work A Devicetree's overlay purpose is to modify the kernel's live tree, and have the modification affecting the state of the kernel in a way that is reflecting the changes. -Since the kernel mainly deals with devices, any new device node that result +Since the kernel mainly deals with devices, any new device node that resul= ts in an active device should have it created while if the device node is eit= her disabled or removed all together, the affected device should be deregister= ed. =20 -Lets take an example where we have a foo board with the following base tre= e:: +Let's take an example where we have a foo board with the following base tr= ee:: =20 ---- foo.dts ---------------------------------------------------------= ------ /* FOO platform */ @@ -111,7 +111,7 @@ The API is quite easy to use. 1) Call of_overlay_fdt_apply() to create and apply an overlay changeset. T= he return value is an error or a cookie identifying this overlay. =20 -2) Call of_overlay_remove() to remove and cleanup the overlay changeset +2) Call of_overlay_remove() to remove and clean up the overlay changeset previously created via the call to of_overlay_fdt_apply(). Removal of an overlay changeset that is stacked by another will not be permitted. =20 diff --git a/Documentation/devicetree/usage-model.rst b/Documentation/devic= etree/usage-model.rst index 0717426856b2..c6146c96ac56 100644 --- a/Documentation/devicetree/usage-model.rst +++ b/Documentation/devicetree/usage-model.rst @@ -46,7 +46,7 @@ The DT was originally created by Open Firmware as part of= the communication method for passing data from Open Firmware to a client program (like to an operating system). An operating system used the Device Tree to discover the topology of the hardware at runtime, and -thereby support a majority of available hardware without hard coded +thereby supported a majority of available hardware without hard coded information (assuming drivers were available for all devices). =20 Since Open Firmware is commonly used on PowerPC and SPARC platforms, @@ -128,7 +128,7 @@ successor, the BeagleBoard xM board might look like, re= spectively:: compatible =3D "ti,omap3-beagleboard-xm", "ti,omap3450", "ti,omap3"; =20 Where "ti,omap3-beagleboard-xm" specifies the exact model, it also -claims that it compatible with the OMAP 3450 SoC, and the omap3 family +claims that it is compatible with the OMAP 3450 SoC, and the omap3 family of SoCs in general. You'll notice that the list is sorted from most specific (exact board) to least specific (SoC family). =20 @@ -205,7 +205,7 @@ platform-specific configuration data. =20 During early boot, the architecture setup code calls of_scan_flat_dt() several times with different helper callbacks to parse device tree -data before paging is setup. The of_scan_flat_dt() code scans through +data before paging is set up. The of_scan_flat_dt() code scans through the device tree and uses the helpers to extract information required during early boot. Typically the early_init_dt_scan_chosen() helper is used to parse the chosen node including kernel parameters, --=20 2.43.0 From nobody Wed Oct 1 22:31:19 2025 Received: from mx07-007fc201.pphosted.com (mx07-007fc201.pphosted.com [185.132.181.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EA4E42F1FF9; Fri, 26 Sep 2025 11:01:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.132.181.212 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884511; cv=none; b=QF7y7kykeDNJAPCNjKT2nerwrHfe4ODxADQEwUKLCcRVi4IhIYsO6op40d1FgBwlUPpWdfkxQVIbXsaGkwEBqFKQqrHdmPtG5ahuVOKXGv10TpjeGUZvym4kVRDA+6idMVy9uneB4QEp40jHsH5bS7dVJwK9/79nTfOgcrqtd0M= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884511; c=relaxed/simple; bh=VaAZKkFChJIHKnL817/3FAjkNowwP29UkpU7OtVMf5E=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=UtjpCggdZhK24U6BzloQnaISRKJIPzI2Q8Gw17OQc2FEJO3NrTUi5IZX2q4vncs2L0d98yTPks6mWnffrfbQNt95e0bU41xNXn6OuHxJ1H66Z8zDFyL4c8tHPz402ZOkfpUBBPjO9TmTu0vAlxKuucHX8lEGIPwhKRzvD0RhE2g= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de; spf=pass smtp.mailfrom=cab.de; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b=H4GfbMmD; arc=none smtp.client-ip=185.132.181.212 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cab.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b="H4GfbMmD" Received: from pps.filterd (m0456228.ppops.net [127.0.0.1]) by mx07-007fc201.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 58QAw1Kf1882429; Fri, 26 Sep 2025 12:58:08 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cab.de; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=pp-2025; bh=zq D6CM9SuPLqYSZCw+MSvKaUJsZirU6oapnpU/YzVlA=; b=H4GfbMmDBf66nbUrK1 knZBHB3qPD6OToUxOVYorDONk0dvAk8RfBfxKiH6L9PDYas5K7yq53uvJPqwuFad VviduH/rXg/udM9OTGz16P7GtvUHlayFZqpFly7s0+q0mE35CxX/ZvxNQI+pHRox w0gvmbLoHQmQZbxw3xRscGFEuzbkSkK1U+pdIl3R5WO8KMJ4QGcDsBO9A3v7yexa BkRPICzi6nggNRiSxybpmhpduzi+7N4DWYjzMjE9UURN3w68aQTDGL79tAfZpMXI 4Geak1MFaQ/gTVTst4fElVDEoG/qvsnIUh3xU3lEzAkC8NZTTg7fdJ3USGfZBRM5 dANQ== Received: from adranos.cab.de (adranos.cab.de [46.232.229.107]) by mx07-007fc201.pphosted.com (PPS) with ESMTPS id 49dbt3g7xb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 26 Sep 2025 12:58:08 +0200 (MEST) Received: from KAN23-025.cab.de (10.10.3.180) by Adranos.cab.de (10.10.1.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.36; Fri, 26 Sep 2025 12:58:25 +0200 From: Markus Heidelberg To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Saravana Kannan CC: , , Markus Heidelberg Subject: [PATCH 2/3] dt-bindings: fix spelling, typos, grammar, duplicated words Date: Fri, 26 Sep 2025 12:57:48 +0200 Message-ID: <20250926105749.209674-3-m.heidelberg@cab.de> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250926105749.209674-1-m.heidelberg@cab.de> References: <20250926105749.209674-1-m.heidelberg@cab.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: Adranos.cab.de (10.10.1.54) To Adranos.cab.de (10.10.1.54) X-Authority-Analysis: v=2.4 cv=fOA0HJae c=1 sm=1 tr=0 ts=68d671c0 cx=c_pps a=LmW7qmVeM6tFdl5svFU9Cg==:117 a=LmW7qmVeM6tFdl5svFU9Cg==:17 a=kldc_9v1VKEA:10 a=yJojWOMRYYMA:10 a=8pif782wAAAA:8 a=iu6B6VvxPaX3Crc4H9AA:9 a=cPQSjfK2_nFv0Q5t_7PE:22 X-Proofpoint-GUID: U1sYgMeZ2hFsMj5GEheTh4NZoQIPIK2R X-Proofpoint-ORIG-GUID: U1sYgMeZ2hFsMj5GEheTh4NZoQIPIK2R X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwOTI2MDEwMCBTYWx0ZWRfX7vGRIoysKqYw DGEuidNxW52ouVIZg1G4kljFs5VGtuJkKq1bpJQCYrjOrBwayJWbe8g0Cc11vfsE/KNjSVuZVYl T3BtQf8p87VvLHYfhpiOY0lN5dHgtdlxmG+WyTXZZbYWZbgV1v6svGxpXotGQgBD6hCYoh6logK AYSj3D8J5Bodye5ozFSluvoTMs6x17hjcsTVCehQK0KeN0/Jnfqq93SllSSE4TOuA0JNb6nVsR1 oWqT1RkjGTrNc/LU1SmcQS29tROezR1vC1hTgihzL/3j7AmKXRH+mHDlAD2WOR7nQzjeQ9vVX9Z QtrMjvuHnYcDaRxF3X/tGY2VHJN3e2mdI0qQLBkFKJhqw9YogfglsV2RetAXqkClpHGLG4YxJBB OionRqn+1V6bETh4zAWYn5diu/Jd/Q== Content-Type: text/plain; charset="utf-8" Signed-off-by: Markus Heidelberg --- .../devicetree/bindings/arm/arm,vexpress-juno.yaml | 2 +- .../devicetree/bindings/example-schema.yaml | 2 +- Documentation/devicetree/bindings/gpio/gpio.txt | 12 ++++++------ .../devicetree/bindings/iommu/mediatek,iommu.yaml | 2 +- Documentation/devicetree/bindings/leds/common.yaml | 2 +- .../devicetree/bindings/mfd/ti,lp87524-q1.yaml | 2 +- .../devicetree/bindings/mfd/ti,lp87561-q1.yaml | 2 +- .../devicetree/bindings/mfd/ti,lp87565-q1.yaml | 2 +- .../bindings/mmc/mmc-controller-common.yaml | 4 ++-- .../devicetree/bindings/net/amlogic,meson-dwmac.yaml | 2 +- .../devicetree/bindings/net/ethernet-controller.yaml | 2 +- .../devicetree/bindings/net/ethernet-phy.yaml | 2 +- .../devicetree/bindings/net/micrel-ksz90x1.txt | 4 ++-- Documentation/devicetree/bindings/net/micrel.txt | 2 +- .../devicetree/bindings/submitting-patches.rst | 2 +- 15 files changed, 22 insertions(+), 22 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml b= /Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml index 89298b39903f..4cdca5320544 100644 --- a/Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml +++ b/Documentation/devicetree/bindings/arm/arm,vexpress-juno.yaml @@ -140,7 +140,7 @@ patternProperties: the connection between the motherboard and any tiles. Sometimes the compatible is placed directly under this node, sometimes it is placed in a subnode named "motherboard-bus". Sometimes the compatible inclu= des - "arm,vexpress,v2?-p1" sometimes (on software models) is is just + "arm,vexpress,v2?-p1" sometimes (on software models) it is just "simple-bus". If the compatible is placed in the "motherboard-bus" n= ode, it is stricter and always has two compatibles. type: object diff --git a/Documentation/devicetree/bindings/example-schema.yaml b/Docume= ntation/devicetree/bindings/example-schema.yaml index c731d5045e80..b04f3cc4312c 100644 --- a/Documentation/devicetree/bindings/example-schema.yaml +++ b/Documentation/devicetree/bindings/example-schema.yaml @@ -223,7 +223,7 @@ required: # # For multiple 'if' schema, group them under an 'allOf'. # -# If the conditionals become too unweldy, then it may be better to just sp= lit +# If the conditionals become too unwieldy, then it may be better to just s= plit # the binding into separate schema documents. allOf: - if: diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentatio= n/devicetree/bindings/gpio/gpio.txt index d82c32217fff..b37dbb1edc62 100644 --- a/Documentation/devicetree/bindings/gpio/gpio.txt +++ b/Documentation/devicetree/bindings/gpio/gpio.txt @@ -35,8 +35,8 @@ and bit-banged data signals: <&gpio1 15 0>; =20 In the above example, &gpio1 uses 2 cells to specify a gpio. The first cel= l is -a local offset to the GPIO line and the second cell represent consumer fla= gs, -such as if the consumer desire the line to be active low (inverted) or open +a local offset to the GPIO line and the second cell represents consumer fl= ags, +such as if the consumer desires the line to be active low (inverted) or op= en drain. This is the recommended practice. =20 The exact meaning of each specifier cell is controller specific, and must = be @@ -59,7 +59,7 @@ GPIO pin number, and GPIO flags as accepted by the "qe_pi= o_e" gpio-controller. Optional standard bitfield specifiers for the last cell: =20 - Bit 0: 0 means active high, 1 means active low -- Bit 1: 0 mean push-pull wiring, see: +- Bit 1: 0 means push-pull wiring, see: https://en.wikipedia.org/wiki/Push-pull_output 1 means single-ended wiring, see: https://en.wikipedia.org/wiki/Single-ended_triode @@ -176,7 +176,7 @@ example of a name from an SoC's reference manual) would= not be desirable. =20 In either case placeholders are discouraged: rather use the "" (blank string) if the use of the GPIO line is undefined in your design. Ideally, -try to add comments to the dts file describing the naming the convention +try to add comments to the dts file describing the naming convention you have chosen, and specifying from where the names are derived. =20 The names are assigned starting from line offset 0, from left to right, @@ -304,7 +304,7 @@ pins 50..69. It is also possible to use pin groups for gpio ranges when pin groups are = the easiest and most convenient mapping. =20 -Both both and must set to 0 when using named pin gr= oups +Both and must be set to 0 when using named pin grou= ps names. =20 The property gpio-ranges-group-names must contain exactly one string for e= ach @@ -313,7 +313,7 @@ range. Elements of gpio-ranges-group-names must contain the name of a pin group defined in the respective pin controller. The number of pins/GPIO lines in= the range is the number of pins in that pin group. The number of pins of that -group is defined int the implementation and not in the device tree. +group is defined in the implementation and not in the device tree. =20 If numerical and named pin groups are mixed, the string corresponding to a numerical pin range in gpio-ranges-group-names must be empty. diff --git a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml b/= Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml index 75750c64157c..f49ed8ac4776 100644 --- a/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml +++ b/Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml @@ -52,7 +52,7 @@ description: |+ As above, The Multimedia HW will go through SMI and M4U while it access EMI. SMI is a bridge between m4u and the Multimedia HW. It contain smi local arbiter and smi common. It will control whether the Multimedia - HW should go though the m4u for translation or bypass it and talk + HW should go through the m4u for translation or bypass it and talk directly with EMI. And also SMI help control the power domain and clocks= for each local arbiter. =20 diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documenta= tion/devicetree/bindings/leds/common.yaml index 3e8319e44339..274f83288a92 100644 --- a/Documentation/devicetree/bindings/leds/common.yaml +++ b/Documentation/devicetree/bindings/leds/common.yaml @@ -62,7 +62,7 @@ properties: default-state: description: The initial state of the LED. If the LED is already on or off and the - default-state property is set the to same value, then no glitch shou= ld be + default-state property is set to the same value, then no glitch shou= ld be produced where the LED momentarily turns off (or on). The "keep" set= ting will keep the LED at whatever its current state is, without producin= g a glitch. diff --git a/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml b/Doc= umentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml index ae149eb8593d..ca72786b0e0d 100644 --- a/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml +++ b/Documentation/devicetree/bindings/mfd/ti,lp87524-q1.yaml @@ -26,7 +26,7 @@ properties: '#gpio-cells': description: The first cell is the pin number. - The second cell is is used to specify flags. + The second cell is used to specify flags. See ../gpio/gpio.txt for more information. const: 2 =20 diff --git a/Documentation/devicetree/bindings/mfd/ti,lp87561-q1.yaml b/Doc= umentation/devicetree/bindings/mfd/ti,lp87561-q1.yaml index 5167d6eb904a..885e33276b1b 100644 --- a/Documentation/devicetree/bindings/mfd/ti,lp87561-q1.yaml +++ b/Documentation/devicetree/bindings/mfd/ti,lp87561-q1.yaml @@ -26,7 +26,7 @@ properties: '#gpio-cells': description: The first cell is the pin number. - The second cell is is used to specify flags. + The second cell is used to specify flags. See ../gpio/gpio.txt for more information. const: 2 =20 diff --git a/Documentation/devicetree/bindings/mfd/ti,lp87565-q1.yaml b/Doc= umentation/devicetree/bindings/mfd/ti,lp87565-q1.yaml index eca430edf608..2b5b54aa6c73 100644 --- a/Documentation/devicetree/bindings/mfd/ti,lp87565-q1.yaml +++ b/Documentation/devicetree/bindings/mfd/ti,lp87565-q1.yaml @@ -28,7 +28,7 @@ properties: '#gpio-cells': description: The first cell is the pin number. - The second cell is is used to specify flags. + The second cell is used to specify flags. See ../gpio/gpio.txt for more information. const: 2 =20 diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller-common.ya= ml b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml index 9a7235439759..1e601da0339a 100644 --- a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml +++ b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml @@ -57,7 +57,7 @@ properties: # latter case. We choose to use the XOR logic for GPIO CD and WP # lines. This means, the two properties are "superimposed," for # example leaving the GPIO_ACTIVE_LOW flag clear and specifying the - # respective *-inverted property property results in a + # respective *-inverted property results in a # double-inversion and actually means the "normal" line polarity is # in effect. wp-inverted: @@ -264,7 +264,7 @@ properties: mmc-pwrseq-simple.yaml. But now it\'s reused as a tunable delay waiting for I/O signalling and card power supply to be stable, regardless of whether pwrseq-simple is used. Default to 10ms if - no available. + not available. default: 10 =20 supports-cqe: diff --git a/Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml= b/Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml index 0cd78d71768c..5c91716d1f21 100644 --- a/Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml +++ b/Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml @@ -149,7 +149,7 @@ properties: - description: The first register range should be the one of the DWMAC controll= er - description: - The second range is is for the Amlogic specific configuration + The second range is for the Amlogic specific configuration (for example the PRG_ETHERNET register range on Meson8b and newe= r) =20 interrupts: diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml= b/Documentation/devicetree/bindings/net/ethernet-controller.yaml index 66b1cfbbfe22..341f4938c956 100644 --- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml +++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml @@ -222,7 +222,7 @@ properties: reg: maxItems: 1 description: - This define the LED index in the PHY or the MAC. It's really + This defines the LED index in the PHY or the MAC. It's really driver dependent and required for ports that define multiple LED for the same port. =20 diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Docu= mentation/devicetree/bindings/net/ethernet-phy.yaml index 71e2cd32580f..2ec2d9fda7e3 100644 --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml @@ -266,7 +266,7 @@ properties: reg: maxItems: 1 description: - This define the LED index in the PHY or the MAC. It's really + This defines the LED index in the PHY or the MAC. It's really driver dependent and required for ports that define multiple LED for the same port. =20 diff --git a/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt b/Doc= umentation/devicetree/bindings/net/micrel-ksz90x1.txt index 2681168777a1..6f7b907d5a04 100644 --- a/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt +++ b/Documentation/devicetree/bindings/net/micrel-ksz90x1.txt @@ -13,7 +13,7 @@ KSZ9021: =20 All skew control options are specified in picoseconds. The minimum value is 0, the maximum value is 3000, and it can be specified in 200ps - steps, *but* these values are in not fact what you get because this chip= 's + steps, *but* these values are in no way what you get because this chip's skew values actually increase in 120ps steps, starting from -840ps. The incorrect values came from an error in the original KSZ9021 datasheet before it was corrected in revision 1.2 (Feb 2014), but it is too late to @@ -153,7 +153,7 @@ KSZ9031: - micrel,force-master: Boolean, force phy to master mode. Only set this option if the phy reference clock provided at CLK125_NDO pin is used as MAC reference - clock because the clock jitter in slave mode is to high (errata#2). + clock because the clock jitter in slave mode is too high (errata#2= ). Attention: The link partner must be configurable as slave otherwise no link will be established. =20 diff --git a/Documentation/devicetree/bindings/net/micrel.txt b/Documentati= on/devicetree/bindings/net/micrel.txt index a407dd1b4614..01622ce58112 100644 --- a/Documentation/devicetree/bindings/net/micrel.txt +++ b/Documentation/devicetree/bindings/net/micrel.txt @@ -26,7 +26,7 @@ Optional properties: Setting the RMII Reference Clock Select bit enables 25 MHz rather than 50 MHz clock mode. =20 - Note that this option in only needed for certain PHY revisions with a + Note that this option is only needed for certain PHY revisions with a non-standard, inverted function of this configuration bit. Specifically, a clock reference ("rmii-ref" below) is always needed to actually select a mode. diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Doc= umentation/devicetree/bindings/submitting-patches.rst index 46d0b036c97e..5f24570f72e9 100644 --- a/Documentation/devicetree/bindings/submitting-patches.rst +++ b/Documentation/devicetree/bindings/submitting-patches.rst @@ -95,7 +95,7 @@ II. For kernel maintainers For subsystem bindings (anything affecting more than a single device), getting a devicetree maintainer to review it is required. =20 - 3) For a series going though multiple trees, the binding patch should be + 3) For a series going through multiple trees, the binding patch should be kept with the driver using the binding. =20 4) The DTS files should however never be applied via driver subsystem tr= ee, --=20 2.43.0 From nobody Wed Oct 1 22:31:19 2025 Received: from mx08-007fc201.pphosted.com (mx08-007fc201.pphosted.com [91.207.212.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8F55E1A0728; Fri, 26 Sep 2025 10:58:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.207.212.40 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884301; cv=none; b=Ehkv1JZmnA4IUp365wgRomL+xBb9UIMT0DxyJQ8ttRVjDmn9XZWdaOj1ZK1MKpcD0pCQ5/W0t0YJej2rIAUJvgglLhc0iFJ7KRKCcSEvonOVQo7LjVHbuzZepnSivsHaHWK7pzMDOu094jYGvACSWO5ogZW3FzjfsVEQ3eCGV6s= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758884301; c=relaxed/simple; bh=6xMqwN1K48HFPeQfpozsi+RDyW+9cDj391ewWhcbO+Y=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=ZJSDqzC0obvfwrKCyeDt56nT8NN15xPvrKHg0jKN3btH8Osfk48KtQfqiroqBORHr3fOjVE8W44wAvmNDSgwOy5/aGyOVJkut4vQa2xWb3Fp1OCRfxm8c3SPzhecXHMM+0lVQmeVIGjMz0kpgeUGsnSuOLREu1B/rb/8SSQuJ0A= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de; spf=pass smtp.mailfrom=cab.de; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b=SoE0hSHn; arc=none smtp.client-ip=91.207.212.40 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=cab.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cab.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cab.de header.i=@cab.de header.b="SoE0hSHn" Received: from pps.filterd (m0456229.ppops.net [127.0.0.1]) by mx08-007fc201.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 58QAiC4v1879977; Fri, 26 Sep 2025 12:58:11 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cab.de; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=pp-2025; bh=vk EunV1KBQ7ghw7cGF+nRAdebricNzU4mNgjoDPs7ME=; b=SoE0hSHnfBhFdiDjtT C0buTrCsix/gNQsRW7e+8rsYoSTshFy1e7Nfdd0DApwd1hFOptXeJFPdvdu72BIz h4Xp+ttJYhL3NCUimtWE5iz6gbjWBPJ5hxxDEn9MvuNh9K+z478rsiy3OfgO/1ja fZGMHAlRf0vLQ/xqnTJR8DTcDLOQeTcA7kKu+MvVubeTLNn/XuQp/ikmF1krL5Sx 7uUxLXoUPWGNroDKnCvqqRkbvE0dZ3pCZ7mPUljKpCTcE8L2fTi2DmsMJxVqv0XN 77cX4/iOT/eWvkFCNEp6h/z7Tw5lc253nOAj4ya5KuCTwcpRa25Hb0FBNa9RRcTw Vmpg== Received: from adranos.cab.de (adranos.cab.de [46.232.229.107]) by mx08-007fc201.pphosted.com (PPS) with ESMTPS id 49dbt4g84c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 26 Sep 2025 12:58:11 +0200 (MEST) Received: from KAN23-025.cab.de (10.10.3.180) by Adranos.cab.de (10.10.1.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.36; Fri, 26 Sep 2025 12:58:27 +0200 From: Markus Heidelberg To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Saravana Kannan CC: , , Markus Heidelberg Subject: [PATCH 3/3] scripts: dt_to_config: fix grammar and a typo in --help text Date: Fri, 26 Sep 2025 12:57:49 +0200 Message-ID: <20250926105749.209674-4-m.heidelberg@cab.de> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250926105749.209674-1-m.heidelberg@cab.de> References: <20250926105749.209674-1-m.heidelberg@cab.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: Adranos.cab.de (10.10.1.54) To Adranos.cab.de (10.10.1.54) X-Proofpoint-GUID: dTadPejI04EJMxz2YVdXUJ03-WsuNaFG X-Authority-Analysis: v=2.4 cv=XdWEDY55 c=1 sm=1 tr=0 ts=68d671c3 cx=c_pps a=LmW7qmVeM6tFdl5svFU9Cg==:117 a=LmW7qmVeM6tFdl5svFU9Cg==:17 a=kldc_9v1VKEA:10 a=yJojWOMRYYMA:10 a=GkquxFhGB3ijP0pvFI0A:9 a=cPQSjfK2_nFv0Q5t_7PE:22 X-Proofpoint-ORIG-GUID: dTadPejI04EJMxz2YVdXUJ03-WsuNaFG X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwOTI2MDEwMCBTYWx0ZWRfX47sOcUM42tUo AFNQ54RiskKCYD2Y+Tj5RlMwOlQg1gcaFO1o5frdP2rELvLL/m64N1PRzXreN8y0LXE9cCi7eSh 5kiwnJLtEEEqJvmdV72wf3wWwZoTsgXXwhBsGdtWw2XioF0+TDbznvA8rByPOKv0cpqnG+i+rEe 15C71gDqGXn6EjK7xFMSSSy8l4jZFsymzN11PqwEmDdEi602N1HaZiKUOGgiFZjlxLR8ktJ2c1I jDiqCFnD8VDO9e7ny1QX3iC/hlzi2Z0tgE+b39MmqfyLtcwfyJ7XQU5c/5AYD8pGqCTQjvsMzSb r8ObgPzE08PGMiA90OMYu5zwOXFMAaO5NC5ytL7EjpoSPs9toB8szLRG3iTd/y95pepayeTlCW9 dT6Z8NI67AnowFKwlNFafOLwlpV1Cg== Content-Type: text/plain; charset="utf-8" - grammar: singular/plural inconsistency - typo: "of" -> "or" Signed-off-by: Markus Heidelberg --- scripts/dtc/dt_to_config | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/scripts/dtc/dt_to_config b/scripts/dtc/dt_to_config index 299d1c2b20d7..70d6d5f06bdc 100755 --- a/scripts/dtc/dt_to_config +++ b/scripts/dtc/dt_to_config @@ -51,10 +51,10 @@ $num_pr_flags =3D $pr_flag_pos_config_test_fail + 1; "compatible is white listed", "matching driver and/or kernel config is hard coded", "kernel config hard coded in Makefile", - "one or more kernel config file options is not set", - "one or more kernel config file options is set to 'm'", - "one or more kernel config file options is set to 'y'", - "one of more kernel config file options fails to have correct value" + "one or more kernel config file options are not set", + "one or more kernel config file options are set to 'm'", + "one or more kernel config file options are set to 'y'", + "one or more kernel config file options fail to have correct value" ); =20 =20 --=20 2.43.0