From: Linus Walleij <linus.walleij@linaro.org>
To: Rajanikanth H V <rajanikanth.hv@stericsson.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Christophe ARNAL <christophe.arnal@stericsson.com>,
Guillaume JAUNET <guillaume.jaunet@stericsson.com>,
Matthias LOCHER <matthias.locher@stericsson.com>,
Chanho Min <chanho0207@gmail.com>,
Srinidhi KASAGAR <srinidhi.kasagar@stericsson.com>
Subject: Re: [PATCH] serial: pl011: implement workaround for CTS clear event issue
Date: Mon, 26 Mar 2012 11:14:56 +0200 [thread overview]
Message-ID: <CACRpkdaHoDawAXnXSK4KG4L_fusbWny2-b=UOS8LcQh4pdQS2g@mail.gmail.com> (raw)
In-Reply-To: <2B1D156D95AE9B4EAD379CB9E465FE73255E4BB903@EXDCVYMBSTM005.EQ1STM.local>
On Mon, Mar 26, 2012 at 11:07 AM, Rajanikanth H V
<rajanikanth.hv@stericsson.com> wrote:
> As per my understanding, pass counter helps to identify/break the
> Deadlock situation and triggers bottom half handler in which
> Uart controller will be forced to reset (save and restore of UART register happens).
It was there before the fix for the deadlock situation found in ST hardwares,
which was solved by the tasklet, was ever introduced.
It has been around forever as a simple guard to stop the ISR from
going into a loop... which is nice coding practice anyway so let's
keep it.
Yours,
Linus Walleij
prev parent reply other threads:[~2012-03-26 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 8:01 [PATCH] serial: pl011: implement workaround for CTS clear event issue Linus Walleij
2012-03-26 8:17 ` Russell King - ARM Linux
2012-03-26 9:05 ` Linus Walleij
2012-03-26 9:07 ` Rajanikanth H V
2012-03-26 9:14 ` Linus Walleij [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='CACRpkdaHoDawAXnXSK4KG4L_fusbWny2-b=UOS8LcQh4pdQS2g@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=chanho0207@gmail.com \
--cc=christophe.arnal@stericsson.com \
--cc=gregkh@suse.de \
--cc=guillaume.jaunet@stericsson.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matthias.locher@stericsson.com \
--cc=rajanikanth.hv@stericsson.com \
--cc=srinidhi.kasagar@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 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).