From: Mark Brown <broonie@kernel.org>
To: "kernelci.org bot" <bot@kernelci.org>
Cc: Olivier Moysan <olivier.moysan@st.com>,
mgalka@collabora.com, enric.balletbo@collabora.com,
khilman@baylibre.com, tomeu.vizoso@collabora.com,
guillaume.tucker@collabora.com,
Brian Austin <brian.austin@cirrus.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>,
Paul Handrigan <Paul.Handrigan@cirrus.com>
Subject: Re: broonie-sound/for-next bisection: boot on rk3399-gru-kevin
Date: Tue, 10 Dec 2019 13:08:01 +0000 [thread overview]
Message-ID: <20191210130801.GF6110@sirena.org.uk> (raw)
In-Reply-To: <5def94e7.1c69fb81.2751f.190a@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Tue, Dec 10, 2019 at 04:51:51AM -0800, kernelci.org bot wrote:
> ASoC: cs42l51: add dac mux widget in codec routes
>
> Add "DAC mux" DAPM widget in CS42l51 audio codec routes,
> to support DAC mux control and to remove error trace
> "DAC Mux has no paths" at widget creation.
> Note: ADC path of DAC mux is not routed in this patch.
This doesn't seem right, as far as I can see this device is not present
on that board (it uses some Realtek and Maxim devices AFAICT). Is it
some sort of timing thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-10 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 12:51 kernelci.org bot
2019-12-10 13:08 ` Mark Brown [this message]
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=20191210130801.GF6110@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=bot@kernelci.org \
--cc=brian.austin@cirrus.com \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalka@collabora.com \
--cc=olivier.moysan@st.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tomeu.vizoso@collabora.com \
/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
all inboxes | Powered by JetHome®