Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756104Ab1FFJzs (ORCPT ); Mon, 6 Jun 2011 05:55:48 -0400 Received: from mho-04-ewr.mailhop.org ([204.13.248.74]:33309 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751199Ab1FFJzq (ORCPT ); Mon, 6 Jun 2011 05:55:46 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 72.249.23.125 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX198uBLHyuIaoNssH++HpASb Date: Mon, 6 Jun 2011 12:55:40 +0300 From: Tony Lindgren To: Peter Ujfalusi Cc: "Girdwood, Liam" , Mark Brown , Samuel Ortiz , Dmitry Torokhov , "linux-input@vger.kernel.org" , "linux-omap@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "alsa-devel@alsa-project.org" Subject: Re: [PATCH 3/8] MFD: twl4030-audio: Rename platform data Message-ID: <20110606095540.GR8696@atomide.com> References: <1306927051-8937-1-git-send-email-peter.ujfalusi@ti.com> <201106020915.46491.peter.ujfalusi@ti.com> <20110603080819.GK8696@atomide.com> <201106031638.26094.peter.ujfalusi@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201106031638.26094.peter.ujfalusi@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1683 Lines: 37 * Peter Ujfalusi [110603 16:34]: > On Friday 03 June 2011 11:08:22 Tony Lindgren wrote: > > Yeah if it gets big then a separate file is better. Also, if we have > > a common init function for twl, then it's easy to add the board specific > > device tree initialization to that too and just leave out the calls to > > omap_pmic_init from board-*.c files. > > I have parsed the board files for a pattern. > There are some, but I have my doubts as well: > We have eight platform data members in twl4030_platform_data for child > devices. > USB, and audio/codec configuration might worth to move out (since most of the > board does not have fine tuned parameters for codec). > > The majority of the code related to pmic is coming from regulator setups, I > can see similarities, but there are differences here and there, which makes > the common configuration mostly useless (different peripherals, boot loader > diffs, etc). Yeah we still need the board specific data passed for sure. > Having said that, I try to create a wrapper for omap_pmic_init, which can > replace the current omap2/3/4_pmic_init, with that we can use common config > for USB, audio, and some selected few regulators initially. > Later other parts might be possible to consolidate as well. > I'm going to call this new wrapper for now omap2/3/4_pmic_config. > > Is this a good way to approach this issue? Sounds good to me! Tony -- 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/