From: Sebastian Reichel <sre@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] Regmap IRQ fix and related changes CPCAP
Date: Wed, 22 Mar 2017 03:22:10 +0100 [thread overview]
Message-ID: <20170322022210.7u4taeepbraf6jaq@earth> (raw)
In-Reply-To: <20170317003633.7361-1-tony@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Hi,
On Thu, Mar 16, 2017 at 05:36:29PM -0700, Tony Lindgren wrote:
> Here are few fixes to make CPCAP PMIC interrupts work reliably when
> used with multiple drivers. While working on the ADC, charger and
> USB PHY drivers I noticed that the PMIC interrupt to the SoC would
> eventually stop working.
>
> All these can wait for v4.12 merge window as these issues don't show
> up currently. Two of the patches are also harmless currently, so I've
> kept them in this series to avoid pointless merge conflicts.
The series is
Tested-by: Sebastian Reichel <sre@kernel.org>
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-22 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 0:36 [PATCH 0/4] Regmap IRQ fix and related changes CPCAP Tony Lindgren
2017-03-17 0:36 ` [PATCH 1/4] regmap: irq: Fix lost interrupts by introducing handle_reread Tony Lindgren
2017-03-20 15:14 ` Charles Keepax
2017-03-20 15:33 ` Tony Lindgren
2017-03-21 9:23 ` Charles Keepax
2017-03-21 15:41 ` Tony Lindgren
2017-03-21 16:43 ` Charles Keepax
2017-03-17 0:36 ` [PATCH 2/4] mfd: cpcap: Use handle_reread flag for interrupts Tony Lindgren
2017-03-17 0:36 ` [PATCH 3/4] mfd: cpcap: Use ack_invert interrupts Tony Lindgren
2017-03-17 0:36 ` [PATCH 4/4] mfd: cpcap: Fix bad use of IRQ sense register Tony Lindgren
2017-03-19 2:01 ` Sebastian Reichel
2017-03-19 16:07 ` Tony Lindgren
2017-03-20 10:47 ` Lee Jones
2017-03-22 2:22 ` Sebastian Reichel [this message]
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=20170322022210.7u4taeepbraf6jaq@earth \
--to=sre@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox