From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com
Subject: Re: [PATCH 1/2] arm64: dts: imx8mm-beacon: Enable RTS-CTS on UART3
Date: Thu, 5 May 2022 11:53:39 +0800 [thread overview]
Message-ID: <20220505035339.GS14615@dragon> (raw)
In-Reply-To: <20220426205144.476234-1-aford173@gmail.com>
On Tue, Apr 26, 2022 at 03:51:43PM -0500, Adam Ford wrote:
> There is a header for a DB9 serial port, but any attempts to use
> hardware handshaking fail. Enable RTS and CTS pin muxing and enable
> handshaking in the uart node.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Applied both, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-05 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 20:51 [PATCH 1/2] arm64: dts: imx8mm-beacon: Enable RTS-CTS on UART3 Adam Ford
2022-04-26 20:51 ` [PATCH 2/2] arm64: dts: imx8mn-beacon: " Adam Ford
2022-05-05 3:53 ` Shawn Guo [this message]
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=20220505035339.GS14615@dragon \
--to=shawnguo@kernel.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).