From: Andrew Duggan <aduggan@synaptics.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] HID: i2c-hid: Only disable irq wake if it was successfully enabled during suspend
Date: Tue, 28 Jul 2015 12:55:47 -0700 [thread overview]
Message-ID: <55B7DE43.9090008@synaptics.com> (raw)
In-Reply-To: <20150728113337.GD11956@lahna.fi.intel.com>
On 07/28/2015 04:33 AM, Mika Westerberg wrote:
> On Mon, Jul 27, 2015 at 05:08:06PM -0700, Andrew Duggan wrote:
>> On at least one platform the kernel prints a warning on resume saying
>> "Unbalanced IRQ 37 wake disable". This is because enable_irq_wake in the
>> suspend function is failing. This patch checks to see if the call to
>> enable_irq_wake succeeded before calling disable_irq_wake.
> While this looks okay, I'm wondering if this can also be fixed from the
> irq chip side by setting IRQCHIP_SKIP_SET_WAKE to .flags, given that the
> driver does not provide such function?
Yes, setting IRQCHIP_SKIP_SET_WAKE does fix the problem. After looking
into it a bit more it turns out commit 5613570 already fixed the issue.
My test system was running an older kernel which didn't include it.
Applying 5613570 fixed this particular issue. Thanks for pointing that
out, now I have a better understanding of why enable_irq_wake was
failing in this instance.
For this patch, I think it is still a good idea to check the return code
of enable_irq_wake. In theory, an irqchip which does have a irq_set_wake
callback set could return an error. I can update the commit comment, add
a warning, and submit a v2.
Thanks,
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Duggan <aduggan@synaptics.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: <linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] HID: i2c-hid: Only disable irq wake if it was successfully enabled during suspend
Date: Tue, 28 Jul 2015 12:55:47 -0700 [thread overview]
Message-ID: <55B7DE43.9090008@synaptics.com> (raw)
In-Reply-To: <20150728113337.GD11956@lahna.fi.intel.com>
On 07/28/2015 04:33 AM, Mika Westerberg wrote:
> On Mon, Jul 27, 2015 at 05:08:06PM -0700, Andrew Duggan wrote:
>> On at least one platform the kernel prints a warning on resume saying
>> "Unbalanced IRQ 37 wake disable". This is because enable_irq_wake in the
>> suspend function is failing. This patch checks to see if the call to
>> enable_irq_wake succeeded before calling disable_irq_wake.
> While this looks okay, I'm wondering if this can also be fixed from the
> irq chip side by setting IRQCHIP_SKIP_SET_WAKE to .flags, given that the
> driver does not provide such function?
Yes, setting IRQCHIP_SKIP_SET_WAKE does fix the problem. After looking
into it a bit more it turns out commit 5613570 already fixed the issue.
My test system was running an older kernel which didn't include it.
Applying 5613570 fixed this particular issue. Thanks for pointing that
out, now I have a better understanding of why enable_irq_wake was
failing in this instance.
For this patch, I think it is still a good idea to check the return code
of enable_irq_wake. In theory, an irqchip which does have a irq_set_wake
callback set could return an error. I can update the commit comment, add
a warning, and submit a v2.
Thanks,
Andrew
next prev parent reply other threads:[~2015-07-28 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 0:08 [PATCH] HID: i2c-hid: Only disable irq wake if it was successfully enabled during suspend Andrew Duggan
2015-07-28 0:08 ` Andrew Duggan
2015-07-28 11:33 ` Mika Westerberg
2015-07-28 19:55 ` Andrew Duggan [this message]
2015-07-28 19:55 ` Andrew Duggan
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=55B7DE43.9090008@synaptics.com \
--to=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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.