[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <331ABD5ECB02734CA317220B2BBEABC13E9F98DB@DBDE01.ent.ti.com>
Date: Thu, 19 Jul 2012 12:35:24 +0000
From: "AnilKumar, Chimata" <anilkumar@...com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: "rdunlap@...otime.net" <rdunlap@...otime.net>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: RE: [PATCH] regulator: tps65217: fix build error if REGULATOR is
not enabled
Hi Mark,
On Wed, Jul 18, 2012 at 15:30:13, Mark Brown wrote:
> On Wed, Jul 18, 2012 at 09:55:57AM +0000, AnilKumar, Chimata wrote:
>
> > Regulators platform data is added to platform device in MFD driver, which we
> > need for regulator driver, of_regulator_match() is used to check the regulator
> > consumers if we pass DT data. If we do not enable CONFIG_REGULATOR then
> > of_regulator_match() is not exported, so we see this error.
>
> Why are you doing that in the MFD driver?
>
I got your point, I referred tps6586x driver while developing the initial driver.
Based on tps6586x MFD driver I added REGULATOR flag. I think tps6586x MFD driver
need to be cleaned up.
I will submit a patch to make tps65217 MFD driver independent of REGULATOR
framework.
Thanks
AnilKumar--
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