From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: ASoC: multi-component updates from RFC
Date: Thu, 22 Jul 2010 14:07:24 +0100 [thread overview]
Message-ID: <1279804044.3083.49.camel@odin> (raw)
In-Reply-To: <1279786704.3083.22.camel@odin>
On Thu, 2010-07-22 at 09:18 +0100, Liam Girdwood wrote:
> On Thu, 2010-07-22 at 09:27 +0300, Peter Ujfalusi wrote:
> > The name for the drivers/mfd/twl4030-codec.c is chosen, because the TRM refers
> > to this block as codec (audio + vibra).
> > We could go, and rename however this mfd driver to twl4030-audio (since the TRM
> > randomly refers to audio block instead of codec).
> > Than we can have twl4030-codec as device name for the soc codec, and twl4030-
> > vibra for the vibra.
> >
>
> Agreed, I'll make that change.
Pushed to git. I also fixed a naming bug in the mcbsp DAI devices too.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
prev parent reply other threads:[~2010-07-22 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 12:31 ASoC: multi-component updates from RFC Liam Girdwood
2010-07-22 6:27 ` Peter Ujfalusi
2010-07-22 8:18 ` Liam Girdwood
2010-07-22 13:07 ` Liam Girdwood [this message]
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=1279804044.3083.49.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@nokia.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