linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Felipe Balbi <balbi@ti.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	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,
	ivo.g.dimitrov.75@gmail.com
Subject: Re: 3.19 on Nokia n900: audio quality awful
Date: Wed, 7 Jan 2015 00:13:41 +0100	[thread overview]
Message-ID: <20150106231341.GA18468@amd> (raw)
In-Reply-To: <20150106230415.GC13752@saruman>

On Tue 2015-01-06 17:04:15, Felipe Balbi wrote:
> Hi,
> 
> On Tue, Jan 06, 2015 at 11:56:14PM +0100, Pavel Machek wrote:
> > > > But I'm mounting it from userspace (using builtin initramfs inside
> > > > zImage), with a poll loop that waits for a device to appear. Maybe if you
> > > > do it from kernel you need to use root wait/delay etc. options?
> > > 
> > > yeah, rootwait should do it.
> > 
> > No, rootwait does not solve it. Try it. Tested many times. (And yes,
> > you need to actually fool the rear cover sensor or close the phone.)
> 
> yeah, just put a magnet or, if you have spare back covers, cut one so
> that you "close" it, but still allow you to put the thing on a
> development jig.

Actually, it should be enough to kill a line from dts somewhere, no
need to hack hardware for this.

> Also, if why doesn't rootwait work ? You never have a new mmc node or is
> the mmc node changing names ?

IIRC node and name are ok, but the mount just fails. As I don't have
"development jig", I lack serial console and this kind of debugging is
not easy.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-01-06 23:13 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 [this message]
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=20150106231341.GA18468@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=balbi@ti.com \
    --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=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).