From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rajendra Nayak Subject: Re: [PATCH v2 3/5] regulator: helper routine to extract regulator_init_data Date: Tue, 25 Oct 2011 11:56:40 +0530 Message-ID: <4EA656A0.4010102@ti.com> References: <4EA00F7C.1080005@ti.com> <20111021082309.GA337@S2100-06.ap.freescale.net> <4EA13053.7080306@ti.com> <20111021115809.GB337@S2100-06.ap.freescale.net> <4EA4FF6B.2080906@ti.com> <20111024081706.GC8708@ponder.secretlab.ca> <20111024090228.GA1755@S2100-06.ap.freescale.net> <4EA52851.8000203@ti.com> <20111024091158.GB1755@S2100-06.ap.freescale.net> <4EA52C56.3080908@ti.com> <20111024134727.GF1755@S2100-06.ap.freescale.net> <4EA65073.7050205@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4EA65073.7050205@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Shawn Guo Cc: patches@linaro.org, tony@atomide.com, devicetree-discuss@lists.ozlabs.org, broonie@opensource.wolfsonmicro.com, linux-kernel@vger.kernel.org, Grant Likely , linux-omap@vger.kernel.org, lrg@ti.com, linux-arm-kernel@lists.infradead.org List-Id: linux-omap@vger.kernel.org On Tuesday 25 October 2011 11:30 AM, Rajendra Nayak wrote: > > In that case should you not be first converting the mfd driver to > register regulator devices using DT? > Thats what we did for OMAP, and hence we always have the of_node > populated when the regulator devices are probed. > See this patch from Benoit on how thats done for twl devices.. > http://marc.info/?l=linux-omap&m=131489864814428&w=2 Sorry, that was a link to an older version of the patch. Here's the latest one from Benoit which he did based on Arnd's suggestion of using of_platform_populate() directly. http://marc.info/?l=linux-omap&m=131705623822369&w=2 From mboxrd@z Thu Jan 1 00:00:00 1970 From: rnayak@ti.com (Rajendra Nayak) Date: Tue, 25 Oct 2011 11:56:40 +0530 Subject: [PATCH v2 3/5] regulator: helper routine to extract regulator_init_data In-Reply-To: <4EA65073.7050205@ti.com> References: <4EA00F7C.1080005@ti.com> <20111021082309.GA337@S2100-06.ap.freescale.net> <4EA13053.7080306@ti.com> <20111021115809.GB337@S2100-06.ap.freescale.net> <4EA4FF6B.2080906@ti.com> <20111024081706.GC8708@ponder.secretlab.ca> <20111024090228.GA1755@S2100-06.ap.freescale.net> <4EA52851.8000203@ti.com> <20111024091158.GB1755@S2100-06.ap.freescale.net> <4EA52C56.3080908@ti.com> <20111024134727.GF1755@S2100-06.ap.freescale.net> <4EA65073.7050205@ti.com> Message-ID: <4EA656A0.4010102@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tuesday 25 October 2011 11:30 AM, Rajendra Nayak wrote: > > In that case should you not be first converting the mfd driver to > register regulator devices using DT? > Thats what we did for OMAP, and hence we always have the of_node > populated when the regulator devices are probed. > See this patch from Benoit on how thats done for twl devices.. > http://marc.info/?l=linux-omap&m=131489864814428&w=2 Sorry, that was a link to an older version of the patch. Here's the latest one from Benoit which he did based on Arnd's suggestion of using of_platform_populate() directly. http://marc.info/?l=linux-omap&m=131705623822369&w=2 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753367Ab1JYG0u (ORCPT ); Tue, 25 Oct 2011 02:26:50 -0400 Received: from na3sys009aog105.obsmtp.com ([74.125.149.75]:33817 "EHLO na3sys009aog105.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751419Ab1JYG0t (ORCPT ); Tue, 25 Oct 2011 02:26:49 -0400 Message-ID: <4EA656A0.4010102@ti.com> Date: Tue, 25 Oct 2011 11:56:40 +0530 From: Rajendra Nayak User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12 MIME-Version: 1.0 To: Shawn Guo CC: Grant Likely , broonie@opensource.wolfsonmicro.com, patches@linaro.org, tony@atomide.com, devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, lrg@ti.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 3/5] regulator: helper routine to extract regulator_init_data References: <4EA00F7C.1080005@ti.com> <20111021082309.GA337@S2100-06.ap.freescale.net> <4EA13053.7080306@ti.com> <20111021115809.GB337@S2100-06.ap.freescale.net> <4EA4FF6B.2080906@ti.com> <20111024081706.GC8708@ponder.secretlab.ca> <20111024090228.GA1755@S2100-06.ap.freescale.net> <4EA52851.8000203@ti.com> <20111024091158.GB1755@S2100-06.ap.freescale.net> <4EA52C56.3080908@ti.com> <20111024134727.GF1755@S2100-06.ap.freescale.net> <4EA65073.7050205@ti.com> In-Reply-To: <4EA65073.7050205@ti.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 25 October 2011 11:30 AM, Rajendra Nayak wrote: > > In that case should you not be first converting the mfd driver to > register regulator devices using DT? > Thats what we did for OMAP, and hence we always have the of_node > populated when the regulator devices are probed. > See this patch from Benoit on how thats done for twl devices.. > http://marc.info/?l=linux-omap&m=131489864814428&w=2 Sorry, that was a link to an older version of the patch. Here's the latest one from Benoit which he did based on Arnd's suggestion of using of_platform_populate() directly. http://marc.info/?l=linux-omap&m=131705623822369&w=2