From: Andrew Davis <afd@ti.com>
To: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: <devicetree@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
<linux-renesas-soc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH v2 7/7] staging: pi433: overlay: Rename overlay source file from .dts to .dtso
Date: Mon, 24 Oct 2022 12:34:34 -0500 [thread overview]
Message-ID: <20221024173434.32518-8-afd@ti.com> (raw)
In-Reply-To: <20221024173434.32518-1-afd@ti.com>
DTB Overlays (.dtbo) can now be built from source files with the
extension (.dtso). This makes it clear what is the content of the files
and differentiates them from base DTB source files.
Rename the pi433-overlay.dts file to pi433-overlay.dtso and update
the information file pi433.txt for the same.
Signed-off-by: Andrew Davis <afd@ti.com>
---
.../devicetree/{pi433-overlay.dts => pi433-overlay.dtso} | 0
drivers/staging/pi433/Documentation/devicetree/pi433.txt | 6 +++---
2 files changed, 3 insertions(+), 3 deletions(-)
rename drivers/staging/pi433/Documentation/devicetree/{pi433-overlay.dts => pi433-overlay.dtso} (100%)
diff --git a/drivers/staging/pi433/Documentation/devicetree/pi433-overlay.dts b/drivers/staging/pi433/Documentation/devicetree/pi433-overlay.dtso
similarity index 100%
rename from drivers/staging/pi433/Documentation/devicetree/pi433-overlay.dts
rename to drivers/staging/pi433/Documentation/devicetree/pi433-overlay.dtso
diff --git a/drivers/staging/pi433/Documentation/devicetree/pi433.txt b/drivers/staging/pi433/Documentation/devicetree/pi433.txt
index a810548c58572..d317c0ec3419e 100644
--- a/drivers/staging/pi433/Documentation/devicetree/pi433.txt
+++ b/drivers/staging/pi433/Documentation/devicetree/pi433.txt
@@ -48,13 +48,13 @@ For Raspbian users only
=======================
Since Raspbian supports device tree overlays, you may use an overlay instead
of editing your boards device tree.
-To use the overlay, you need to compile the file pi433-overlay.dts which can
+To use the overlay, you need to compile the file pi433-overlay.dtso which can
be found alongside this documentation.
The file needs to be compiled - either manually or by integration in your kernel
source tree. For a manual compile, you may use a command line like the following:
-'linux/scripts/dtc/dtc -@ -I dts -O dtb -o pi433.dtbo pi433-overlay.dts'
+'linux/scripts/dtc/dtc -@ -I dts -O dtb -o pi433.dtbo pi433-overlay.dtso'
-For compiling inside of the kernel tree, you need to copy pi433-overlay.dts to
+For compiling inside of the kernel tree, you need to copy pi433-overlay.dtso to
arch/arm/boot/dts/overlays and you need to add the file to the list of files
in the Makefile over there. Execute 'make dtbs' in kernel tree root to make the
kernel make files compile the device tree overlay for you.
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-24 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:34 [PATCH v2 0/7] Rename DTB overlay source files Andrew Davis
2022-10-24 17:34 ` [PATCH v2 1/7] kbuild: Allow DTB overlays to built from .dtso named " Andrew Davis
2022-10-24 22:01 ` Frank Rowand
2022-10-24 17:34 ` [PATCH v2 2/7] kbuild: Allow DTB overlays to built into .dtso.S files Andrew Davis
2022-10-24 22:01 ` Frank Rowand
2022-10-24 17:34 ` [PATCH v2 3/7] of: overlay: rename overlay source files from .dts to .dtso Andrew Davis
2022-10-24 22:01 ` Frank Rowand
2022-10-24 17:34 ` [PATCH v2 4/7] arm64: dts: freescale: Rename DTB " Andrew Davis
2022-11-19 6:32 ` Shawn Guo
2022-10-24 17:34 ` [PATCH v2 5/7] arm64: dts: renesas: " Andrew Davis
2022-10-24 17:34 ` [PATCH v2 6/7] arm64: dts: xilinx: " Andrew Davis
2022-11-30 16:50 ` Michal Simek
2022-10-24 17:34 ` Andrew Davis [this message]
2022-10-25 6:57 ` [PATCH v2 7/7] staging: pi433: overlay: Rename overlay source file " Geert Uytterhoeven
2022-10-24 22:04 ` [PATCH v2 0/7] Rename DTB overlay source files Frank Rowand
2022-10-26 14:11 ` Rob Herring
2022-11-11 19:39 ` Andy Shevchenko
2022-11-11 19:40 ` Andy Shevchenko
2022-11-11 21:05 ` Andrew Davis
2022-11-13 12:20 ` Andy Shevchenko
2022-11-13 12:36 ` Andy Shevchenko
2022-11-14 16:06 ` Andy Shevchenko
2022-11-14 20:43 ` Andrew Davis
2022-11-15 11:29 ` Andy Shevchenko
2022-11-14 14:39 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221024173434.32518-8-afd@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).