LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: <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: Tue, 6 Jan 2015 11:25:45 -0600	[thread overview]
Message-ID: <20150106172545.GK6502@saruman> (raw)
In-Reply-To: <20150106170433.GA5408@amd>

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

On Tue, Jan 06, 2015 at 06:04:33PM +0100, Pavel Machek wrote:
> Hi!
> 
> In 3.18, sound is nice and clear.
> 
> In 3.19, sound is unusable. It produces nasty tone when it should be
> quiet, and there's at least as much noise as is sound.
> 
> Unfortunately, list of mixers also changed (and there's cca 120
> settings), but a) it does not work with the old list and b) nothing I
> could figure out did make the sound usable. Some setting resulted in
> even more noise.
> 
> Any idea what could have caused it?

$ git bisect start
$ git bisect good v3.18
$ git bisect bad

that'll help find what caused it.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-01-06 17:27 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 [this message]
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
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=20150106172545.GK6502@saruman \
    --to=balbi@ti.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=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;
as well as URLs for NNTP newsgroup(s).