From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: jslaby@suse.com, linux-serial@vger.kernel.org, dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
patrice.chotard@st.com
Subject: Re: [PATCH v2 00/10] serial: st-asc: Allow handling of RTS line
Date: Fri, 3 Feb 2017 10:10:43 +0100 [thread overview]
Message-ID: <20170203091043.GA10386@kroah.com> (raw)
In-Reply-To: <20170201143145.31962-1-lee.jones@linaro.org>
On Wed, Feb 01, 2017 at 02:31:35PM +0000, Lee Jones wrote:
> When hardware flow-control is disabled, manual toggling of the UART's
> reset line (RTS) using userland applications (e.g. stty) is not
> possible, since the ASC IP does not provide this functionality in the
> same was as some other IPs do. Thus, we have to do this manually.
>
> This set ensures the correct Pinctrl groups are configured and
> obtained for both manual toggling of the RTS line and for the IP to
> take over the lines when HW flow-control is requested by the user.
I see 2 series that are listed as "v2", which one to take?
I know, I'll drop both and wait for an updated set with all of the acks
added to them...
Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-03 9:10 UTC|newest]
Thread overview: 23+ 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
2017-02-01 14:31 ` [PATCH v2 02/10] serial: st-asc: Provide RTS functionality 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 ` [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 06/10] dt-bindings: serial: Update 'uart-has-rtscts' description Lee Jones
2017-02-01 14:57 ` [STLinux Kernel] " Peter Griffin
2017-02-01 14:31 ` [PATCH v2 07/10] ARM: dts: STiH410-b2260: Identify the UART RTS line Lee Jones
2017-02-01 14:55 ` [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-01 14:31 ` [PATCH v2 09/10] ARM: dts: STiH407-family: Use new Pinctrl groups Lee Jones
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
2017-02-03 9:10 ` Greg KH [this message]
2017-02-03 10:17 ` [PATCH v2 00/10] serial: st-asc: Allow handling of RTS line Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 17:27 Lee Jones
2017-02-02 7:42 ` Lee Jones
2017-02-02 9:55 ` Greg KH
2017-02-03 9:22 ` Lee Jones
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=20170203091043.GA10386@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=dt@kernel.org \
--cc=jslaby@suse.com \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--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