From: Tony Lindgren <tony@atomide.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Alan Stern <stern@rowland.harvard.edu>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] PM / wakeirq: Add wakeup name to dedicated wake irqs
Date: Fri, 23 Feb 2018 14:04:40 -0800 [thread overview]
Message-ID: <20180223220440.GC5593@atomide.com> (raw)
In-Reply-To: <CAHp75VcSRxLZJxmqXWpAGypvZa6W2cEAiTF2muJWqdaOYu_TpA@mail.gmail.com>
* Andy Shevchenko <andy.shevchenko@gmail.com> [180214 10:24]:
> Subject: [PATCH] genirq: Add wakeup sysfs node to show IRQ wakeup state
>
> Surprisingly there is no simple way to see if the IRQ line in question
> is wakeup source or not.
Finally got around trying this one. Yeah it's nice and it seems
that this is how we could also allow add support for showing the
time when the wakeirq triggered and was actually seen by the irq
subsystem. I think that's what people have been after for a
while :)
It seems we should do both /sys/kernel/irq/*/wakeup and also
have a name for the dedicated wakeirqs. I'll send out my
kasprintf updated patch shortly.
Regards,
Tony
next prev parent reply other threads:[~2018-02-23 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 16:14 [PATCH] PM / wakeirq: Add wakeup name to dedicated wake irqs Tony Lindgren
2018-02-14 10:52 ` Rafael J. Wysocki
2018-02-14 11:23 ` Andy Shevchenko
2018-02-16 9:14 ` Rafael J. Wysocki
2018-02-16 10:39 ` Andy Shevchenko
2018-02-16 10:54 ` Rafael J. Wysocki
2018-02-16 14:52 ` Andy Shevchenko
2018-02-20 11:14 ` Rafael J. Wysocki
2018-02-16 16:54 ` Tony Lindgren
2018-02-23 22:04 ` Tony Lindgren [this message]
2018-02-16 9:42 ` Rafael J. Wysocki
2018-02-16 16:42 ` Tony Lindgren
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=20180223220440.GC5593@atomide.com \
--to=tony@atomide.com \
--cc=andy.shevchenko@gmail.com \
--cc=briannorris@chromium.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox