linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yin Kangkai <kangkai.yin@linux.intel.com>
To: linux-serial <linux-serial@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	"Woodhouse, David" <david.woodhouse@intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] serial: also set the uartclk value in resume after goes to highspeed
Date: Tue, 25 Jan 2011 15:44:47 +0800	[thread overview]
Message-ID: <20110125074447.GJ3315@kai-debian> (raw)

>From 6f96e25fd4401b152adb9d91ebda0777f3532162 Mon Sep 17 00:00:00 2001
From: Yin Kangkai <kangkai.yin@intel.com>
Date: Mon, 24 Jan 2011 18:45:39 +0800
Subject: [PATCH] serial: also set the uartclk value in resume after goes to highspeed

For any reason if the NS16550A was not work in high speed mode (e.g. we hold
NS16550A from going to high speed mode in autoconfig_16550a()), now we are
resume from suspend, we should also set the uartclk to the correct
value. Otherwise it is still the old 1843200 and that will bring issues.

Signed-off-by: Yin Kangkai <kangkai.yin@intel.com>
---
 drivers/serial/8250.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
index 3e690da..e928e06 100644
--- a/drivers/serial/8250.c
+++ b/drivers/serial/8250.c
@@ -2995,6 +2995,7 @@ void serial8250_resume_port(int line)
 		ns16550a_goto_highspeed(up);
 
 		serial_outp(up, UART_LCR, 0);
+		up->port.uartclk = 921600*16;
 	}
 	uart_resume_port(&serial8250_reg, &up->port);
 }
-- 
1.6.5

             reply	other threads:[~2011-01-25  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  7:44 Yin Kangkai [this message]
2011-02-03 22:15 ` [PATCH] serial: also set the uartclk value in resume after goes to highspeed Greg KH
2011-02-09  3:34 ` [PATCH resend 1/2] " Yin Kangkai
2011-02-09  3:35 ` [PATCH resend 2/2] serial: change the divisor latch only when prescalar actually changed Yin Kangkai

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=20110125074447.GJ3315@kai-debian \
    --to=kangkai.yin@linux.intel.com \
    --cc=david.woodhouse@intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.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).