Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752495AbaJQJUF (ORCPT ); Fri, 17 Oct 2014 05:20:05 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:64901 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752241AbaJQJUB (ORCPT ); Fri, 17 Oct 2014 05:20:01 -0400 Date: Fri, 17 Oct 2014 18:19:50 +0900 From: Gyungoh Yoo To: Mark Brown Cc: sameo@linux.intel.com, lee.jones@linaro.org, jg1.han@samsung.com, cooloney@gmail.com, lgirdwood@gmail.com, jack.yoo@skyworksinc.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, grant.likely@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, pawel.moll@arm.com, heiko@sntech.de, jason@lakedaemon.net, shawn.guo@freescale.com, treding@nvidia.com, florian.vaussard@epfl.ch, trivial@kernel.org, linux@roeck-us.net, andrew@lunn.ch, jic23@kernel.org Subject: Re: [RESUBMIT PATCH v4 7/8] regulator: sky81452: Add compatible string for device binding Message-ID: <20141017091950.GA3233@jack-ThinkPad-T520> References: <1412657745-7812-1-git-send-email-jack.yoo@skyworksinc.com> <1413179262-27636-1-git-send-email-jack.yoo@skyworksinc.com> <1413179262-27636-8-git-send-email-jack.yoo@skyworksinc.com> <20141013103512.GJ27755@sirena.org.uk> <20141014011112.GB2751@jack-ThinkPad-T520> <20141014075606.GN27755@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20141014075606.GN27755@sirena.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 14, 2014 at 09:56:06AM +0200, Mark Brown wrote: > On Tue, Oct 14, 2014 at 10:11:12AM +0900, Gyungoh Yoo wrote: > > On Mon, Oct 13, 2014 at 12:35:12PM +0200, Mark Brown wrote: > > > > If you're doing anything here you should convert the code to use the > > > simplified interface for parsing regulator data based on putting the > > > subnode name and regualtor name in the regulator descriptor. > > > Thank you for the review. > > > The driver has of_device_id. > > > static const struct of_device_id sky81452_reg_of_match[] = { > > { .compatible = "skyworks,sky81452-regulator", }, > > { } > > }; > > > And the MFD adds the driver with of_compatible="skyworks,sky81452-regulator". > > MFD core maps the device node and the regulator driver does > > not need to parse the subnode name. > > No, that's for the device (and as I say I don't think this is a good > idea). I'm talking about the parsing of the constraints from the DT. Wow. I understand. I missed .supply_name. I think I need something like below, before devm_regulator_register(). config->supply_name = init_data->constraints.name; I will resubmit it. Thank you so much. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/