public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Pavel Machek <pavel@ucw.cz>,
	pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com
Subject: Re: 3.19 on Nokia n900: audio quality awful
Date: Wed, 28 Jan 2015 20:15:46 +0200	[thread overview]
Message-ID: <54C92752.9000004@bitmer.com> (raw)
In-Reply-To: <54C63F1C.6010703@ti.com>

On 01/26/2015 03:20 PM, Peter Ujfalusi wrote:
> On 01/18/2015 02:01 PM, Pavel Machek wrote:
>> In 2.6.28-nokia, it is neccessary to set "Input select" na "digital
>> mic", then it works. Input select being in "playback" option makes it
>> easy to miss.
>>
>> In 3.18 and 3.19-rc3, all I can record are zeros.
>>
>> Does playback/recording work for you on OMAP 3430-based machines?
> 
> Same codec (tlv320aic3106) works fine on my am335x and omap-l138 boards.
> BeagleBoard-xM also fine with twl4030 codec.
> 
> I don't have my n900 in hacking mode (it is still in use time-to-time) but
> looking at the dts file: you might want to add ai3x-micbias-vg property to the
> aic3x nodes to select the correct mic bias voltage. I can't recall what is
> appropriate for n900, but 2.6.28-nokia sources might give you the answer.
> 
No need to go that far. N900 has been supported in mainline since 2.6.39
or so. Part A of AIC34 (which is basically dual AIC33 in a same package)
drives 2 V for the digital microphone bias and part B 2.5 V for the headset.

Unfortunately I haven't had time recently to try what might have caused
that regression after 3.18.

-- 
Jarkko

  reply	other threads:[~2015-01-29  2:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:04 3.19 on Nokia n900: audio quality awful Pavel Machek
2015-01-06 17:25 ` Felipe Balbi
2015-01-06 17:51   ` Pavel Machek
2015-01-06 20:28     ` Felipe Balbi
2015-01-06 20:50       ` Pavel Machek
2015-01-06 20:54         ` Felipe Balbi
2015-01-06 21:57           ` Pavel Machek
2015-01-06 22:02             ` Felipe Balbi
2015-01-06 20:57         ` Aaro Koskinen
2015-01-06 22:08           ` Pavel Machek
2015-01-06 22:27             ` Aaro Koskinen
2015-01-06 22:46               ` Felipe Balbi
2015-01-06 22:52                 ` Tony Lindgren
2015-01-06 22:56                 ` Pavel Machek
2015-01-06 23:04                   ` Felipe Balbi
2015-01-06 23:13                     ` Pavel Machek
2015-01-06 23:29                       ` Felipe Balbi
2015-01-06 22:58               ` Pavel Machek
2015-01-07 19:43                 ` Aaro Koskinen
2015-01-06 20:39     ` Aaro Koskinen
2015-01-18 12:01 ` Pavel Machek
2015-01-26 13:20   ` Peter Ujfalusi
2015-01-28 18:15     ` Jarkko Nikula [this message]
2015-01-28 22:41       ` Pavel Machek
2015-01-29  7:35         ` Jarkko Nikula
2015-01-29 11:19           ` Peter Ujfalusi
2015-01-29 20:42             ` Pavel Machek
2015-01-30  8:16               ` Pali Rohár
2015-01-30  8:52                 ` Pavel Machek
2015-01-30 10:26             ` Pavel Machek
2015-01-30 10:37               ` Pavel Machek
2015-01-30 12:40                 ` Peter Ujfalusi
2015-01-30 12:43                   ` Peter Ujfalusi
2015-01-28 22:02     ` Pavel Machek

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=54C92752.9000004@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=peter.ujfalusi@ti.com \
    --cc=sre@debian.org \
    --cc=sre@ring0.de \
    --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