From: Tony Lindgren <tony@atomide.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
mika.westerberg@linux.intel.com
Subject: Re: [PATCH 3/6] tty: serial: 8250 core: add runtime pm
Date: Wed, 9 Jul 2014 23:28:12 -0700 [thread overview]
Message-ID: <20140710062812.GF28884@atomide.com> (raw)
In-Reply-To: <1404928177-26554-4-git-send-email-bigeasy@linutronix.de>
* Sebastian Andrzej Siewior <bigeasy@linutronix.de> [140709 10:52]:
> While comparing the OMAP-serial and the 8250 part of this I noticed that
> the the latter does not use runtime-pm. Here are the pieces. It is
> basically a get before first register access and a last_busy + put after
> last access.
> If I understand this correct, it should do nothing as long as
> pm_runtime_use_autosuspend() + pm_runtime_enable() isn't invoked on the
> device.
...
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -571,7 +573,17 @@ static void serial8250_set_sleep(struct uart_8250_port *p, int sleep)
> serial_out(p, UART_EFR, 0);
> serial_out(p, UART_LCR, 0);
> }
> +
> + if (!device_may_wakeup(p->port.dev)) {
> + if (sleep)
> + pm_runtime_forbid(p->port.dev);
> + else
> + pm_runtime_allow(p->port.dev);
> + }
> }
> +out:
> + pm_runtime_mark_last_busy(p->port.dev);
> + pm_runtime_put_autosuspend(p->port.dev);
> }
The device_may_wakeup logic here is wrong as I described in the
earlier thread. For runtime PM, the wake-up events should be
always enabled. So the device_may_wakeup checks should be only
done for suspend and resume.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] tty: serial: 8250 core: add runtime pm
Date: Wed, 9 Jul 2014 23:28:12 -0700 [thread overview]
Message-ID: <20140710062812.GF28884@atomide.com> (raw)
In-Reply-To: <1404928177-26554-4-git-send-email-bigeasy@linutronix.de>
* Sebastian Andrzej Siewior <bigeasy@linutronix.de> [140709 10:52]:
> While comparing the OMAP-serial and the 8250 part of this I noticed that
> the the latter does not use runtime-pm. Here are the pieces. It is
> basically a get before first register access and a last_busy + put after
> last access.
> If I understand this correct, it should do nothing as long as
> pm_runtime_use_autosuspend() + pm_runtime_enable() isn't invoked on the
> device.
...
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -571,7 +573,17 @@ static void serial8250_set_sleep(struct uart_8250_port *p, int sleep)
> serial_out(p, UART_EFR, 0);
> serial_out(p, UART_LCR, 0);
> }
> +
> + if (!device_may_wakeup(p->port.dev)) {
> + if (sleep)
> + pm_runtime_forbid(p->port.dev);
> + else
> + pm_runtime_allow(p->port.dev);
> + }
> }
> +out:
> + pm_runtime_mark_last_busy(p->port.dev);
> + pm_runtime_put_autosuspend(p->port.dev);
> }
The device_may_wakeup logic here is wrong as I described in the
earlier thread. For runtime PM, the wake-up events should be
always enabled. So the device_may_wakeup checks should be only
done for suspend and resume.
Regards,
Tony
next prev parent reply other threads:[~2014-07-10 6:28 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 17:49 (unknown), Sebastian Andrzej Siewior
2014-07-09 17:49 ` No subject Sebastian Andrzej Siewior
2014-07-09 17:49 ` [PATCH 1/6] tty: serial: 8250 core: provide a function to export uart_8250_port Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-10 14:30 ` Olivier Galibert
2014-07-10 14:30 ` Olivier Galibert
2014-07-16 8:22 ` Sebastian Andrzej Siewior
2014-07-16 8:22 ` Sebastian Andrzej Siewior
2014-07-09 17:49 ` [PATCH 2/6] tty: serial: 8250 core: allow to overwrite & export serial8250_startup() Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-10 14:54 ` One Thousand Gnomes
2014-07-10 14:54 ` One Thousand Gnomes
2014-07-10 14:55 ` Sebastian Andrzej Siewior
2014-07-10 14:55 ` Sebastian Andrzej Siewior
2014-07-09 17:49 ` [PATCH 3/6] tty: serial: 8250 core: add runtime pm Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-10 6:28 ` Tony Lindgren [this message]
2014-07-10 6:28 ` Tony Lindgren
2014-07-16 8:26 ` Sebastian Andrzej Siewior
2014-07-16 8:26 ` Sebastian Andrzej Siewior
2014-07-21 13:34 ` Mika Westerberg
2014-07-21 13:34 ` Mika Westerberg
2014-07-09 17:49 ` [PATCH 4/6] tty: serial: 8250-core: reorder serial8250_stop_rx() & serial8250_start_tx() Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-09 17:49 ` [PATCH 5/6] tty: serial: 8250-core: add rs485 support Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-09 19:01 ` Lennart Sorensen
2014-07-09 19:01 ` Lennart Sorensen
2014-07-10 15:55 ` Sebastian Andrzej Siewior
2014-07-10 15:55 ` Sebastian Andrzej Siewior
2014-07-10 14:52 ` One Thousand Gnomes
2014-07-10 14:52 ` One Thousand Gnomes
2014-07-09 17:49 ` [PATCH 6/6] tty: serial: Add 8250-core based omap driver Sebastian Andrzej Siewior
2014-07-09 17:49 ` Sebastian Andrzej Siewior
2014-07-10 7:09 ` Tony Lindgren
2014-07-10 7:09 ` Tony Lindgren
2014-07-10 15:47 ` Sebastian Andrzej Siewior
2014-07-10 15:47 ` Sebastian Andrzej Siewior
2014-07-10 16:03 ` Carlos Hernandez
2014-07-10 16:03 ` Carlos Hernandez
2014-07-10 16:14 ` menon.nishanth
2014-07-10 16:14 ` menon.nishanth at gmail.com
2014-07-11 6:41 ` Tony Lindgren
2014-07-11 6:41 ` Tony Lindgren
2014-07-16 12:11 ` Sebastian Andrzej Siewior
2014-07-16 12:11 ` Sebastian Andrzej Siewior
2014-07-16 12:32 ` Tony Lindgren
2014-07-16 12:32 ` Tony Lindgren
2014-07-16 13:00 ` Sekhar Nori
2014-07-16 13:00 ` Sekhar Nori
2014-08-08 11:05 ` Heikki Krogerus
2014-08-08 11:05 ` Heikki Krogerus
2014-07-09 17:58 ` [RFC v3] 8250-core based serial driver for OMAP Sebastian Andrzej Siewior
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=20140710062812.GF28884@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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.