From: Sudeep Holla <sudeep.holla@arm.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>,
linux-omap@vger.kernel.org, linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 3/3] ARM: OMAP2+: remove misuse of IRQF_NO_SUSPEND flag
Date: Thu, 4 Feb 2016 13:34:28 +0000 [thread overview]
Message-ID: <56B35364.8090104@arm.com> (raw)
In-Reply-To: <56B34EB7.4080005@ti.com>
On 04/02/16 13:14, Grygorii Strashko wrote:
> Hi Sudeep,
>
> On 02/01/2016 08:28 PM, Sudeep Holla wrote:
>> The IRQF_NO_SUSPEND flag is used to identify the interrupts that should
>> be left enabled so as to allow them to work as expected during the
>> suspend-resume cycle, but doesn't guarantee that it will wake the system
>> from a suspended state, enable_irq_wake is recommended to be used for
>> the wakeup.
>>
>> This patch removes the use of IRQF_NO_SUSPEND flags replacing it with
>> enable_irq_wake instead.
>
> And sorry for delayed reply - I've spent some time investigating it, but
> It was during Christmas holidays and finally I lost track of it :)
>
That's fine, usually that's the case in general will all of us :)
[..]
>
> Another option is to convert omap_prcm_irq_handler to the generic handler
> (now chained) and, probably, make it threaded and all cascaded IRQs as
> nested threaded (this is just a theory).
>
Since I don't have any knowledge of OMAP, I will completely depend on
your for anything OMAP specific.
> I'll be on business trip next two weeks and will not be able to help more with it
> Sorry.
>
No problem, let me know once you get a chance to try out things at your end.
--
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: OMAP2+: remove misuse of IRQF_NO_SUSPEND flag
Date: Thu, 4 Feb 2016 13:34:28 +0000 [thread overview]
Message-ID: <56B35364.8090104@arm.com> (raw)
In-Reply-To: <56B34EB7.4080005@ti.com>
On 04/02/16 13:14, Grygorii Strashko wrote:
> Hi Sudeep,
>
> On 02/01/2016 08:28 PM, Sudeep Holla wrote:
>> The IRQF_NO_SUSPEND flag is used to identify the interrupts that should
>> be left enabled so as to allow them to work as expected during the
>> suspend-resume cycle, but doesn't guarantee that it will wake the system
>> from a suspended state, enable_irq_wake is recommended to be used for
>> the wakeup.
>>
>> This patch removes the use of IRQF_NO_SUSPEND flags replacing it with
>> enable_irq_wake instead.
>
> And sorry for delayed reply - I've spent some time investigating it, but
> It was during Christmas holidays and finally I lost track of it :)
>
That's fine, usually that's the case in general will all of us :)
[..]
>
> Another option is to convert omap_prcm_irq_handler to the generic handler
> (now chained) and, probably, make it threaded and all cascaded IRQs as
> nested threaded (this is just a theory).
>
Since I don't have any knowledge of OMAP, I will completely depend on
your for anything OMAP specific.
> I'll be on business trip next two weeks and will not be able to help more with it
> Sorry.
>
No problem, let me know once you get a chance to try out things at your end.
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-02-04 13:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 18:28 [PATCH 0/3] OMAP/pinmux: remove misuse of IRQF_NO_SUSPEND flag Sudeep Holla
2016-02-01 18:28 ` Sudeep Holla
2016-02-01 18:28 ` [PATCH 1/3] pinctrl: single: Use a separate lockdep class Sudeep Holla
2016-02-01 18:28 ` Sudeep Holla
2016-03-08 11:32 ` Grygorii Strashko
2016-03-08 11:32 ` Grygorii Strashko
2016-03-11 16:04 ` Linus Walleij
2016-03-11 16:04 ` Linus Walleij
2016-02-01 18:28 ` [PATCH 2/3] pinctrl: single: remove misuse of IRQF_NO_SUSPEND flag Sudeep Holla
2016-02-01 18:28 ` Sudeep Holla
2016-02-01 18:28 ` [PATCH 3/3] ARM: OMAP2+: " Sudeep Holla
2016-02-01 18:28 ` Sudeep Holla
2016-02-04 13:14 ` Grygorii Strashko
2016-02-04 13:14 ` Grygorii Strashko
2016-02-04 13:34 ` Sudeep Holla [this message]
2016-02-04 13:34 ` Sudeep Holla
2016-02-13 14:42 ` [PATCH 0/3] OMAP/pinmux: " Linus Walleij
2016-02-13 14:42 ` Linus Walleij
2016-02-15 10:01 ` Sudeep Holla
2016-02-15 10:01 ` Sudeep Holla
2016-02-15 15:27 ` Tony Lindgren
2016-02-15 15:27 ` Tony Lindgren
2016-03-08 11:31 ` Grygorii Strashko
2016-03-08 11:31 ` Grygorii Strashko
2016-03-08 17:09 ` Tony Lindgren
2016-03-08 17:09 ` 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=56B35364.8090104@arm.com \
--to=sudeep.holla@arm.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.