From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: ASoC: Failed to create component debugfs directory
Date: Tue, 20 Feb 2018 11:47:08 +0000 [thread overview]
Message-ID: <20180220114708.GA6378@sirena.org.uk> (raw)
In-Reply-To: <20180219201440.GA10420@Asurada>
[-- Attachment #1.1: Type: text/plain, Size: 613 bytes --]
On Mon, Feb 19, 2018 at 12:14:41PM -0800, Nicolin Chen wrote:
> On Mon, Feb 19, 2018 at 03:49:11PM -0300, Fabio Estevam wrote:
> > [ 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.
> I think it's because we recently changed all CPU dai drivers to
> component drivers, so our drivers should probably add something
> to create debugfs directories I guess...will take a look at it.
Hrm, that's not the goal - if every driver has to do it there's
something wrong.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-02-20 11:47 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 [this message]
2018-02-20 14:18 ` Fabio Estevam
2018-02-20 14:24 ` Lars-Peter Clausen
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=20180220114708.GA6378@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.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.