From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Cousson, Benoit" Subject: Re: [GIT PULL] ARM: OMAP: IRQ domain support for INTC Date: Mon, 5 Mar 2012 16:19:26 +0100 Message-ID: <4F54D97E.4070805@ti.com> References: <4F4BB0FB.3040308@ti.com> <20120228234837.GH18901@atomide.com> <4F4E4F1D.7020109@ti.com> <20120305135838.GA2108@localhost> <4F54CCBD.2080802@ti.com> <20120305150351.GB2108@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:50149 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932480Ab2CEPTe (ORCPT ); Mon, 5 Mar 2012 10:19:34 -0500 In-Reply-To: <20120305150351.GB2108@localhost> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Johan Hovold Cc: Tony Lindgren , linux-omap , "linux-arm-kernel@lists.infradead.org" , Grant Likely On 3/5/2012 4:03 PM, Johan Hovold wrote: > On Mon, Mar 05, 2012 at 03:25:01PM +0100, Cousson, Benoit wrote: >> On 3/5/2012 2:58 PM, Johan Hovold wrote: >>> On Wed, Feb 29, 2012 at 05:15:25PM +0100, Cousson, Benoit wrote: >>>> On 2/29/2012 12:48 AM, Tony Lindgren wrote: >>>>> * Cousson, Benoit [120227 08:04]: >>>>> Hmm, looks like this now produces the following warning at least on omap3: >>>> >>>> Yes, Rajendra has just reported that issue with linux-next. >>> >>> I'm getting the same warning and initialisation failure with 3.3-rc6 on >>> overo. Are these fixes queued up for 3.3 (and not just 3.4) somewhere? >> >> It is under review, I posted the series last Friday: >> mfd: twl: Fix for irqdomain/next + SPARSE_IRQ + MMC card detect >> >> It will be anyway material for 3.4 since it is in linux-next. > > Yes, I noted that there was a fix against linux-next. My question was > whether any fix is planned for 3.3 as twl4030 is broken with SPARSE_IRQ > enabled. > > Disabling SPARSE_IRQ will be the only workaround until 3.4 is out then? Mmm, but is SPARSE_IRQ used to work before on OMAP3? Benoit From mboxrd@z Thu Jan 1 00:00:00 1970 From: b-cousson@ti.com (Cousson, Benoit) Date: Mon, 5 Mar 2012 16:19:26 +0100 Subject: [GIT PULL] ARM: OMAP: IRQ domain support for INTC In-Reply-To: <20120305150351.GB2108@localhost> References: <4F4BB0FB.3040308@ti.com> <20120228234837.GH18901@atomide.com> <4F4E4F1D.7020109@ti.com> <20120305135838.GA2108@localhost> <4F54CCBD.2080802@ti.com> <20120305150351.GB2108@localhost> Message-ID: <4F54D97E.4070805@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 3/5/2012 4:03 PM, Johan Hovold wrote: > On Mon, Mar 05, 2012 at 03:25:01PM +0100, Cousson, Benoit wrote: >> On 3/5/2012 2:58 PM, Johan Hovold wrote: >>> On Wed, Feb 29, 2012 at 05:15:25PM +0100, Cousson, Benoit wrote: >>>> On 2/29/2012 12:48 AM, Tony Lindgren wrote: >>>>> * Cousson, Benoit [120227 08:04]: >>>>> Hmm, looks like this now produces the following warning at least on omap3: >>>> >>>> Yes, Rajendra has just reported that issue with linux-next. >>> >>> I'm getting the same warning and initialisation failure with 3.3-rc6 on >>> overo. Are these fixes queued up for 3.3 (and not just 3.4) somewhere? >> >> It is under review, I posted the series last Friday: >> mfd: twl: Fix for irqdomain/next + SPARSE_IRQ + MMC card detect >> >> It will be anyway material for 3.4 since it is in linux-next. > > Yes, I noted that there was a fix against linux-next. My question was > whether any fix is planned for 3.3 as twl4030 is broken with SPARSE_IRQ > enabled. > > Disabling SPARSE_IRQ will be the only workaround until 3.4 is out then? Mmm, but is SPARSE_IRQ used to work before on OMAP3? Benoit