From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: "Girdwood, Liam" <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 3/8] MFD: twl4030-audio: Rename platform data
Date: Mon, 6 Jun 2011 12:55:40 +0300 [thread overview]
Message-ID: <20110606095540.GR8696@atomide.com> (raw)
In-Reply-To: <201106031638.26094.peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [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
next prev parent reply other threads:[~2011-06-06 9:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 11:17 [PATCH 0/8] MFD/ASoC: TWL4030/TWL6040 changes Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 1/8] MFD: twl4030-codec: Rename internals from codec to audio Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 2/8] MFD: twl4030-codec -> twl4030-audio: Rename the driver Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 3/8] MFD: twl4030-audio: Rename platform data Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 12:07 ` Tony Lindgren
2011-06-01 12:54 ` Peter Ujfalusi
2011-06-01 12:54 ` Peter Ujfalusi
2011-06-01 13:00 ` Tony Lindgren
2011-06-01 13:00 ` Tony Lindgren
2011-06-01 13:17 ` Peter Ujfalusi
2011-06-01 13:17 ` Peter Ujfalusi
2011-06-01 13:38 ` Tony Lindgren
2011-06-02 6:15 ` Peter Ujfalusi
2011-06-02 6:15 ` Peter Ujfalusi
2011-06-03 8:08 ` Tony Lindgren
2011-06-03 8:08 ` Tony Lindgren
2011-06-03 13:38 ` Peter Ujfalusi
2011-06-03 13:38 ` Peter Ujfalusi
2011-06-06 9:55 ` Tony Lindgren [this message]
2011-06-01 11:17 ` [PATCH 4/8] mfd: twl6040: Add initial support Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 13:47 ` T Krishnamoorthy, Balaji
2011-06-01 13:47 ` T Krishnamoorthy, Balaji
2011-06-03 16:44 ` Peter Ujfalusi
2011-06-03 16:44 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 5/8] ASoC: twl6040: Convert into TWL6040 MFD child Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 6/8] MFD: twl6040: Change platform data for soc codec driver Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 7/8] input: Add initial support for TWL6040 vibrator Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-01 11:17 ` [PATCH 8/8] OMAP4: SDP4430: Add twl6040 vibrator platform support Peter Ujfalusi
2011-06-01 11:17 ` Peter Ujfalusi
2011-06-02 8:29 ` [PATCH 0/8] MFD/ASoC: TWL4030/TWL6040 changes Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110606095540.GR8696@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.