All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irq: enable suspended EARLY_RESUME irqs forcefully if not resumed
Date: Fri, 19 Jul 2013 19:30:48 +0530	[thread overview]
Message-ID: <51E94690.1010702@nvidia.com> (raw)
In-Reply-To: <1373380343-10143-1-git-send-email-ldewangan@nvidia.com>

Hi Thomas,

On Tuesday 09 July 2013 08:02 PM, Laxman Dewangan wrote:
> When system enters into suspend, it disable all irqs in single
> function call. This disables EARLY_RESUME irqs also along with
> normal irqs.
>
> The EARLY_RESUME irqs get enabled in sys_core_ops->resume and
> non-EARLY_RESUME irqs get enabled in normal system resume path.
>
> When suspend_noirq failed or suspend is aborted for any reason,
> the EARLY_RESUME irqs do not get enabled as sys_core_ops->resume()
> call did not happen. It only enables the non-EARLY_RESUME irqs in normal
> disable for remaining life of system.
>
> Add checks on normal irq_resume() whether EARLY_RESUME irqs have been
> enabled or not and if not then enable it forcefully.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---


Any feedback on this patch please?

Thanks,
Laxman

  reply	other threads:[~2013-07-19 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 14:32 [PATCH] irq: enable suspended EARLY_RESUME irqs forcefully if not resumed Laxman Dewangan
2013-07-19 14:00 ` Laxman Dewangan [this message]
2013-07-19 15:29 ` Thomas Gleixner
2013-07-22 15:49   ` Konrad Rzeszutek Wilk
2013-07-22 19:32     ` Konrad Rzeszutek Wilk
2013-07-31 14:10       ` Laxman Dewangan

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=51E94690.1010702@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.