From: andreas.devel@googlemail.com (Andreas Bießmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "serial: omap: fix software flow control"
Date: Wed, 07 Nov 2012 10:56:59 +0100 [thread overview]
Message-ID: <509A306B.10409@gmail.com> (raw)
In-Reply-To: <1350396562-32579-1-git-send-email-balbi@ti.com>
On 16.10.2012 16:09, Felipe Balbi wrote:
> This reverts commit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6
> (serial: omap: fix software flow control).
>
> As Russell has pointed out, that commit isn't fixing
> Software Flow Control at all, and it actually makes
> it even more broken.
>
> It was agreed to revert this commit and use Russell's
> latest UART patches instead.
>
> Cc: Russell King <linux@arm.linux.org.uk>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
since 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6 made it into stable (at
least 3.4) I think it would be good decision to also apply this revert
to stable until a working solution exists.
Best regards
Andreas Bie?mann
> ---
>
> Hi Greg,
>
> you might prefer to do the revert yourself, in that case just
> revert commit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6.
>
> thanks
>
> arch/arm/plat-omap/include/plat/omap-serial.h | 4 ++--
> drivers/tty/serial/omap-serial.c | 12 ++++++------
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm/plat-omap/include/plat/omap-serial.h b/arch/arm/plat-omap/include/plat/omap-serial.h
> index f4a4cd0..1957a85 100644
> --- a/arch/arm/plat-omap/include/plat/omap-serial.h
> +++ b/arch/arm/plat-omap/include/plat/omap-serial.h
> @@ -40,10 +40,10 @@
> #define OMAP_UART_WER_MOD_WKUP 0X7F
>
> /* Enable XON/XOFF flow control on output */
> -#define OMAP_UART_SW_TX 0x8
> +#define OMAP_UART_SW_TX 0x04
>
> /* Enable XON/XOFF flow control on input */
> -#define OMAP_UART_SW_RX 0x2
> +#define OMAP_UART_SW_RX 0x04
>
> #define OMAP_UART_SYSC_RESET 0X07
> #define OMAP_UART_TCR_TRIG 0X0F
> diff --git a/drivers/tty/serial/omap-serial.c b/drivers/tty/serial/omap-serial.c
> index 6ede6fd..6d3d26a 100644
> --- a/drivers/tty/serial/omap-serial.c
> +++ b/drivers/tty/serial/omap-serial.c
> @@ -671,19 +671,19 @@ serial_omap_configure_xonxoff
>
> /*
> * IXON Flag:
> - * Flow control for OMAP.TX
> - * OMAP.RX should listen for XON/XOFF
> + * Enable XON/XOFF flow control on output.
> + * Transmit XON1, XOFF1
> */
> if (termios->c_iflag & IXON)
> - up->efr |= OMAP_UART_SW_RX;
> + up->efr |= OMAP_UART_SW_TX;
>
> /*
> * IXOFF Flag:
> - * Flow control for OMAP.RX
> - * OMAP.TX should send XON/XOFF
> + * Enable XON/XOFF flow control on input.
> + * Receiver compares XON1, XOFF1.
> */
> if (termios->c_iflag & IXOFF)
> - up->efr |= OMAP_UART_SW_TX;
> + up->efr |= OMAP_UART_SW_RX;
>
> serial_out(up, UART_EFR, up->efr | UART_EFR_ECB);
> serial_out(up, UART_LCR, UART_LCR_CONF_MODE_A);
>
next prev parent reply other threads:[~2012-11-07 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:09 [PATCH] Revert "serial: omap: fix software flow control" Felipe Balbi
2012-10-16 15:13 ` Tony Lindgren
2012-10-24 10:02 ` Felipe Balbi
2012-10-24 18:57 ` Greg KH
2012-10-24 18:53 ` Felipe Balbi
2012-11-07 9:56 ` Andreas Bießmann [this message]
2012-11-21 20:21 ` Greg KH
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=509A306B.10409@gmail.com \
--to=andreas.devel@googlemail.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).