mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Eric Caruso <ejcaruso@google.com>,
	rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
	Benson Leung <bleung@google.com>
Subject: Re: irq mask swapping during suspend/resume
Date: Wed, 17 Sep 2014 13:05:33 -0700	[thread overview]
Message-ID: <30052021.2q1IqLHYpU@dtor-glaptop> (raw)
In-Reply-To: <alpine.DEB.2.10.1409171200350.21313@nanos>

Hi Thomas,

On Wednesday, September 17, 2014 12:05:42 PM Thomas Gleixner wrote:
> On Tue, 16 Sep 2014, Eric Caruso wrote:
> > We would like to be able to set different irq masks for triggers during
> > normal operation and for waking up the system. For example, while a laptop
> > is awake, closing the lid and opening the lid should both fire an
> > interrupt, but when the system is asleep, we would like to stay asleep
> > when
> > closing the lid.
> > 
> > We are thinking about stashing the irq mask used specifically for waking
> > the system up in the irq_desc struct, and then swapping it during
> > enable_irq_wake and disable_irq_wake calls. Devices that do not specify a
> > different wake mask will use their normal trigger mask for both
> > situations.
> > 
> > Is this acceptable?
> 
> Not really. Why should irq_desc provide storage for random
> configurations and bind them to some random system state?
> 
> What's wrong with calling
> 
>        irq_set_type(irq, B);
>        enable_irq_wake(irq);
> 
>        disable_irq_wake(irq);
>        irq_set_type(irq, A);

The desire is to avoid doing it in [every] driver but rather have it done
centrally by device/PM core. It does not have to be irq_desc though,
maybe you can suggest a better place for it (aside of the individual driver
code that is)?

Thanks,
Dmitry

  reply	other threads:[~2014-09-17 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA9CXT07f01KW4UeoPPy4k1NM6qfxdtsOQXXSPjTKx7mG_v7Rw@mail.gmail.com>
2014-09-17 17:35 ` Fwd: " Eric Caruso
2014-09-17 19:05 ` Thomas Gleixner
2014-09-17 20:05   ` Dmitry Torokhov [this message]
2014-09-18 20:32     ` Thomas Gleixner
2014-09-21  0:48       ` Rafael J. Wysocki
2014-09-26 16:58         ` Eric Caruso
2014-09-26 21:39           ` Rafael J. Wysocki
2014-09-26 21:47             ` Rafael J. Wysocki
2014-09-29 22:43         ` Thomas Gleixner

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=30052021.2q1IqLHYpU@dtor-glaptop \
    --to=dtor@google.com \
    --cc=bleung@google.com \
    --cc=ejcaruso@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®