<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/stable/linux.git/sound/soc/codecs, branch linux-4.2.y</title>
<subtitle>Linux kernel stable tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=linux-4.2.y</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=linux-4.2.y'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/'/>
<updated>2015-10-22T21:49:21+00:00</updated>
<entry>
<title>ASoC: tas2552: fix dBscale-min declaration</title>
<updated>2015-10-22T21:49:21+00:00</updated>
<author>
<name>Andreas Dannenberg</name>
<email>dannenberg@ti.com</email>
</author>
<published>2015-10-05T20:00:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0bfc2f5be12d31d56053c0dd933ee0686690237a'/>
<id>urn:sha1:0bfc2f5be12d31d56053c0dd933ee0686690237a</id>
<content type='text'>
commit e2600460bc3aa14ca1df86318a327cbbabedf9a8 upstream.

The minimum volume level for the TAS2552 (control register value 0x00)
is -7dB however the driver declares it as -0.07dB.

Running amixer before the patch reports:
dBscale-min=-0.07dB,step=1.00dB,mute=0

Running amixer with the patch applied reports:
dBscale-min=-7.00dB,step=1.00dB,mute=0

Signed-off-by: Andreas Dannenberg &lt;dannenberg@ti.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: sgtl5000: fix wrong register MIC_BIAS_VOLTAGE setup on probe</title>
<updated>2015-10-22T21:49:21+00:00</updated>
<author>
<name>Gianluca Renzi</name>
<email>gianlucarenzi@eurekelettronica.it</email>
</author>
<published>2015-09-25T19:33:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=db120b6f5fa664cbd146b174737593140e27c2e4'/>
<id>urn:sha1:db120b6f5fa664cbd146b174737593140e27c2e4</id>
<content type='text'>
commit e256da84a04ea31c3c215997c847609af224e8f4 upstream.

Signed-off-by: Gianluca Renzi &lt;gianlucarenzi@eurekelettronica.it&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: arizona: Poll for FLL clock OK rather than use interrupts</title>
<updated>2015-09-21T17:10:54+00:00</updated>
<author>
<name>Charles Keepax</name>
<email>ckeepax@opensource.wolfsonmicro.com</email>
</author>
<published>2015-08-25T11:43:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d96fc0af4ea266d2fc39a49a44d46b56c53f502c'/>
<id>urn:sha1:d96fc0af4ea266d2fc39a49a44d46b56c53f502c</id>
<content type='text'>
commit 0e7659712836ca59b4735bc5cc94de38698a5e01 upstream.

The extcon driver takes the DAPM mutex from within the interrupt thread
in several places, which makes it possible to get into a situation where
the interrupt thread is blocked waiting on the DAPM mutex whilst a DAPM
sequence is running which is attempting to configure the FLL. In this
case the FLL completion can't be completed as as the IRQ handler is
ONE_SHOT, which cause the FLL lock to use the full time out (250mS) and
report that the process timed out.

It is not really practical to make the extcon driver not take the DAPM
mutex from within the interrupt thread, at least not without extensive
modification. So this patch fixes the issue by switching the wait for
the FLL lock to polling. A few fast polls are done first as the FLL
should lock quickly for a good quality reference clock, (indeed it hits
on the first poll on my system) and it will poll every 20mS after that
until it times out.

Signed-off-by: Charles Keepax &lt;ckeepax@opensource.wolfsonmicro.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: arizona: Fix gain settings of FLL in free-run mode</title>
<updated>2015-09-21T17:10:54+00:00</updated>
<author>
<name>Nikesh Oswal</name>
<email>Nikesh.Oswal@wolfsonmicro.com</email>
</author>
<published>2015-08-19T15:02:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=00de7f96794db1f761480e172326a9d42c6e8697'/>
<id>urn:sha1:00de7f96794db1f761480e172326a9d42c6e8697</id>
<content type='text'>
commit 1cf5a330c05ae37a0a98ac7c9800a6f50d5579ec upstream.

The wrong register was used to set the gain of ref loop, when changing
the FLL output on an active FLL. This patch corrects the offset of the
gain register.

Signed-off-by: Nikesh Oswal &lt;Nikesh.Oswal@wolfsonmicro.com&gt;
Signed-off-by: Charles Keepax &lt;ckeepax@opensource.wolfsonmicro.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: adav80x: Remove .read_flag_mask setting from adav80x_regmap_config</title>
<updated>2015-09-21T17:10:53+00:00</updated>
<author>
<name>Axel Lin</name>
<email>axel.lin@ingics.com</email>
</author>
<published>2015-08-14T09:54:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fa3b747afec0c88cef9d9e99090f4c8993d66410'/>
<id>urn:sha1:fa3b747afec0c88cef9d9e99090f4c8993d66410</id>
<content type='text'>
commit 9d8352864907f0ad76124c5b28f65b5a382d7d7c upstream.

Don't set .read_flag_mask for adav803, it's for adav801 only.

Fixes: 0c2d69645628 ("ASoC: adav80x: Split SPI and I2C code into different modules")
Signed-off-by: Axel Lin &lt;axel.lin@ingics.com&gt;
Acked-by: Lars-Peter Clausen &lt;lars@metafoo.de&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: rt5645: Add struct dmi_system_id "Google Celes" for chrome platform</title>
<updated>2015-09-21T17:10:53+00:00</updated>
<author>
<name>Oder Chiou</name>
<email>oder_chiou@realtek.com</email>
</author>
<published>2015-08-25T08:03:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7ae811d50e1bfca4eb30366787f53d797892fd7f'/>
<id>urn:sha1:7ae811d50e1bfca4eb30366787f53d797892fd7f</id>
<content type='text'>
commit c1713485f9fc06e1f4de9800b43f6486f2527379 upstream.

Signed-off-by: Oder Chiou &lt;oder_chiou@realtek.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ASoC: rt5640: fix line out no sound issue</title>
<updated>2015-09-21T17:10:53+00:00</updated>
<author>
<name>John Lin</name>
<email>john.lin@realtek.com</email>
</author>
<published>2015-08-11T06:27:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=33d4ee442a28e215d2b798fd0788e7b797d8fb29'/>
<id>urn:sha1:33d4ee442a28e215d2b798fd0788e7b797d8fb29</id>
<content type='text'>
commit 9b850ca4f1c5acd7fcbbd4b38a2d27132801a8d5 upstream.

The power for line out was not turned on when line out is enabled.
So we add "LOUT amp" widget to turn on the power for line out.

Signed-off-by: John Lin &lt;john.lin@realtek.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Merge remote-tracking branches 'asoc/fix/cs4265', 'asoc/fix/intel' and 'asoc/fix/topology' into asoc-linus</title>
<updated>2015-08-06T11:39:07+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2015-08-06T11:39:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d00a9e02178401433fc386e69c936f2039f07b57'/>
<id>urn:sha1:d00a9e02178401433fc386e69c936f2039f07b57</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'asoc/fix/rt5645' into asoc-linus</title>
<updated>2015-08-06T11:39:07+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2015-08-06T11:39:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=78be55af0d6092dd7ec19c0c7b2f381383af1a95'/>
<id>urn:sha1:78be55af0d6092dd7ec19c0c7b2f381383af1a95</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ASoC: rt5645: Fix lost pin setting for DMIC1</title>
<updated>2015-08-03T16:02:45+00:00</updated>
<author>
<name>Bard Liao</name>
<email>bardliao@realtek.com</email>
</author>
<published>2015-08-03T04:17:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a094935e4ebdf5c22c45b8aeeb2d88e9e8c53dbf'/>
<id>urn:sha1:a094935e4ebdf5c22c45b8aeeb2d88e9e8c53dbf</id>
<content type='text'>
I2S2_DAC pin can be used for I2S or GPIO. We should set it as GPIO
if we use GPIO5 as DMIC1 data pin.

Signed-off-by: Bard Liao &lt;bardliao@realtek.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
</feed>
