From: "Govindraj.R" <govindraj.raja@ti.com>
To: linux-omap@vger.kernel.org
Cc: linux-serial@vger.kernel.org,
"Govindraj.R" <govindraj.raja@ti.com>,
Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
Partha Basak <p-basak2@ti.com>
Subject: [RFC PATCH] OMAP: UART: Enable tx wakeup bit in wer
Date: Tue, 24 Jan 2012 19:07:29 +0530 [thread overview]
Message-ID: <1327412249-31575-1-git-send-email-govindraj.raja@ti.com> (raw)
From: "Govindraj.R" <govindraj.raja@ti.com>
On omap3630 onwards uart wer reg has bit 7
for tx wakeup enable.
Without this bit set some uart sluggishness might be seen
while printing data on console, response is better when
enabling this bit.
Tested with Beagle XM (OMAP3630)
Cc: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
---
But on omap3430 the bit is not available.
arch/arm/plat-omap/include/plat/omap-serial.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/plat-omap/include/plat/omap-serial.h b/arch/arm/plat-omap/include/plat/omap-serial.h
index 9ff4444..0c22d8d 100644
--- a/arch/arm/plat-omap/include/plat/omap-serial.h
+++ b/arch/arm/plat-omap/include/plat/omap-serial.h
@@ -39,7 +39,7 @@
/* WER = 0x7F
* Enable module level wakeup in WER reg
*/
-#define OMAP_UART_WER_MOD_WKUP 0X7F
+#define OMAP_UART_WER_MOD_WKUP 0xFF
/* Enable XON/XOFF flow control on output */
#define OMAP_UART_SW_TX 0x04
--
1.7.5.4
next reply other threads:[~2012-01-24 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 13:37 Govindraj.R [this message]
2012-01-25 19:14 ` [RFC PATCH] OMAP: UART: Enable tx wakeup bit in wer Paul Walmsley
2012-01-25 19:18 ` Paul Walmsley
2012-03-05 20:23 ` Paul Walmsley
2012-03-06 10:05 ` Raja, Govindraj
2012-03-07 5:57 ` Paul Walmsley
2012-03-09 6:19 ` Raja, Govindraj
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=1327412249-31575-1-git-send-email-govindraj.raja@ti.com \
--to=govindraj.raja@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.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).