From: Mark Brown <broonie@kernel.org>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
"\"René van Dorst\"" <opensource@vdorst.com>
Subject: Re: Aw: Re: BUG: devm_regulator_get returns EPROBE_DEFER (5.3-rc5..next-20190822) for bpi-r2/mt7623/mt7530
Date: Fri, 23 Aug 2019 11:04:24 +0100 [thread overview]
Message-ID: <20190823100424.GL23391@sirena.co.uk> (raw)
In-Reply-To: <trinity-5d117f0d-9f34-4a2b-8a12-1cd34152c108-1566505724458@3c-app-gmx-bs43>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
On Thu, Aug 22, 2019 at 10:28:44PM +0200, Frank Wunderlich wrote:
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
> cfba5de9b99f drivers: Introduce device lookup variants by of_node
>
> this looks suspicios to me since the change is in the function which fails:
> struct regulator_dev *of_find_regulator_by_node(struct device_node *np)
> {
> struct device *dev;
>
> - dev = class_find_device(®ulator_class, NULL, np, of_node_match);
> + dev = class_find_device_by_of_node(®ulator_class, np);
>
>
> but i cannot revert this commit so i did it manually...but this does not seem to be the cause...still error 517, also a change in core.c is not the cause...
Can you run a git bisect to try to identify the commit that
caused things to fail?
> how can i check instantiation at runtime?
Look to see if there is a device driver bound to that device, or
check if the parent regulator is visible in /sys/class/regulators.
You'll also see a mesage printed out for each regulator as it
instantiates in the boot logs, you can check there too.
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-23 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 19:23 BUG: devm_regulator_get returns EPROBE_DEFER (5.3-rc5..next-20190822) for bpi-r2/mt7623/mt7530 Frank Wunderlich
2019-08-22 19:30 ` Mark Brown
2019-08-22 20:28 ` Aw: " Frank Wunderlich
2019-08-23 10:04 ` Mark Brown [this message]
2019-08-23 12:00 ` Aw: " Frank Wunderlich
2019-08-23 14:43 ` Matthias Brugger
[not found] ` <0fcdea56-c6fc-993d-1520-be40ff03df2d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-23 15:07 ` Frank Wunderlich
2019-08-27 19:34 ` 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=20190823100424.GL23391@sirena.co.uk \
--to=broonie@kernel.org \
--cc=frank-w@public-files.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=opensource@vdorst.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;
as well as URLs for NNTP newsgroup(s).