From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: Nokia N900: mixers changed between 4.9 and 4.10-rc3, no longer can use in-call speaker
Date: Sun, 15 Jan 2017 01:00:54 +0100	[thread overview]
Message-ID: <201701150100.54214@pali> (raw)
In-Reply-To: <20170114225614.GA25321@amd>
On Saturday 14 January 2017 23:56:15 Pavel Machek wrote:
> Hi!
> 
> > > In v4.10 (and probably v4.9, too) I can no longer use the in-call
> > > speaker. I can no longer use the wired headset, either.
> > > 
> > > v4.4 (and probably v4.6) works ok.
> > > 
> > > Any ideas? Does wired headset / in-call speaker work for you?
> > > 
> > > "Mono" and "Mono DAC" options are still there.. but something
> > > else changed, as alsamixer now shows way many more options
> > > (meaning they are shorter?) and I get complains from alsactl:
> > > 
> > > alsactl: set_control:1328: failed to obtain info for control #49
> > > (No such file or directory)
> > > ...
> > > alsactl: set_control:1328: failed to obtain info for control #229
> > > (No such file or directory)
> > 
> > Looks like there are not so much commits related to
> > sound/soc/omap/rx51.c Maybe it can be one of these twos?
> > 
> > cb7e62256e99d285e415cf75db67558f0f8bb107
> > 6d2de5ab4328718302c54b20222c6b1a574c3fce
> 
> Both are based on v4.7-rc1. v4.6 worked ok for me.
> 
> Lets test mini-v4.7: in-call speaker works ok there, and no alsactl
> warnings.
> 
> mini-v4.7+cb7e62256e99d285e415cf75db67558f0f8bb107+6d2de5ab4328718302
> c54b20222c6b1a574c3fce
> 
> : something seems to be broken there already.
> 
> alsactl: set_control:1464: Cannot write control '2:0:0:TPA6130A2
> Headphone Playback Volume:0' : Remote I/O error
> 
> But in-call speakers and wired headset still seems to work.
> 
> Lets test mini-v4.9... works ok. I don't even get the remote i/o
> error. Interesting.
> 
> So regression seems to be between v4.9 and v4.10. Any ideas?
Interesting... seems there are no sound relevant changes after v4.9.
Looks like there are only three commits after v4.9 for sound/soc which 
are built for Nokia N900:
e411b0b5eb9b65257a050eac333d181d6e00e2c6
e7aa450fe17890e59db7d3c2d8eff5b6b41fc531
63c3194b82530bd71fd49db84eb7ab656b8d404a
Maybe something not related to sound/soc could broke it?
-- 
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170115/1ff353d6/attachment.sig>
next prev parent reply	other threads:[~2017-01-15  0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 18:18 Nokia N900: mixers changed between 4.6 and 4.10, no longer can use in-call speaker Pavel Machek
2017-01-12 18:34 ` Pali Rohár
2017-01-14 22:56   ` Nokia N900: mixers changed between 4.9 and 4.10-rc3, " Pavel Machek
2017-01-15  0:00     ` Pali Rohár [this message]
2017-01-15 10:05       ` Pavel Machek
2017-01-15 19:08         ` Jarkko Nikula
2017-01-17 13:47           ` Peter Ujfalusi
2017-01-19 18:51             ` Jarkko Nikula
     [not found]               ` <20170120133159.GA5241@amd>
2017-01-20 13:38                 ` Nokia N900: microphone mixers Pali Rohár
2017-01-20 14:00                   ` Pavel Machek
2017-01-20 14:04                     ` Pali Rohár
2017-01-20 19:32                       ` Pavel Machek
2017-01-16 21:15       ` Nokia N900: mixers changed between 4.9 and 4.10-rc3, no longer can use in-call speaker Pavel Machek
2017-01-18 20:44         ` Pavel Machek
2017-01-18 21:55           ` Pavel Machek
2017-01-19  1:17             ` Kuninori Morimoto
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=201701150100.54214@pali \
    --to=pali.rohar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).