From: Samuel Ortiz <sameo@linux.intel.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: NeilBrown <neilb@suse.de>, Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] fixes for twl4030-irq in mainline
Date: Tue, 13 Dec 2011 21:52:56 +0100 [thread overview]
Message-ID: <20111213205256.GG2796@sortiz-mobl> (raw)
In-Reply-To: <CAMP44s1D+HXP_prHVwEztLCd1XJpnzukFeNKH_xEZrq06jEouA@mail.gmail.com>
Hi Felipe,
On Tue, Dec 13, 2011 at 04:12:02PM +0200, Felipe Contreras wrote:
> Hi,
>
> On Mon, Dec 12, 2011 at 7:38 PM, Samuel Ortiz <sameo@linux.intel.com> wrote:
> > On Sun, Nov 27, 2011 at 07:17:41AM +1100, NeilBrown wrote:
> >> The recent tidying up of twl4030-irq seems to have left it broken.
> >> At least it doesn't work for me on my gta04 (www.gta04.org). The
> >> first interrupt from the device freezes the whole system (by being
> >> constantly delivered)
> >>
> >> The following 4 patches make it work for me and addresses some other
> >> less critical issues like a typo in a comment :-)
> >
> > Thanks, I applied all 4 of them.
>
> Did you apply them for 3.2 or 3.3? Without the first patch any system
> that has a twl4030 chip will immediately hang on the first interrupt,
> and many functions of twl4030 will just not work without the second
> one.
Thanks for the heads up. I applied the first 2 patches to my for-linus branch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: NeilBrown <neilb@suse.de>, Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] fixes for twl4030-irq in mainline
Date: Tue, 13 Dec 2011 21:52:56 +0100 [thread overview]
Message-ID: <20111213205256.GG2796@sortiz-mobl> (raw)
In-Reply-To: <CAMP44s1D+HXP_prHVwEztLCd1XJpnzukFeNKH_xEZrq06jEouA@mail.gmail.com>
Hi Felipe,
On Tue, Dec 13, 2011 at 04:12:02PM +0200, Felipe Contreras wrote:
> Hi,
>
> On Mon, Dec 12, 2011 at 7:38 PM, Samuel Ortiz <sameo@linux.intel.com> wrote:
> > On Sun, Nov 27, 2011 at 07:17:41AM +1100, NeilBrown wrote:
> >> The recent tidying up of twl4030-irq seems to have left it broken.
> >> At least it doesn't work for me on my gta04 (www.gta04.org). The
> >> first interrupt from the device freezes the whole system (by being
> >> constantly delivered)
> >>
> >> The following 4 patches make it work for me and addresses some other
> >> less critical issues like a typo in a comment :-)
> >
> > Thanks, I applied all 4 of them.
>
> Did you apply them for 3.2 or 3.3? Without the first patch any system
> that has a twl4030 chip will immediately hang on the first interrupt,
> and many functions of twl4030 will just not work without the second
> one.
Thanks for the heads up. I applied the first 2 patches to my for-linus branch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-12-13 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 20:17 [PATCH 0/4] fixes for twl4030-irq in mainline NeilBrown
2011-11-26 20:17 ` [PATCH 3/4] twl4030-irq: set tertiary interrupts to be nested/threaded NeilBrown
2011-11-26 20:17 ` [PATCH 4/4] twl4030-irq: fix typo NeilBrown
2011-11-26 20:17 ` [PATCH 1/4] twl4030-irq: Base interrupt must be one-shot NeilBrown
2011-11-26 20:17 ` [PATCH 2/4] twl4030-irq: use request_threaded_irq in place of irq_set_chained_handler NeilBrown
2011-12-07 18:34 ` [PATCH 0/4] fixes for twl4030-irq in mainline Felipe Contreras
2011-12-12 17:38 ` Samuel Ortiz
2011-12-12 21:39 ` NeilBrown
2011-12-13 20:24 ` Samuel Ortiz
2011-12-13 14:12 ` Felipe Contreras
2011-12-13 20:52 ` Samuel Ortiz [this message]
2011-12-13 20:52 ` Samuel Ortiz
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=20111213205256.GG2796@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=balbi@ti.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
/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.