From: Udit Kumar <u-kumar1@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <francesco@dolcini.it>
Cc: <kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH v2 0/2] Fix UART pin type and macro type
Date: Mon, 15 Apr 2024 15:26:03 +0530 [thread overview]
Message-ID: <20240415095605.3547933-1-u-kumar1@ti.com> (raw)
This series fixes UART pin mux for J784s4-evm and am69.
Along with replacing pin mux macro of J784S4 SOC instead of J721S2.
Test logs
https://gist.github.com/uditkumarti/a28ec171732e32c16b2666c27093c115
For fixes, these errors should be caught during review but missed due to
cross reference is taken from tool's output.
Note to self, don't always rely on tool's output while reviewing the patch.
Change logs:
Changes in v2:
Splitting patch series into two as refactoring and fixes,
This series is for fixes, refactoring will be sent later
Link of v1: https://lore.kernel.org/all/20240415063329.3286600-1-u-kumar1@ti.com/
Udit Kumar (2):
arm64: dts: ti: k3-j784s4-evm: Fix UART pin type and macro type
arm64: dts: ti: k3-am69-sk: Fix UART pin type and macro type
arch/arm64/boot/dts/ti/k3-am69-sk.dts | 12 ++++++------
arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 8 ++++----
2 files changed, 10 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-15 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 9:56 Udit Kumar [this message]
2024-04-15 9:56 ` [PATCH v2 1/2] arm64: dts: ti: k3-j784s4-evm: Fix UART pin type and macro type Udit Kumar
2024-04-15 11:02 ` Francesco Dolcini
2024-04-15 9:56 ` [PATCH v2 2/2] arm64: dts: ti: k3-am69-sk: " Udit Kumar
2024-04-15 11:03 ` Francesco Dolcini
2024-04-26 22:39 ` [PATCH v2 0/2] " Nishanth Menon
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=20240415095605.3547933-1-u-kumar1@ti.com \
--to=u-kumar1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@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