From: Liam Girdwood <lrg@slimlogic.co.uk>
To: peter.ujfalusi@nokia.com
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [RFC 04/16] ASoC: multi-component - TI CODECs
Date: Mon, 05 Jul 2010 22:15:46 +0100 [thread overview]
Message-ID: <1278364546.3258.215.camel@odin> (raw)
In-Reply-To: <C358A26273CF2948B8BCDBA661A581782A6FBF945E@NOK-EUMSG-03.mgdnok.nokia.com>
On Wed, 2010-06-30 at 14:08 +0200, peter.ujfalusi@nokia.com wrote:
> Hello Liam,
>
> I'm on holiday, and I have limited access to e-mail, but I did taken a brief look at the series..
Same here, I'm just back from some travels....
> I have few question:
> Is the support for the former codec->idle_bias_off is gone? This patch removes it from the
> tlv320dac33, and t2l4030 codec drivers.
> I'm not really sure about the restructure of the tlv320dac33 driver:
> - The codec ID register read has been removed, which is really useful, and it is going to be
> used to enable/disable features of DAC33 based on the ID.
> - Originally the codec was off by default, now it is on all the time.
> - What is the reason to move the IRQ, GPIO, and regulator request from the i2c_probe to soc_probe?
>
> Some of these valid for the twl4030 codec as well (especially the idle_bias_off support).
>
> I don't claim, that I have checked all the patches, and changes, but at least with the tlv320dac33,
> and twl4030 codec drivers I can see some unwanted (for me) PM related regressions.
> Are these removals intentional?
Nope, this can all be explained my merge issues since both these codecs
did go though a lot of churn in the last few months. I'll fix up soon.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-07-05 21:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 17:52 [RFC 00/16] ASoC: multi-component - CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 01/16] ASoC: multi-component - AKM CODECs Liam Girdwood
2010-06-25 17:58 ` Liam Girdwood
2010-06-25 17:52 ` [RFC 02/16] ASoC: multi-component - cs4720, cs42l51 and da7210 CODECs Liam Girdwood
2010-06-25 18:29 ` Timur Tabi
2010-06-26 17:36 ` Liam Girdwood
2010-06-25 17:52 ` [RFC 03/16] ASoC: multi-component - pcm3008, ssm2602, jz4740 and uda1380 Liam Girdwood
2010-06-25 17:52 ` [RFC 04/16] ASoC: multi-component - TI CODECs Liam Girdwood
2010-06-30 12:08 ` peter.ujfalusi
2010-06-30 12:53 ` Mark Brown
2010-07-01 19:02 ` Mark Brown
2010-07-05 21:15 ` Liam Girdwood [this message]
2010-06-30 19:39 ` Bedia, Vaibhav
2010-06-25 17:52 ` [RFC 05/16] ASoC: multi-component - open firmware Liam Girdwood
2010-06-25 17:52 ` [RFC 06/16] ASoC: multi-component - Generic AC97 and SPDIF CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 07/16] ASoC: multi-component - cq93vc, cx20442, stac9766 and UDA134x CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 08/16] ASoC: multi-component - Wolfson WM85xx CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 09/16] ASoC: multi-component - Wolfson WM87xx CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 10/16] ASoC: multi-component - Wolfson wm8900, 8903, 8904 and 8955 CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 11/16] ASoC: multi-component - Wolfson wm8960, 8961 and 8940 CODECs Liam Girdwood
2010-06-25 17:52 ` [RFC 12/16] ASoC: multi-component - Wolfson WM8971, 8993, 8990 and 8974 CODECs Liam Girdwood
2010-06-25 17:53 ` [RFC 13/16] ASoC: multi-component - Wolfson WM8978, 8988 and 8994 CODECs Liam Girdwood
2010-06-25 17:53 ` [RFC 14/16] ASoC: multi-component - Wolfson WM90xx CODECs Liam Girdwood
2010-06-25 17:53 ` [RFC 15/16] ASoC: multi-component - Wolfson AudioPlus CODECs Liam Girdwood
2010-06-25 17:53 ` [RFC 16/16] ASoC: multi-component - Wolfson WM97xx AC97 CODECs Liam Girdwood
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=1278364546.3258.215.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