<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tinyalsa, branch master</title>
<subtitle>Tiny library to interface with ALSA in the Linux kernel</subtitle>
<id>http://git.dec05eba.com/tinyalsa/atom/?h=master</id>
<link rel='self' href='http://git.dec05eba.com/tinyalsa/atom/?h=master'/>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/'/>
<updated>2023-09-13T19:01:06Z</updated>
<entry>
<title>Add build.zig</title>
<updated>2023-09-13T19:01:06Z</updated>
<author>
<name>dec05eba</name>
<email>dec05eba@protonmail.com</email>
</author>
<published>2023-09-13T19:01:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=a1b12e879c16dcdfbcc5fc8975ba14d692528c6b'/>
<id>urn:sha1:a1b12e879c16dcdfbcc5fc8975ba14d692528c6b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #244 from rohit-qc/chmap_mixer_support</title>
<updated>2023-09-05T02:20:40Z</updated>
<author>
<name>dvdli</name>
<email>70133153+dvdli@users.noreply.github.com</email>
</author>
<published>2023-09-05T02:20:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=2ca2386c1f41f3820e22281de570b19380682086'/>
<id>urn:sha1:2ca2386c1f41f3820e22281de570b19380682086</id>
<content type='text'>
Chmap mixer support</content>
</entry>
<entry>
<title>utils: tinymix: Print device number associated with mixer controls</title>
<updated>2023-09-04T09:56:19Z</updated>
<author>
<name>Rohit kumar</name>
<email>quic_rohkumar@quicinc.com</email>
</author>
<published>2023-05-30T15:04:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=4516c73951d861e974f338540b026285148dc426'/>
<id>urn:sha1:4516c73951d861e974f338540b026285148dc426</id>
<content type='text'>
For mixer controls with same name and different device number, there
is no clarity in tinymix output. Print device number along with
mixer control name to distinguish between mixer controls with
same name.
</content>
</entry>
<entry>
<title>mixer: add support for pcm device specific mixer controls</title>
<updated>2023-09-04T09:56:14Z</updated>
<author>
<name>Rohit kumar</name>
<email>quic_rohkumar@quicinc.com</email>
</author>
<published>2023-05-30T14:57:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=a8a581fb422c9c2af2d8858a678c008db80e1e3c'/>
<id>urn:sha1:a8a581fb422c9c2af2d8858a678c008db80e1e3c</id>
<content type='text'>
Mixer control such as "Playback channel map" can be registered by
multiple pcm device nodes and is distinguished by device in
snd_ctl_elem_id. Add support to get the control handle associated
with mixer ctl name and device number.
Also, introduce API to get the device number associated with specific
mixer_ctl handle.
</content>
</entry>
<entry>
<title>Merge pull request #246 from CodeLinaro/master</title>
<updated>2023-09-04T09:34:44Z</updated>
<author>
<name>dvdli</name>
<email>70133153+dvdli@users.noreply.github.com</email>
</author>
<published>2023-09-04T09:34:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=c0fbed5e2ba87ee8cacc3cbca55488bcb85f327a'/>
<id>urn:sha1:c0fbed5e2ba87ee8cacc3cbca55488bcb85f327a</id>
<content type='text'>
Support pcm drain ops</content>
</entry>
<entry>
<title>Support pcm drain ops</title>
<updated>2023-09-04T05:15:03Z</updated>
<author>
<name>Guodong Hu</name>
<email>quic_guodhu@quicinc.com</email>
</author>
<published>2023-08-15T05:37:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=bc3af517534346742a2e753f753a0ad21f51513b'/>
<id>urn:sha1:bc3af517534346742a2e753f753a0ad21f51513b</id>
<content type='text'>
Signed-off-by: Guodong Hu &lt;quic_guodhu@quicinc.com&gt;
</content>
</entry>
<entry>
<title>Merge pull request #237 from michaelforney/tinyplay-format</title>
<updated>2023-09-04T02:33:51Z</updated>
<author>
<name>dvdli</name>
<email>70133153+dvdli@users.noreply.github.com</email>
</author>
<published>2023-09-04T02:33:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=7c467a1179cca66bb65a4a04f889319e4bfb9b3e'/>
<id>urn:sha1:7c467a1179cca66bb65a4a04f889319e4bfb9b3e</id>
<content type='text'>
tinyplay: fix playback of 24-bit and 8-bit pcm</content>
</entry>
<entry>
<title>tinyplay: fix playback of 24-bit and 8-bit pcm</title>
<updated>2022-10-31T07:10:39Z</updated>
<author>
<name>Michael Forney</name>
<email>mforney@mforney.org</email>
</author>
<published>2022-10-31T07:07:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=f5368cdf08be50d8de01155e17a2dfdcb3c9beb3'/>
<id>urn:sha1:f5368cdf08be50d8de01155e17a2dfdcb3c9beb3</id>
<content type='text'>
The bits-to-format function returned bool, which happened to work
for PCM_FORMAT_S16_LE (0) and PCM_FORMAT_S32_LE (1). However, all
other formats were incorrectly mapped to PCM_FORMAT_S32_LE. Return
enum pcm_format instead.
</content>
</entry>
<entry>
<title>Merge pull request #230 from rsglobal/propagate-error-message</title>
<updated>2022-08-03T07:21:49Z</updated>
<author>
<name>dvdli</name>
<email>70133153+dvdli@users.noreply.github.com</email>
</author>
<published>2022-08-03T07:21:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=4fbaeef03cd1cb216e0f356c0433ca70f8b9c464'/>
<id>urn:sha1:4fbaeef03cd1cb216e0f356c0433ca70f8b9c464</id>
<content type='text'>
pcm: Propagate error message to the bad_pcm in case of failure</content>
</entry>
<entry>
<title>pcm: Propagate error message to the bad_pcm in case of failure</title>
<updated>2022-07-26T14:09:39Z</updated>
<author>
<name>Roman Stratiienko</name>
<email>r.stratiienko@gmail.com</email>
</author>
<published>2022-07-26T14:07:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dec05eba.com/tinyalsa/commit/?id=563016b7fe31a8918b3db2a2f2cbb67607ecd153'/>
<id>urn:sha1:563016b7fe31a8918b3db2a2f2cbb67607ecd153</id>
<content type='text'>
Signed-off-by: Roman Stratiienko &lt;r.stratiienko@gmail.com&gt;
</content>
</entry>
</feed>
