New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 760797 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

gru: Configure audio routes in the device tree

Project Member Reported by mka@chromium.org, Aug 30 2017

Issue description

With the CL series leading to CL:643906 the audio configuration becomes more dynamic and is partially defined in the device tree. One thing that remains static are the DAPM routes. This seems to work, at least for now, however the kernel emits warnings when it doesn't find elements specified in the routes because a device doesn't have the corresponding codec:

[    2.475501] rk3399-gru-sound sound: ASoC: no sink widget found for DMIC1L
[    2.475503] rk3399-gru-sound sound: ASoC: Failed to add route Int Mic -> direct -> DMIC1L
[    2.475505] rk3399-gru-sound sound: ASoC: no sink widget found for DMIC1R
[    2.475507] rk3399-gru-sound sound: ASoC: Failed to add route Int Mic -> direct -> DMIC1R

The above trace is from scarlet, which doesn't have the rt5514.

This could be fixed by moving the specification of the audio routes to the device tree (rockchip,rk3399-gru-sound binding).

 
Cc: jeffy.c...@rock-chips.com
Similar/duplicate filed here:

https://issuetracker.google.com/65812341

Comment 3 by mka@chromium.org, Sep 18 2017

Status: WontFix (was: Assigned)
Let's track this in issue tracker (can't mark as dupe since the other issue is in a different tracker).

Sign in to add a comment