From: Lars-Peter Clausen <lars@metafoo.de>
To: Fabio Estevam <festevam@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
alsa-devel@alsa-project.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: ASoC: Failed to create component debugfs directory
Date: Tue, 20 Feb 2018 15:24:02 +0100 [thread overview]
Message-ID: <5b591fd8-d4d5-27bb-0850-a376da20d7f3@metafoo.de> (raw)
In-Reply-To: <CAOMZO5C3joR2QS+yFDmQUs1Q69PfuVw8tBMNd+F+cjDnUMEPSQ@mail.gmail.com>
On 02/20/2018 03:18 PM, Fabio Estevam wrote:
> On Mon, Feb 19, 2018 at 3:49 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi,
>>
>> On linux-next I see the following errors on imx6 wandboard:
>>
>> [ 3.040897] fsl-ssi-dai 2028000.ssi: ASoC: Failed to create
>> component debugfs directory
>> [ 3.065722] fsl-spdif-dai 2004000.spdif: ASoC: Failed to create
>> component debugfs directory
>>
>> I haven't started debugging this yet and not sure if this is something
>> fsl driver specific.
>
> This is not fsl sound specific as I see the same warnings in
> kernelci.org boot logs with other SoCs.
>
> The failures happens because we are trying to create debugfs twice:
>
> [ 2.122894] mmc1: new SDIO card at address 0001
> [ 2.150560] fsl-asoc-card sound: ASoC: CPU DAI (null) not registered
> [ 2.160601] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW
> [ 2.326140] [drm] Cannot find any crtc or sizes
> [ 2.538048] ******** component name is 2028000.ssi
> [ 2.542911] fsl-ssi-dai 2028000.ssi: ASoC: Succeeded in creating
> component debugfs directory
> [ 2.551513] ******** component name is sgtl5000.1-000a
> [ 2.556761] sgtl5000 1-000a: ASoC: Succeeded in creating component
> debugfs directory
> [ 2.580521] ******** component name is 2028000.ssi
> [ 2.585552] fsl-ssi-dai 2028000.ssi: ASoC: Failed to create
> component debugfs directory
> [ 2.601344] imx-sgtl5000 sound: sgtl5000 <-> 2028000.ssi mapping ok
> [ 2.620625] ******** component name is 2004000.spdif
> [ 2.625867] fsl-spdif-dai 2004000.spdif: ASoC: Succeeded in
> creating component debugfs directory
> [ 2.634754] ******** component name is 2004000.spdif
> [ 2.639850] fsl-spdif-dai 2004000.spdif: ASoC: Failed to create
> component debugfs directory
> [ 2.652127] imx-spdif sound-spdif: snd-soc-dummy-dai <->
> 2004000.spdif mapping ok
>
> Any ideas why this second debugfs registration is being attempted?
>
One for the DMA, one for the I2S?
next prev parent reply other threads:[~2018-02-20 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 18:49 ASoC: Failed to create component debugfs directory Fabio Estevam
2018-02-19 20:14 ` Nicolin Chen
2018-02-20 11:47 ` Mark Brown
2018-02-20 14:18 ` Fabio Estevam
2018-02-20 14:24 ` Lars-Peter Clausen [this message]
2018-02-20 19:26 ` Fabio Estevam
2018-02-20 19:30 ` Lars-Peter Clausen
2018-02-20 19:37 ` Fabio Estevam
2018-02-21 13:02 ` Mark Brown
2018-02-21 13:43 ` Fabio Estevam
2018-02-21 13:47 ` Fabio Estevam
2018-02-21 14:40 ` Mark Brown
2018-02-20 16:40 ` Fabio Estevam
2018-02-20 18:37 ` Srinivas Kandagatla
2018-02-20 18:43 ` Fabio Estevam
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=5b591fd8-d4d5-27bb-0850-a376da20d7f3@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=nicoleotsuka@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.