From: Lee Jones <lee.jones@linaro.org>
To: gregkh@linuxfoundation.org, jslaby@suse.com,
linux-serial@vger.kernel.org, dt@kernel.org,
devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
patrice.chotard@st.com, Lee Jones <lee.jones@linaro.org>
Subject: [PATCH v2 06/10] dt-bindings: serial: Update 'uart-has-rtscts' description
Date: Wed, 1 Feb 2017 14:31:41 +0000 [thread overview]
Message-ID: <20170201143145.31962-7-lee.jones@linaro.org> (raw)
In-Reply-To: <20170201143145.31962-1-lee.jones@linaro.org>
'uart-has-rtscts' property and 'rts-gpios|cts-gpios' are normally
mutually exclusive, however it is possible for some drivers to have
a dynamic approach, meaning that both properties can be relevant.
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
Documentation/devicetree/bindings/serial/serial.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/serial/serial.txt b/Documentation/devicetree/bindings/serial/serial.txt
index fd970f7..b542a0e 100644
--- a/Documentation/devicetree/bindings/serial/serial.txt
+++ b/Documentation/devicetree/bindings/serial/serial.txt
@@ -23,7 +23,8 @@ Optional properties:
they are available for use (wired and enabled by pinmux configuration).
This depends on both the UART hardware and the board wiring.
Note that this property is mutually-exclusive with "cts-gpios" and
- "rts-gpios" above.
+ "rts-gpios" above, unless support is provided to switch between modes
+ dynamically.
Examples:
--
2.9.3
next prev parent reply other threads:[~2017-02-01 14:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 14:31 [PATCH v2 00/10] serial: st-asc: Allow handling of RTS line Lee Jones
2017-02-01 14:31 ` [PATCH v2 01/10] serial: st-asc: Ignore the parity error bit if 8-bit mode is enabled Lee Jones
[not found] ` <20170201143145.31962-1-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-01 14:31 ` [PATCH v2 02/10] serial: st-asc: Provide RTS functionality Lee Jones
2017-02-01 14:31 ` [PATCH v2 04/10] serial: st-asc: (De)Register GPIOD and swap Pinctrl profiles Lee Jones
2017-02-01 14:31 ` [PATCH v2 05/10] serial: st-asc: Use generic DT binding for announcing RTS/CTS lines Lee Jones
2017-02-01 14:56 ` [STLinux Kernel] " Peter Griffin
2017-02-01 14:31 ` [PATCH v2 08/10] ARM: dts: STiH407-pinctrl: Add Pinctrl group for HW flow-control Lee Jones
2017-02-03 9:10 ` [PATCH v2 00/10] serial: st-asc: Allow handling of RTS line Greg KH
[not found] ` <20170203091043.GA10386-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-02-03 10:17 ` Lee Jones
2017-02-01 14:31 ` [PATCH v2 03/10] serial: st-asc: Read in all Pinctrl states Lee Jones
2017-02-01 14:55 ` [STLinux Kernel] " Peter Griffin
2017-02-01 14:31 ` Lee Jones [this message]
[not found] ` <20170201143145.31962-7-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-01 14:57 ` [STLinux Kernel] [PATCH v2 06/10] dt-bindings: serial: Update 'uart-has-rtscts' description Peter Griffin
2017-02-01 14:31 ` [PATCH v2 07/10] ARM: dts: STiH410-b2260: Identify the UART RTS line Lee Jones
[not found] ` <20170201143145.31962-8-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-01 14:55 ` [STLinux Kernel] " Peter Griffin
2017-02-01 14:31 ` [PATCH v2 09/10] ARM: dts: STiH407-family: Use new Pinctrl groups Lee Jones
[not found] ` <20170201143145.31962-10-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-01 15:02 ` [STLinux Kernel] " Peter Griffin
2017-02-01 14:31 ` [PATCH v2 10/10] ARM: dts: STiH410-b2260: Enable HW flow-control Lee Jones
2017-02-01 14:53 ` [STLinux Kernel] " Peter Griffin
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 17:27 [PATCH v2 00/10] serial: st-asc: Allow handling of RTS line Lee Jones
[not found] ` <20170127172804.23881-1-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-01-27 17:28 ` [PATCH v2 06/10] dt-bindings: serial: Update 'uart-has-rtscts' description Lee Jones
2017-02-01 15:41 ` Rob Herring
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=20170201143145.31962-7-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dt@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=patrice.chotard@st.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).