[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120806145702.GB29272@sirena.org.uk>
Date: Mon, 6 Aug 2012 15:57:03 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Dongjin Kim <tobetter@...il.com>
Cc: Kukjin Kim <kgene.kim@...sung.com>,
Russell King <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Jon Medhurst <tixy@...t.co.uk>, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
Uwe Kleine-K??nig <u.kleine-koenig@...gutronix.de>,
Shawn Guo <shawn.guo@...aro.org>,
linux-arm-kernel@...ts.infradead.org,
Dongjin Kim <dongjin.kim@...eeyamobility.net>
Subject: Re: [PATCH] ODROID-X: hkdk4412: Add new hardware based on
Exynos4412
On Mon, Aug 06, 2012 at 11:10:51PM +0900, Dongjin Kim wrote:
> +static struct regulator_consumer_supply __initdata max77686_buck4_consumer[] = {
> + REGULATOR_SUPPLY("vdd_g3d", NULL),
> +};
Not that it matters much since new board drivers won't get merged but
all your regulator setup here is problematic. These look like names
from the board schematic as opposed to mappings of the supplies onto the
consumer devices.
> +static struct regulator_init_data __initdata max77686_buck1_data = {
> + .constraints = {
> + .name = "vdd_mif range",
This would normally just be the name of the supply for display purposes.
--
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