From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>, Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/4] arm64: dts: ti: k3-am62x-sk-common: Cleanups and minor additions
Date: Tue, 18 Apr 2023 16:37:36 -0500 [thread overview]
Message-ID: <20230418213740.153519-1-nm@ti.com> (raw)
Hi,
This is a result of looking to cleanup u-boot and realizing there are
pieces missing in kernel that need to be pushed out.
So, minor cleanups and adding a few missing pieces.
Bootlog: https://gist.github.com/nmenon/5e18c8d02c13cf00db649b6f01971d99
Nishanth Menon (4):
arm64: dts: ti: k3-am62x-sk-common: Drop extra EoL
arm64: dts: ti: k3-am62x-sk-common: Describe main_uart1 and wkup_uart
arm64: dts: ti: k3-am62x-sk-common: Add eeprom
arm64: dts: ti: k3-am62x-sk-common: Improve documentation of
mcasp1_pins
.../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 39 ++++++++++++++++---
1 file changed, 34 insertions(+), 5 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-18 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 21:37 Nishanth Menon [this message]
2023-04-18 21:37 ` [PATCH 1/4] arm64: dts: ti: k3-am62x-sk-common: Drop extra EoL Nishanth Menon
2023-04-18 21:37 ` [PATCH 2/4] arm64: dts: ti: k3-am62x-sk-common: Describe main_uart1 and wkup_uart Nishanth Menon
2023-04-18 21:37 ` [PATCH 3/4] arm64: dts: ti: k3-am62x-sk-common: Add eeprom Nishanth Menon
2023-04-18 21:37 ` [PATCH 4/4] arm64: dts: ti: k3-am62x-sk-common: Improve documentation of mcasp1_pins Nishanth Menon
2023-06-15 10:28 ` [PATCH 0/4] arm64: dts: ti: k3-am62x-sk-common: Cleanups and minor additions Vignesh Raghavendra
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=20230418213740.153519-1-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®