From: Kevin Hilman <khilman@deeprootsystems.com>
To: Jouni Hogander <jouni.hogander@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH PM-20081106] OMAP: PM: Few fixes to uart clock handling
Date: Wed, 19 Nov 2008 11:41:46 -0800 [thread overview]
Message-ID: <87abbvfqpx.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1227088474-27452-1-git-send-email-jouni.hogander@nokia.com> (Jouni Hogander's message of "Wed\, 19 Nov 2008 11\:54\:34 +0200")
Jouni Hogander <jouni.hogander@nokia.com> writes:
> Omap3_can_sleep is not inside part of idle loop which is protected
> with irg disable. If some irq handler is trying dump out something
> after omap3_can_sleep and before irqs are disabled. It causes oops
> because uart clocks are disabled.
>
> Remove also some unused extra code from omap_uart_can_sleep
>
> Signed-off-by: Jouni Hogander <jouni.hogander@nokia.com>
> ---
> arch/arm/mach-omap2/serial.c | 11 +----------
> 1 files changed, 1 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index ef30d8d..b06b797 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -314,21 +314,13 @@ void omap_uart_check_wakeup(void)
> int omap_uart_can_sleep(void)
> {
> struct omap_uart_state *uart;
> - int can_sleep = 1;
>
> list_for_each_entry(uart, &uart_list, node) {
> - if (!uart->clocked)
> + if (!uart->clocked || !uart->can_sleep)
> continue;
>
> - if (!uart->can_sleep) {
> - can_sleep = 0;
> - continue;
> - }
> -
> /* This UART can now safely sleep. */
> omap_uart_allow_sleep(uart);
> - if (clocks_off_while_idle)
> - omap_uart_disable_clocks(uart);
If we remove this disable, then the fclks will have to be masked/ignored
in omap3_fclks_active() too. This is what I was trying to avoid.
However, based on the potential race with ISRs you described, I think
this is the best option.
Kevin
> }
>
> return 1;
> @@ -435,7 +427,6 @@ static void omap_uart_pm(struct uart_port *port,
> break;
> case 3: /* suspend */
> omap_uart_allow_sleep(uart);
> - omap_uart_disable_clocks(uart);
> break;
> }
> }
> --
> 1.6.0.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-11-19 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 9:54 [PATCH PM-20081106] OMAP: PM: Few fixes to uart clock handling Jouni Hogander
2008-11-19 17:54 ` Kevin Hilman
2008-11-19 19:41 ` Kevin Hilman [this message]
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=87abbvfqpx.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=jouni.hogander@nokia.com \
--cc=linux-omap@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 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.