Audio issue on Kirkwood t5325: no sound
broonie at kernel.org
Thu Jul 18 17:52:32 EDT 2013
On Thu, Jul 18, 2013 at 10:23:50PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 18, 2013 at 10:15:21PM +0100, Mark Brown wrote:
> > This means that for uda134x (which I think is what you're using here, I
> No, this report is against ALC5623, which does appear to have widgets.
> I was remarking that this looks like the same kind of issue I had with
Ah, OK. In that case the issue is likely to be that no connection has
been made between the audio interface and the outputs desired - probably
some routing control needs to be enabled by userspace. If there's no
visible path between a source of audio (like playback from the CPU) and
a sink (such as an output) then the framework will think there's nothing
> So if everything on the codec is powered down, it's not surprising that
> there is no audio output.
Indeed, and if the routing isn't set up to connect an audio path the
core will not bother powering it on at all. The issue with the UDA134x
is that we need to give the framework the information that the playback
interfaces are connected to an output (or restore the code to do this in
the core but at this point since it's all data driven now in the drivers
it's easier and more robust to just plumb them in and avoid having to
deal with special cases which keep tripping us up).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the linux-arm-kernel