From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: [PATCH 4/4] ASoC: TWL4030: Driver registration via twl4030_codec MFD
Date: Tue, 20 Oct 2009 12:51:06 +0100 [thread overview]
Message-ID: <20091020115106.GB2909@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200910201430.49223.peter.ujfalusi@nokia.com>
On Tue, Oct 20, 2009 at 02:30:49PM +0300, Peter Ujfalusi wrote:
> In patch 1, the register definitions had to be added, so that the twl4030_codec
> driver knows the registers (and there could be the vibra driver placed
> separately from the soc codec driver).
> In patch 3, where I modify the soc codec driver to use the new method, than I
> remove the definitions and use the existing header file, introduced by the first
> patch.
> All in all, after each patch the kernel can be builds, boots and works as
> before.
Sure, though I suspect patch 3 could just be split in two happily with
an include. I don't really mind either way. If you are going to keep
them as one patch it'd be good to call out the move in the changelog.
> > You've also got the bias being brought up when the ASoC system comes up
> > rather than when the driver comes up. To be honest it doesn't really
> > make any difference either way, it's just slightly different to other
> > drivers.
> I was thinking that if you built the kernel with SND_SOC_ALL_CODECS on OMAP
> platform for some reason and you don't actually use the twl4030 as audio device
> -> no machine driver, which would use it, than the codec part would be off.
> But yes, probably I can move the povering up to the probe function.
That's a good enough reason to leave things as they are, though really
if you're building SND_SOC_ALL_CODECs in a production system you're
being a bit strange.
> > > +MODULE_ALIAS("platform:twl4030_codec:audio");
> > Is that second colon right given...
> I'm not sure about it at all either. I did not found any other 'nested MFD'
> drivers around, so this is just a guess
> Should it be:
> +MODULE_ALIAS("platform:twl4030_codec_audio");
Yes. The aliasing makes no reference to the parents of the device, it
only cares about the device name - for the purposes of module loading
and driver matching it's identical to any other platform device.
next prev parent reply other threads:[~2009-10-20 11:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 12:42 [PATCH 0/4] twl4030 codec as MFD device Peter Ujfalusi
2009-10-19 12:42 ` [PATCH 1/4] MFD: twl4030: add twl4030_codec MFD as a new child to the core Peter Ujfalusi
2009-10-19 12:42 ` [PATCH 2/4] OMAP: Platform support for twl4030_codec MFD Peter Ujfalusi
2009-10-19 12:42 ` [PATCH 3/4] ASoC: TWL4030: Only update the needed bits in *set_dai_sysclk Peter Ujfalusi
2009-10-19 12:42 ` [PATCH 4/4] ASoC: TWL4030: Driver registration via twl4030_codec MFD Peter Ujfalusi
2009-10-20 10:25 ` Mark Brown
2009-10-20 11:30 ` Peter Ujfalusi
2009-10-20 11:51 ` Mark Brown [this message]
2009-10-20 12:01 ` Peter Ujfalusi
2009-10-19 12:55 ` [PATCH 3/4] ASoC: TWL4030: Only update the needed bits in *set_dai_sysclk Mark Brown
2009-10-19 12:59 ` Peter Ujfalusi
2009-10-20 19:01 ` [PATCH 2/4] OMAP: Platform support for twl4030_codec MFD Tony Lindgren
2009-10-20 10:03 ` [PATCH 1/4] MFD: twl4030: add twl4030_codec MFD as a new child to the core Mark Brown
2009-10-20 11:16 ` Peter Ujfalusi
2009-10-21 23:13 ` Samuel Ortiz
2009-10-22 6:04 ` Peter Ujfalusi
2009-10-22 7:57 ` Samuel Ortiz
2009-10-22 10:55 ` Mark Brown
2009-10-22 11:02 ` Peter Ujfalusi
2009-10-21 8:56 ` [PATCH 0/4] twl4030 codec as MFD device Peter Ujfalusi
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=20091020115106.GB2909@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox