From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: brgl@bgdev.pl, david@lechnology.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: regmap: Failed to create debugfs directory
Date: Thu, 1 Mar 2018 18:24:36 +0000 [thread overview]
Message-ID: <20180301182436.GI12864@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5BsSpi_40ky5L_XafxNULnprphv9nhPCQVNgi+vmexD+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Thu, Mar 01, 2018 at 03:19:50PM -0300, Fabio Estevam wrote:
> Hi,
>
> Running linux-next 20180301 on a imx6q-sabresd the following
> regmap-debugfs warnings are seen:
Is this triggered by 9b947a13e7f6017f18 (regmap: use debugfs even when
no device)?
>
> [ 0.067965] CPU identified as i.MX6Q, silicon rev 1.2
> [ 0.083466] vdd1p1: supplied by regulator-dummy
> [ 0.084768] vdd3p0: supplied by regulator-dummy
> [ 0.085816] vdd2p5: supplied by regulator-dummy
> [ 0.109831] (NULL device *): Failed to create debugfs directory
> ....
>
> [ 2.961117] input: EETI eGalax Touch Screen as
> /devices/soc0/soc/2100000.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0
> [ 2.977027] (NULL device *): Failed to create debugfs directory
> [ 2.983929] snvs_rtc 20cc000.snvs:snvs-rtc-lp: rtc core: registered
> 20cc000.snvs:snvs-rtc-lp as rtc0
> [ 2.993457] i2c /dev entries driver
> [ 3.002084] (NULL device *): Failed to create debugfs directory
> [ 3.010452] imx2-wdt 20c0000.wdog: timeout 60 sec (nowayout=0)
>
> I haven't started to debug this yet, but would like to know if anyone
> has any ideas?
>
> Thanks,
>
> Fabio Estevam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-01 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 18:19 Fabio Estevam
2018-03-01 18:24 ` Mark Brown [this message]
2018-03-02 0:27 ` Fabio Estevam
2018-03-02 12:35 ` Fabio Estevam
2018-03-01 18:28 ` Fabio Estevam
2018-03-05 16:07 ` 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=20180301182436.GI12864@sirena.org.uk \
--to=broonie@kernel.org \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®