From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Govindraj <govindraj.ti@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: Unbalanced IRQ wake disable during resume from static suspend
Date: Tue, 07 Dec 2010 13:32:02 -0800 [thread overview]
Message-ID: <87bp4xl165.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012030251230.17078@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 3 Dec 2010 03:00:28 -0700 (MST)")
Paul Walmsley <paul@pwsan.com> writes:
> Hi Kevin
>
> On Thu, 2 Dec 2010, Kevin Hilman wrote:
>
>> I guess this hasn't been seen before since we haven't tested the sysfs
>> wakeup interface for the omap-serial driver. For on-chip OMAP UARTs,
>> using the sysfs interface isn't needed as the serial core is already
>> doing device_init_wakeup(dev, true);
>
> Is this the code you're referring to, in serial_core.c?
>
> tty_dev = tty_register_device(drv->tty_driver, uport->line, uport->dev);
> if (likely(!IS_ERR(tty_dev))) {
> device_init_wakeup(tty_dev, 1);
> device_set_wakeup_enable(tty_dev, 0);
> } else
>
> I may be misreading it, but it appears that the code leaves wakeups
> disabled for the serial port, by default.
No, I was referring to the code in mach-omap2/serial.c, in omap_serial_init_port():
if ((cpu_is_omap34xx() && uart->padconf) ||
(uart->wk_en && uart->wk_mask)) {
device_init_wakeup(&od->pdev.dev, true);
DEV_CREATE_FILE(&od->pdev.dev, &dev_attr_sleep_timeout);
}
Kevin
> As an aside, this code is somewhat perplexing: it doesn't seem accurate to
> assume that every serial device really is capable of waking up the system.
next prev parent reply other threads:[~2010-12-07 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 8:05 Unbalanced IRQ wake disable during resume from static suspend Paul Walmsley
2010-12-02 8:14 ` Paul Walmsley
2010-12-02 9:08 ` Santosh Shilimkar
2010-12-02 10:34 ` Govindraj
2010-12-02 11:10 ` Santosh Shilimkar
2010-12-02 14:15 ` Kevin Hilman
2010-12-02 14:54 ` Santosh Shilimkar
2010-12-03 10:00 ` Paul Walmsley
2010-12-07 21:32 ` Kevin Hilman [this message]
2010-12-03 10:23 ` Paul Walmsley
2010-12-03 11:08 ` Santosh Shilimkar
2010-12-03 11:20 ` Govindraj
2010-12-03 11:26 ` Santosh Shilimkar
2010-12-09 18:20 ` Kevin Hilman
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=87bp4xl165.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=govindraj.ti@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.