From: Linus Walleij <linus.walleij@linaro.org>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Shreshtha Kumar Sahu <shreshthakumar.sahu@stericsson.com>
Subject: Re: [PATCH 1/2] amba pl011: workaround for uart registers lockup
Date: Thu, 16 Jun 2011 10:17:51 +0200 [thread overview]
Message-ID: <BANLkTikSEVCGGsjF_fTCNZsmjvGoic5u=Q@mail.gmail.com> (raw)
In-Reply-To: <1307952693-25232-1-git-send-email-linus.walleij@stericsson.com>
On Mon, Jun 13, 2011 at 10:11 AM, Linus Walleij
<linus.walleij@stericsson.com> wrote:
> From: Shreshtha Kumar Sahu <shreshthakumar.sahu@stericsson.com>
>
> This workaround aims to break the deadlock situation
> which raises during continuous transfer of data for long
> duration over uart with hardware flow control. It is
> observed that CTS interrupt cannot be cleared in uart
> interrupt register (ICR). Hence further transfer over
> uart gets blocked.
Ping on this, Greg have you picked these two for the tty next tree?
Thanks,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] amba pl011: workaround for uart registers lockup
Date: Thu, 16 Jun 2011 10:17:51 +0200 [thread overview]
Message-ID: <BANLkTikSEVCGGsjF_fTCNZsmjvGoic5u=Q@mail.gmail.com> (raw)
In-Reply-To: <1307952693-25232-1-git-send-email-linus.walleij@stericsson.com>
On Mon, Jun 13, 2011 at 10:11 AM, Linus Walleij
<linus.walleij@stericsson.com> wrote:
> From: Shreshtha Kumar Sahu <shreshthakumar.sahu@stericsson.com>
>
> This workaround aims to break the deadlock situation
> which raises during continuous transfer of data for long
> duration over uart with hardware flow control. It is
> observed that CTS interrupt cannot be cleared in uart
> interrupt register (ICR). Hence further transfer over
> uart gets blocked.
Ping on this, Greg have you picked these two for the tty next tree?
Thanks,
Linus Walleij
next prev parent reply other threads:[~2011-06-16 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 8:11 [PATCH 1/2] amba pl011: workaround for uart registers lockup Linus Walleij
2011-06-13 8:11 ` Linus Walleij
2011-06-16 8:17 ` Linus Walleij [this message]
2011-06-16 8:17 ` Linus Walleij
2011-06-16 15:16 ` Greg KH
2011-06-16 15:16 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 20:56 Linus Walleij
2011-06-09 20:56 ` Linus Walleij
2011-05-16 13:01 Shreshtha Kumar SAHU
2011-05-16 13:01 ` Shreshtha Kumar SAHU
2011-05-16 17:29 ` 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='BANLkTikSEVCGGsjF_fTCNZsmjvGoic5u=Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=gregkh@suse.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=shreshthakumar.sahu@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.