From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM/arm64: dts: renesas: Describe RTS/CTS hardware flow control
Date: Fri, 6 May 2016 08:49:07 +0900 [thread overview]
Message-ID: <20160505234906.GD24999@verge.net.au> (raw)
In-Reply-To: <1462352278-30327-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
On Wed, May 04, 2016 at 10:57:55AM +0200, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> This patch series updates the various Renesas DTSes to describe that
> some UARTS have dedicated lines for RTS/CTS hardware flow control, and
> that they are available for use (wired and enabled by pinmux
> configuration), by adding the "uart-has-rtscts" property to
> board-specific DTS files where appropriate.
>
> While the actual DT binding updates documenting the "uart-has-rtscts"
> property for SCIF(A) UARTs ("serial: sh-sci: Update DT binding
> documentation for dedicated RTS/CTS") hasn't been accepted into tty-next
> yet, this property is part of the Generic Serial DT Bindings
> (Documentation/devicetree/bindings/serial/serial.txt), which has been
> accepted.
On the basis of the binding being present in the generic documentation
I have queued up these patches. If that was not your intention please
let me know.
> Actual enablement of RTS/CTS hardware flow control (through setting the
> CRTSCTS termios flag from userspace) depends on series "[PATCH v2 00/11]
> serial: sh-sci: Hardware Flow Control Updates"
> (http://www.spinics.net/lists/linux-serial/msg22535.html).
> Note that setting the CRTSCTS flag for a serial port that is being used
> as the kernel console is a bad idea ;-) You'll have better luck with
> UARTs on expansion connectors, cfr. the topic/renesas-overlays branch of
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
>
> Thanks!
>
> Geert Uytterhoeven (3):
> ARM: dts: bockw: SCIF0 supports RTS/CTS hardware flow control
> ARM: dts: kzm9g: SCIFA4 supports RTS/CTS hardware flow control
> arm64: dts: salvator-x: SCIF1 supports RTS/CTS hardware flow control
>
> arch/arm/boot/dts/r8a7778-bockw.dts | 1 +
> arch/arm/boot/dts/sh73a0-kzm9g.dts | 1 +
> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 1 +
> 3 files changed, 3 insertions(+)
>
> --
> 1.9.1
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2016-05-05 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 8:57 [PATCH 0/3] ARM/arm64: dts: renesas: Describe RTS/CTS hardware flow control Geert Uytterhoeven
2016-05-04 8:57 ` [PATCH 1/3] ARM: dts: bockw: SCIF0 supports " Geert Uytterhoeven
2016-05-04 8:57 ` [PATCH 2/3] ARM: dts: kzm9g: SCIFA4 " Geert Uytterhoeven
2016-05-04 8:57 ` [PATCH 3/3] arm64: dts: salvator-x: SCIF1 " Geert Uytterhoeven
2016-05-05 23:49 ` Simon Horman [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=20160505234906.GD24999@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).