From: Peter Hung <hpeter@gmail.com>
To: gregkh@linuxfoundation.org
Cc: jslaby@suse.cz, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, tom_tsai@fintek.com.tw,
peter_hong@fintek.com.tw, hpeter+kernel@gmail.com,
Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: [PATCH V3 0/1] serial: 8250_pci: Fintek products S3 patch
Date: Wed, 1 Apr 2015 14:00:20 +0800 [thread overview]
Message-ID: <1427868021-4027-1-git-send-email-hpeter+linux_kernel@gmail.com> (raw)
The patch works for Fintek F81504/F81508/F81512 PCI to Serial Port IC.
Serial port of this IC will failed after wakeup from S3(STR).
It's due to this PCI device's configuration space from 0x40 to
0x40 + max_port * 0x08 should be re-configured when the system wakeup from
S3(STR). If had no re-configure after S3, It's will all zero. It's will make
uart function disabled.
We move all initialization from pci_fintek_setup() to pci_fintek_init() and
set it to pci_serial_quirks struct .init section. It's will re-init this
device when system wakeup from pciserial_resume_ports().
V3 changelog
1. due to cleanup code patch is applied, this patch is following branch
tty_testing fbf47635315ab308c9b58a1ea0906e711a9228de.
V2 changelog (old)
1. swap pci_fintek_setup() / pci_fintek_init() location in source code to
make diff more readable
V1 changelog (old)
1. Initial version, including 2 patches, one is cleanup code, another is fix
S3 bug.
Peter Hung (1):
serial: 8250_pci: port failed after wakeup from S3
drivers/tty/serial/8250/8250_pci.c | 114 ++++++++++++++++---------------------
1 file changed, 50 insertions(+), 64 deletions(-)
--
1.9.1
next reply other threads:[~2015-04-01 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 6:00 Peter Hung [this message]
2015-04-01 6:00 ` [PATCH V3 1/1] serial: 8250_pci: port failed after wakeup from S3 Peter Hung
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=1427868021-4027-1-git-send-email-hpeter+linux_kernel@gmail.com \
--to=hpeter@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+kernel@gmail.com \
--cc=hpeter+linux_kernel@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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).