public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] mfd: tps65218: make INT[12] and STATUS registers volatile
Date: Fri, 16 Jan 2015 16:57:32 -0600	[thread overview]
Message-ID: <20150116225732.GB6254@saruman> (raw)
In-Reply-To: <20150114170716.GL2419@atomide.com>

Hi,

On Wed, Jan 14, 2015 at 09:07:17AM -0800, Tony Lindgren wrote:
> > > > > STATUS register can be modified by the HW, so we
> > > > > should bypass cache because of that.
> > > > > 
> > > > > In the case of INT[12] registers, they are the ones
> > > > > that actually clear the IRQ source at the time they
> > > > > are read. If we rely on the cache for them, we will
> > > > > never be able to clear the interrupt, which will cause
> > > > > our IRQ line to be disabled due to IRQ throttling.
> > > > > 
> > > > > Fixes: 44b4dc6 mfd: tps65218: Add driver for the TPS65218 PMIC
> > > > > Cc: <stable@vger.kernel.org> # v3.15+
> > > > > Cc: Keerthy <j-keerthy@ti.com>
> > > > > Cc: Lee Jones <lee.jones@linaro.org>
> > > > > Signed-off-by: Felipe Balbi <balbi@ti.com>
> > > > 
> > > > ping
> > > 
> > > another ping. Without this and the following patch TPS65218 power button
> > > driver which was already applied by Dmitry, won't work.
> > 
> > Anybody ? -rc4 is out and tps65218 is still broken because nobody has
> > acted on these two patches. All other patches which are meant for 3.20
> > merge window are applied and because of these pending, those patches
> > won't work.
> 
> Lee, are you planning to pick these two drivers/mfd patches?

Samuel, Lee, is someone planning on picking these two patches up ?
v3.19 remains broken.

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150116/5feee76e/attachment.sig>

  reply	other threads:[~2015-01-16 22:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 19:28 [PATCH 0/5] AM437x SK: Add power-button support Felipe Balbi
2014-12-26 19:28 ` [PATCH 1/5] mfd: tps65218: make INT[12] and STATUS registers volatile Felipe Balbi
2015-01-06 17:37   ` Felipe Balbi
2015-01-08 16:25     ` Felipe Balbi
2015-01-12 16:46       ` Felipe Balbi
2015-01-14 17:07         ` Tony Lindgren
2015-01-16 22:57           ` Felipe Balbi [this message]
2015-01-18  9:52   ` Lee Jones
2015-01-19 14:41     ` Felipe Balbi
2014-12-26 19:28 ` [PATCH 2/5] mfd: tps65218: make INT1 our status_base register Felipe Balbi
2015-01-06 17:37   ` Felipe Balbi
2015-01-18  9:52   ` Lee Jones
2014-12-26 19:28 ` [PATCH 3/5] input: misc: add tps65218 power button driver Felipe Balbi
2014-12-26 19:33   ` Felipe Balbi
2014-12-26 23:41   ` Dmitry Torokhov
2014-12-27  3:36     ` [PATCH v2 " Felipe Balbi
2014-12-28  4:50       ` Dmitry Torokhov
2014-12-26 19:28 ` [PATCH 4/5] arm: boot: dts: am437x-sk: add power button binding Felipe Balbi
2015-01-08  0:09   ` Tony Lindgren
2014-12-26 19:28 ` [PATCH 5/5] arm: omap2plus_defconfig: enable TPS65218 power button Felipe Balbi
2015-01-08  0:55   ` 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=20150116225732.GB6254@saruman \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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