[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120108233820.GH13679@sortiz-mobl>
Date: Mon, 9 Jan 2012 00:38:20 +0100
From: Samuel Ortiz <sameo@...ux.intel.com>
To: "Cousson, Benoit" <b-cousson@...com>
Cc: Grant Likely <grant.likely@...retlab.ca>, rob.herring@...xeda.com,
tony@...mide.com, linux-omap@...r.kernel.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
devicetree-discuss@...ts.ozlabs.org, linux-i2c@...r.kernel.org,
ben-linux@...ff.org, Balaji T K <balajitk@...com>,
Graeme Gregory <gg@...mlogic.co.uk>
Subject: Re: [PATCH v4 03/12] mfd: twl-core: Add initial DT support for
twl4030/twl6030
Hi Benoit,
On Tue, Jan 03, 2012 at 03:09:49PM +0100, Cousson, Benoit wrote:
> On 1/2/2012 10:04 AM, Grant Likely wrote:
> > On Thu, Dec 22, 2011 at 03:56:37PM +0100, Benoit Cousson wrote:
> >> Add initial device-tree support for twl familly chips.
> >> The current version is missing the regulator entries due
> >> to the lack of DT regulator bindings for the moment.
> >> Only the simple sub-modules that do not depend on
> >> platform_data information can be initialized properly.
> >>
> >> Add irqdomain support.
> >>
> >> Add documentation for the Texas Instruments TWL Integrated Chip.
> >>
> >> Signed-off-by: Benoit Cousson<b-cousson@...com>
> >> Cc: Balaji T K<balajitk@...com>
> >> Cc: Graeme Gregory<gg@...mlogic.co.uk>
> >> Cc: Samuel Ortiz<sameo@...ux.intel.com>
> >> ---
> >> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> >> index f1391c2..f0de088 100644
> >> --- a/drivers/mfd/Kconfig
> >> +++ b/drivers/mfd/Kconfig
> >> @@ -200,6 +200,7 @@ config MENELAUS
> >> config TWL4030_CORE
> >> bool "Texas Instruments TWL4030/TWL5030/TWL6030/TPS659x0 Support"
> >> depends on I2C=y&& GENERIC_HARDIRQS
> >> + select IRQ_DOMAIN
> >
> > As discussed on linux-next, this breaks powerpc. Drivers cannot select
> > IRQ_DOMAIN, it can only be selected by architectures. Drivers must depend
> > on it instead.
>
> OK, good to know. The previous version was already breaking non-ARM platform because the IRQ_DOMAIN was not defined, hence this update.
> I was able to check that this patch was fixing at least x86... but did not have any way to check the PPC build.
>
> To be honest, I did not fully understand that this flag was there because some arch does not support IRQ domain yet and thus it should be selected at arch level.
>
> Samuel,
> Here is the updated version, and hopefully the last one, including Grant's fix.
>
Thanks, I applied it now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists