From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: S3C6410 UART resume problem
Date: Tue, 19 Jul 2011 21:34:01 +0200 [thread overview]
Message-ID: <1534460.6WAISbrX4v@flatron> (raw)
List,
I am experiencing a strange issue with UART ports on a Tiny6410 board, based
on the S3C6410 SoC (hardware wise same as the Mini6410 supported by Linux),
after enabling CONFIG_PM and suspending the SoC.
After triggering a wakeup event, it resumes till arch_suspend_enable_irqs()
called by suspend_enter() and starts to get hammered by infinite amounts of
UART interrupts.
I have tracked this down to disabling UART PCLK clock on suspend and the
bootloader/reset/power down/whatever leaving the UART in an undefined state
with interrupt bits set (specifically Tx interrupt), with the masked clock
making it impossible to ack them by plat-samsung/irq-uart.c.
Any suggestions how to solve this problem?
Best regards,
Tomasz Figa
next reply other threads:[~2011-07-19 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 19:34 Tomasz Figa [this message]
2011-07-20 17:12 ` S3C6410 UART resume problem Tomasz Figa
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=1534460.6WAISbrX4v@flatron \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).