From: jeffy.chen@rock-chips.com (Jeffy Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] This series of patches fix the boot time dapm route warnings(without rt5514):
Date: Tue, 19 Sep 2017 20:57:55 +0800 [thread overview]
Message-ID: <20170919125800.336-1-jeffy.chen@rock-chips.com> (raw)
[ 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
And support detect rt5514-dsp codec and rt5514 codec by checking bus_type.
Changes in v3:
Rebase onto for-next 20170919
Changes in v2:
Separate HDMI/DMIC patches.
Fix DMic typo.
Jeffy Chen (5):
ASoC: rockchip: Add dapm route for HDMI
ASoC: rockchip: Add dapm route for DMic
ASoC: rockchip: Init dapm routes dynamically
ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514
codec
ASoC: rt5514: Add devicetree binding support for rt5514-spi
Documentation/devicetree/bindings/sound/rt5514.txt | 13 +-
sound/soc/rockchip/rk3399_gru_sound.c | 149 +++++++++++++++++----
2 files changed, 132 insertions(+), 30 deletions(-)
--
2.11.0
next reply other threads:[~2017-09-19 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:57 Jeffy Chen [this message]
2017-09-19 12:57 ` [PATCH v3 1/5] ASoC: rockchip: Add dapm route for HDMI Jeffy Chen
2017-09-19 12:57 ` [PATCH v3 2/5] ASoC: rockchip: Add dapm route for DMic Jeffy Chen
2017-09-19 12:57 ` [PATCH v3 3/5] ASoC: rockchip: Init dapm routes dynamically Jeffy Chen
2017-09-19 12:57 ` [PATCH v3 4/5] ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec Jeffy Chen
2017-09-19 13:46 ` Applied "ASoC: rockchip: Use bus_type to distinguish rt5514 dsp from rt5514 codec" to the asoc tree Mark Brown
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=20170919125800.336-1-jeffy.chen@rock-chips.com \
--to=jeffy.chen@rock-chips.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